From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WdXnC-0007D9-8H for bitcoin-development@lists.sourceforge.net; Fri, 25 Apr 2014 04:31:18 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.171 as permitted sender) client-ip=209.85.213.171; envelope-from=gacrux@gmail.com; helo=mail-ig0-f171.google.com; Received: from mail-ig0-f171.google.com ([209.85.213.171]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WdXnB-0008SW-DB for bitcoin-development@lists.sourceforge.net; Fri, 25 Apr 2014 04:31:18 +0000 Received: by mail-ig0-f171.google.com with SMTP id c1so1758178igq.10 for ; Thu, 24 Apr 2014 21:31:12 -0700 (PDT) X-Received: by 10.50.61.177 with SMTP id q17mr2687459igr.44.1398400272115; Thu, 24 Apr 2014 21:31:12 -0700 (PDT) Received: from [192.168.1.150] (60-240-212-53.tpgi.com.au. [60.240.212.53]) by mx.google.com with ESMTPSA id p9sm5032451igj.16.2014.04.24.21.31.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Apr 2014 21:31:11 -0700 (PDT) Message-ID: <5359E509.4080907@gmail.com> Date: Fri, 25 Apr 2014 14:31:05 +1000 From: Gareth Williams User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: X-Enigmail-Version: 1.6 OpenPGP: id=378E4544 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3Gr6OtLHI1ErMj2JSCNODDECd3A1Dd5KG" X-Spam-Score: -1.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 (gacrux[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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: 1WdXnB-0008SW-DB Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage Finney attacks 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: Fri, 25 Apr 2014 04:31:18 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3Gr6OtLHI1ErMj2JSCNODDECd3A1Dd5KG Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 25/04/14 00:28, Mike Hearn wrote: > Why are we here? We are here because we were brought together by shared= > goals. >=20 > What are those goals? They were defined at the start of the project by > the creator of the project. >=20 > Why do we issue 21 million coins and not 42? Because 21 million is the > goal everyone signed up for. Mike: the blockchain is a public document, with a very public and well defined interpretation, which we've all signed up for too. What's the point of piling PoW on top of some data to make it difficult to modify if the interpretation itself is open to modification? There is an important distinction to draw between a hard fork via a change in block validation rules, and a hard fork via a change in the /interpretation of the blockchain itself/. Bitcoin validates data /before/ it makes it into a block; we can all be confident that, short of a reorg, /if it's in a block, it's the law/. As much as the 21m cap is the law anyway. Proving that you can convince the economic majority that the interpretation of existing blocks is in any way up for grabs would set a dangerous precedent, and shake some people's faith in Bitcoin's overall robustness and security (well, mine anyway.) My 2 bits. -Gareth --3Gr6OtLHI1ErMj2JSCNODDECd3A1Dd5KG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTWeUKAAoJEEY5w2E3jkVE6tIIAKlMwN6ZB42m/2k0BuAO7Hko yEPqUVkmgfECp4SG4vzTsNg0Z0kbMSasSTsA2TVo8mmNWM/3uiyORPkvsM7HUZnQ V+cNxqvlEjlo3uNLHWXxQJ0H+lU0MOog5/Dng9WDr1ffFPE8f1lGtB6qgV6eWWK6 mEKSh7iLThayz8tSooEVXnhSbcNAuZbNvfnFPmTOK2uIzEX8yttbyqk66Iti8PQj BWg4wgtzWGzAHbaXF+nc7Ohi0WVfmonbiJt+JI39t7XTVkt6KEReCEgrtlZQwh5x Yrkp65hHm9m/D7Dk0guuLS6Y/uqv0rQtHVtc4bzRTf+BQE5fa8aW2dKlekAD0n8= =D1Yw -----END PGP SIGNATURE----- --3Gr6OtLHI1ErMj2JSCNODDECd3A1Dd5KG--