1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1XmWS7-0004aY-H9
for bitcoin-development@lists.sourceforge.net;
Thu, 06 Nov 2014 23:26:55 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.78 as permitted sender)
client-ip=62.13.149.78; envelope-from=pete@petertodd.org;
helo=outmail149078.authsmtp.net;
Received: from outmail149078.authsmtp.net ([62.13.149.78])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1XmWS6-0002sz-4o for bitcoin-development@lists.sourceforge.net;
Thu, 06 Nov 2014 23:26:55 +0000
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id sA6NQm5N030142;
Thu, 6 Nov 2014 23:26:48 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 sA6NQjxb079712
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Thu, 6 Nov 2014 23:26:47 GMT
Date: Thu, 6 Nov 2014 18:26:49 -0500
From: Peter Todd <pete@petertodd.org>
To: Justus Ranvier <justusranvier@riseup.net>
Message-ID: <20141106232649.GD26859@savin.petertodd.org>
References: <20141106213215.GA12918@savin.petertodd.org>
<A53D2C60-1D6A-4796-9776-3AF396BEC9F1@bitsofproof.com>
<545BF0C2.3030201@bluematt.me>
<CAJHLa0NTj6m4JpHx3+nWtYVV1Zpwf-FaxiyFX9DR821cQYVqsg@mail.gmail.com>
<545BFAD6.1000504@riseup.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="eheScQNz3K90DVRs"
Content-Disposition: inline
In-Reply-To: <545BFAD6.1000504@riseup.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 60df1fa1-660c-11e4-9f74-002590a135d3
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aAdMdgQUFloCAgsB AmIbWVdeUlt7XWQ7 bA9PbARUfEhLXhtr
VklWR1pVCwQmQm0H eH9EGktycAxBeXw+ Y0FgXT5dXBAsdBAs
Q1NSE21VeGZhPWQC WRZfcx5UcAFPdx8U a1N6AHBDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA43HjN0 SxEMEzQkAEkZVm00
IVQ5MF8AHUAeek41 N0AsX0kFKH1aARdf A0BGCSsRLF4NSnhj
EQNXFXU/Px10egdr OTwODTtlSjZPVUIA
X-Authentic-SMTP: 61633532353630.1024: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: 1XmWS6-0002sz-4o
Cc: bitcoin-development@lists.sourceforge.net
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 06 Nov 2014 23:26:55 -0000
--eheScQNz3K90DVRs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Nov 06, 2014 at 04:48:54PM -0600, Justus Ranvier wrote:
> Why not schedule protocol upgrades every two years for the foreseeable
> future?
For the same reason we don't do hard-forking upgrades of basically every
protocol on the planet on a regular basis, even when we don't have
consensus problems to worry about.
Flag days are really rare in engineering, and for good reason.
--=20
'peter'[:-1]@petertodd.org
000000000000000008f2290924a6882928d4566f487f33cc57203a6535795201
--eheScQNz3K90DVRs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJUXAO1XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwOGYyMjkwOTI0YTY4ODI5MjhkNDU2NmY0ODdmMzNjYzU3
MjAzYTY1MzU3OTUyMDEvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftxnQf9EcHdN2OiOwWdtY+pS/y8ofl9
ni2IExsG9d5MIYhQIek1QoJASUEPLNRr+C66cdDcqLKGfJtpkdWMzGD8kWyuPKZd
FH25MBHPb6HvwYKiisSpkZn1HpsKZu+xJT/ljQsbaiRGizgnj2BEFBelHvFVREwZ
xk5LuincpsNVLof7T3HU1MVlCMk7hhpNWT8eI5x6HsKUV396s9o0clmYqQ9/KQ9H
qEpEGdCNBggvFoojhJdkq1fIJTMDiKg0k91ZFdqUXxkBC//8KMlZXOHJVh8LrCcA
Xmyf03ozH6h3l/MxqGWzbTdT9uSQHddLToczjJqNDJ015i5HgdMieLueUEWqTw==
=OY7z
-----END PGP SIGNATURE-----
--eheScQNz3K90DVRs--
|
