Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XjDq7-00047q-Kq for bitcoin-development@lists.sourceforge.net; Tue, 28 Oct 2014 20:58:03 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.174 as permitted sender) client-ip=209.85.212.174; envelope-from=alex.mizrahi@gmail.com; helo=mail-wi0-f174.google.com; Received: from mail-wi0-f174.google.com ([209.85.212.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XjDq6-00042M-OB for bitcoin-development@lists.sourceforge.net; Tue, 28 Oct 2014 20:58:03 +0000 Received: by mail-wi0-f174.google.com with SMTP id d1so13977wiv.1 for ; Tue, 28 Oct 2014 13:57:56 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.190.19 with SMTP id gm19mr7563209wjc.4.1414529876540; Tue, 28 Oct 2014 13:57:56 -0700 (PDT) Received: by 10.27.203.138 with HTTP; Tue, 28 Oct 2014 13:57:56 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Oct 2014 22:57:56 +0200 Message-ID: From: Alex Mizrahi To: Gregory Maxwell Content-Type: multipart/alternative; boundary=047d7bea3792d0c367050681e64c X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (alex.mizrahi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XjDq6-00042M-OB Cc: Bitcoin Development Subject: Re: [Bitcoin-development] Fwd: death by halving X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Oct 2014 20:58:03 -0000 --047d7bea3792d0c367050681e64c Content-Type: text/plain; charset=UTF-8 > This thread is, in my opinion, a waste of time. It's yet again > another perennial bikeshedding proposal brought up many times since at > least 2011, suggesting random changes for > non-existing(/not-yet-existing) issues. > > There is a lot more complexity to the system than the subsidy schedule. > Well, the main question is what makes Bitcoin secure. It is secured by proofs of work which are produced by miners. Miners have economic incentives to play by the rules; in simple terms, that is more profitable than performing attacks. So the question is, why and when it works? It would be nice to know the boundaries, no? --047d7bea3792d0c367050681e64c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=C2=A0
This thread is, in my opinion, a waste of time.=C2=A0 It's yet again another perennial bikeshedding proposal brought up many times since at
least 2011, suggesting random changes for
non-existing(/not-yet-existing) issues.

There is a lot more complexity to the system than the subsidy schedule.
=

Well, the main question is what makes Bitc= oin secure.
It is secured by proofs of work which are produced by= miners.=C2=A0
Miners have economic incentives to play by the rul= es; in simple terms, that is more profitable than performing attacks.
=

So the question is, why and when it works? It would be = nice to know the boundaries, no?

--047d7bea3792d0c367050681e64c--