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
117
118
119
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>)
id 1UFMH5-00049A-6D; Tue, 12 Mar 2013 10:17:39 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.149.112 as permitted sender)
client-ip=62.13.149.112; envelope-from=pete@petertodd.org;
helo=outmail149112.authsmtp.co.uk;
Received: from outmail149112.authsmtp.co.uk ([62.13.149.112])
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1UFMH2-0001ex-Qz; Tue, 12 Mar 2013 10:17:39 +0000
Received: from mail-c226.authsmtp.com (mail-c226.authsmtp.com [62.13.128.226])
by punt12.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id
r2CAHTTF037156; Tue, 12 Mar 2013 10:17:29 GMT
Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r2CAHO8J020507
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Tue, 12 Mar 2013 10:17:26 GMT
Date: Tue, 12 Mar 2013 06:17:24 -0400
From: Peter Todd <pete@petertodd.org>
To: Mike Hearn <mike@plan99.net>
Message-ID: <20130312101724.GA22309@savin>
References: <CAPg+sBip_4Jtxhq+rm-na2=RSJ_PuoZt+akGgJyo0b_Bwbr1Dw@mail.gmail.com>
<CAPg+sBjm+e=A+edSRHXU7JSqyfSc4hou_SRdQHF48xhKQGA4zA@mail.gmail.com>
<CANEZrP2V9uDQ-dmyaUBbsCuj5u3Mrh+jvU9RDpYkrKQV6+t0tQ@mail.gmail.com>
<20130312095749.GB8130@savin>
<CANEZrP3KunGQSnmKxOBcuCNH=c1aHG_Yj=Ea_-HwkR5DP1eooA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh"
Content-Disposition: inline
In-Reply-To: <CANEZrP3KunGQSnmKxOBcuCNH=c1aHG_Yj=Ea_-HwkR5DP1eooA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 0a81a289-8afe-11e2-98a9-0025907ec6c5
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
bgdMdwAUFVQGAgsB AmUbWlReUVp7W2Q7 bAxPbAVDY01GQQRq
WVdMSlVNFUsqA29w fmEWKBlwdwBGfzBx ZkZgXj5bDUx7JER1
S1NcRDtTeGZhPWIC WUgJfh5UcAFPdx9C PwN5B3ZDAzANdhES
HhM4ODE3eDlSNilR RRkIIFQOdA40FyQ6 RhYNT30qFEsUD311
cFQgLVIRBw4bKEg7 MhMmXxocOgUdB28W GVxICiJDb14PDzY7
SgleWkUdQ3VTRj1f SgcpORwg
X-Authentic-SMTP: 61633532353630.1020:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 76.10.178.109/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: 1UFMH2-0001ex-Qz
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
bitcoin-security@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Warning: many 0.7 nodes break on large
number of tx/block; fork risk
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: Tue, 12 Mar 2013 10:17:39 -0000
--jI8keyz6grp/JLjh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Mar 12, 2013 at 11:10:47AM +0100, Mike Hearn wrote:
> However, most nodes are not running in such a loop today. Probably
> almost no nodes are.
>=20
> I suppose you could consider mass node death to be more benign than a
> hard fork, but both are pretty damn serious and warrant immediate
> action. Otherwise we're going to see the number of nodes drop sharply
> over the coming days as unattended nodes die and then don't get
> restarted.
I'm sure if "mass node death" becomes an issue miners will have plenty
of incentive to temporarily, or permanently, setup some high-memory and
high-bandwidth nodes to accept transactions. The DNS seeds sort by
reliability so it won't be long before nodes are connecting to them.
My home machine has 16GB of ram, bigger than the whole blockchain.
--=20
'peter'[:-1]@petertodd.org
--jI8keyz6grp/JLjh
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJRPwCzAAoJEH+rEUJn5PoEkc0IAIgdkF9qvoDG5DVW0uJCp7SF
E1wvDK4+xkCP/RJNnlGsIuiDkOp7G+EHnq8+V6qaPoKp4zfTZ7Dfh/1KOaGKOm+q
rKxp5cv1QJMu+Qu6Sa2ady6yeHrO2oH4PTcBqyVL0VI/FW8iFMcMacmaE1Za/kiC
xFS0oWwOm0mAUWqCUj0P35VafdjtFy990G5+mMOh3Wj1P3A1aaE4A9vL01ioUwp5
Qwkcy/8i+oV50P3Gs8wDDs08lEYE+e+mt3lXHZVeI07QNTrO4V2RfxywLkMAX1GN
7gafavrrECIPbbwgjIedQb9NvRBCP2VHTAZ+r7Ts/MPmqv2I+9GhJLagtrTutvU=
=HIaX
-----END PGP SIGNATURE-----
--jI8keyz6grp/JLjh--
|
