From: Peter Todd <pete@petertodd•org>
To: Mike Hearn <mike@plan99•net>
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
Date: Tue, 12 Mar 2013 06:17:24 -0400 [thread overview]
Message-ID: <20130312101724.GA22309@savin> (raw)
In-Reply-To: <CANEZrP3KunGQSnmKxOBcuCNH=c1aHG_Yj=Ea_-HwkR5DP1eooA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
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.
>
> 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.
--
'peter'[:-1]@petertodd.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-03-12 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 0:18 Pieter Wuille
2013-03-12 1:01 ` Pieter Wuille
2013-03-12 9:10 ` Mike Hearn
2013-03-12 9:53 ` Jorge Timón
2013-03-12 9:57 ` Peter Todd
2013-03-12 10:10 ` Mike Hearn
2013-03-12 10:17 ` Peter Todd [this message]
2013-03-12 10:13 ` Michael Gronager
2013-03-12 10:26 ` Peter Todd
2013-03-12 10:43 ` Mike Hearn
2013-03-12 10:40 ` Roy Badami
2013-03-12 11:44 ` Pieter Wuille
2013-03-12 12:11 ` Mike Hearn
2013-03-12 12:27 ` Michael Gronager
2013-03-12 12:18 ` Jorge Timón
2013-03-12 12:40 ` Jay F
2013-03-12 12:38 ` Gregory Maxwell
2013-03-12 13:00 ` Michael Gronager
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130312101724.GA22309@savin \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-security@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox