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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WmMg3-00019l-Ow for bitcoin-development@lists.sourceforge.net; Mon, 19 May 2014 12:28:23 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.52 as permitted sender) client-ip=209.85.219.52; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f52.google.com; Received: from mail-oa0-f52.google.com ([209.85.219.52]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WmMg2-0001hn-Ss for bitcoin-development@lists.sourceforge.net; Mon, 19 May 2014 12:28:23 +0000 Received: by mail-oa0-f52.google.com with SMTP id eb12so6002810oac.25 for ; Mon, 19 May 2014 05:28:17 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.60.84.204 with SMTP id b12mr690935oez.8.1400502497435; Mon, 19 May 2014 05:28:17 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.71.162 with HTTP; Mon, 19 May 2014 05:28:17 -0700 (PDT) In-Reply-To: <5379F803.40509@gmail.com> References: <5379CE4D.5040100@gmail.com> <5379F803.40509@gmail.com> Date: Mon, 19 May 2014 14:28:17 +0200 X-Google-Sender-Auth: NQTkbvViVzAThR2_-lVJthOWOz8 Message-ID: From: Mike Hearn To: =?UTF-8?B?QmrDuHJuIMOYaXZpbmQgQmrDuHJuc2Vu?= Content-Type: multipart/alternative; boundary=089e01184b28dde86204f9bfe586 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1WmMg2-0001hn-Ss Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes 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: Mon, 19 May 2014 12:28:23 -0000 --089e01184b28dde86204f9bfe586 Content-Type: text/plain; charset=UTF-8 > > Does this mean that you can currently actively hurt the network by > adding a node with a very slow upstream / downstream? Well, I guess "hurting" the network is perhaps a bit dramatic. There are already lots of ways the download process can go wrong and take days. Using the torrent is much faster. But my understanding is that this will slow down the bootstrap process for some people yes. Remote peers won't try and download in parallel or anything like that. --089e01184b28dde86204f9bfe586 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Does this mean that you can curr= ently actively hurt the network by
adding a node with a very slow upstream / downstream?

=
Well, I guess "hurting" the network is perhaps a bit d= ramatic. There are already lots of ways the download process can go wrong a= nd take days. Using the torrent is much faster. But my understanding is tha= t this will slow down the bootstrap process for some people yes. Remote pee= rs won't try and download in parallel or anything like that.=C2=A0
--089e01184b28dde86204f9bfe586--