Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1WmMvf-000661-Ud
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 12:44:32 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.169 as permitted sender)
	client-ip=209.85.223.169; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f169.google.com; 
Received: from mail-ie0-f169.google.com ([209.85.223.169])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WmMve-0002PQ-9f
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 12:44:31 +0000
Received: by mail-ie0-f169.google.com with SMTP id at1so2234001iec.14
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 19 May 2014 05:44:24 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.50.231 with SMTP id f7mr16206352igo.42.1400503464466;
	Mon, 19 May 2014 05:44:24 -0700 (PDT)
Received: by 10.64.22.168 with HTTP; Mon, 19 May 2014 05:44:24 -0700 (PDT)
In-Reply-To: <5379CE4D.5040100@gmail.com>
References: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
	<5379CE4D.5040100@gmail.com>
Date: Mon, 19 May 2014 14:44:24 +0200
Message-ID: <CA+s+GJCzks9RRi8HgFbPJ+zmuona26QCpYX8Eax+Qg6WmDd2fQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: =?UTF-8?B?QmrDuHJuIMOYaXZpbmQgQmrDuHJuc2Vu?= <bo.bjornsen@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
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
	(laanwj[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	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: 1WmMve-0002PQ-9f
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <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: Mon, 19 May 2014 12:44:33 -0000

On Mon, May 19, 2014 at 11:26 AM, Bj=C3=B8rn =C3=98ivind Bj=C3=B8rnsen
<bo.bjornsen@gmail.com> wrote:
> On 18/05/14 19:43, Ra=C3=BAl Mart=C3=ADnez wrote:
>> <snip some good ideas>
>
> As an interested party not intimately familiar with the bitcoin codebase
> who also spent some time setting up a node a while ago, I would like to
> add one thing to the above list - network rate limiting.

There is already an (old) patch that implements that. It won't be
merged, though, until headers-first and parallel block download is in.
Only when the node can download blocks from multiple peers at once it
is really safe to allow limiting rates.

(sure - there are tricks to limit rates anyway, like the script in
contrib/qos, but to have it generally available the block download
needs to be more robust first)

Wladimir