From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XmfDT-0004Bx-JO for bitcoin-development@lists.sourceforge.net; Fri, 07 Nov 2014 08:48:23 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.149.58 as permitted sender) client-ip=62.13.149.58; envelope-from=pete@petertodd.org; helo=outmail149058.authsmtp.co.uk; Received: from outmail149058.authsmtp.co.uk ([62.13.149.58]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1XmfDS-0007Aa-9o for bitcoin-development@lists.sourceforge.net; Fri, 07 Nov 2014 08:48:23 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt14.authsmtp.com (8.14.2/8.14.2) with ESMTP id sA78mEDt093931; Fri, 7 Nov 2014 08:48:14 GMT Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com [75.119.251.161]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id sA78mAVl081578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 7 Nov 2014 08:48:13 GMT Date: Fri, 7 Nov 2014 03:48:10 -0500 From: Peter Todd To: Tamas Blummer Message-ID: <20141107084810.GA7878@savin.petertodd.org> References: <20141106213215.GA12918@savin.petertodd.org> <545BF0C2.3030201@bluematt.me> <545BFAD6.1000504@riseup.net> <20141106232649.GD26859@savin.petertodd.org> <545C0617.7020300@riseup.net> <20141107000310.GA6532@savin.petertodd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: cf444794-665a-11e4-b396-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aQdMdgUUFloCAgsB AmIbW1xeVFV7WGA7 bA9PbARUfEhLXhtr VklWR1pVCwQmQm0G DkNvNEVyfwRDf3Y+ ZEdhWnAVDxJ+cUJ6 S0pJE2sDNHphaTUb TRJbfgVJcANIexZF O1F6ACIKLwdSbGoL NQ4vNDcwO3BTJTpY RgYVKF8UXXNDIj4x DxwDEzsuFlABWzR7 KBJuNUQdAEcXPQ05 Nl06VFQDLgRwQgZE Hl1MCyZdb1IGSyd5 RR9aUAYlMRJ9aBx8 NSYJBDBsL3RYRyUw X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 75.119.251.161/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1XmfDS-0007Aa-9o Cc: bitcoin-development@lists.sourceforge.net, Justus Ranvier Subject: Re: [Bitcoin-development] The difficulty of writing consensus critical code: the SIGHASH_SINGLE bug 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, 07 Nov 2014 08:48:23 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 07, 2014 at 09:07:47AM +0100, Tamas Blummer wrote: > Peter, >=20 > forking would work best with a freeze of the consensus code. Do you see a= ny chance for that? To a first approximation the consensus code *is* frozen; if we introduce any consensus changes into it at this point it's due to a mistake, not intentionally. Of course, that's not including the two serious soft-fork proposals in the air right now, Pieter Wuille's BIP62 and my CHECKLOCKTIMEVERIFY. However dealing with proposed changes like those in an environment where the competing implementations all use essentially the same consensus-critical code is much easier than in an environment where they don't; I say this on both a technical and political level. --=20 'peter'[:-1]@petertodd.org 00000000000000000c901eb1b6b765519b99c3afd7a9062ff4cfa29666ce140d --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJUXIdGXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw MDAwMDAwMDAwMDAwMDAwZjI4NmNhNDI1NGY5NmVmMTgyMWU1ZTQyYmY4MDA5MDk5 Y2NlNDZjY2IwNWIxOTUvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0 ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfuGjAf+KTzt9tv8EFDK6TpuZQ0NQ30i wflN/18Uj1qZEUVhSlFaoZzyamJv0soI1G7gqKeIedL5lFdMpoNR2MgY6YvN3do7 JxrhBGtAhs74cBPl0ndwSFa4h7AZyaI4Oh7N08LpSc5YamirQ64XbjSIQ1X9WkMV WIDzk8e3BgCNrw9dIAcGOtohoCMA3Jc69S6om/AMlLuHNwX0d4uIEFd8sB01knmk jLSiNpTawEOMRHBe8S107B6DcZrHEVWZVVoeusZvvGtY0rEnzUC3b/SesyYx9tLb otq7obVuntQ2c/I2dN6Bqfd0EiIYL8SIkktDmwmmG2snf3f0+feuiL1Kqx/h5Q== =Es4q -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g--