summaryrefslogtreecommitdiff
path: root/d3/f1f4843dcb5cfa6f76ff59382c004deb14aa4d
blob: ec1ef78c95960e87dfb210af5af65145a7b0ebb9 (plain)
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
Return-Path: <lf-lists@mattcorallo.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 019BD259
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  3 May 2017 22:03:47 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.bluematt.me (mail.bluematt.me [192.241.179.72])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 85117155
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed,  3 May 2017 22:03:46 +0000 (UTC)
Received: from [33.253.173.105] (unknown [172.56.19.65])
	by mail.bluematt.me (Postfix) with ESMTPSA id C88D413ABB7;
	Wed,  3 May 2017 22:03:44 +0000 (UTC)
Date: Wed, 03 May 2017 22:03:43 +0000
In-Reply-To: <CAAS2fgQYhi3oqncrNU+26E4JoHHfQMJAyTGtJY-ZD6J9O7NPsQ@mail.gmail.com>
References: <CAJowKg+snAUjbCFkTybNqiJCy=d_M3s5k376y1B=rVqD8WCOXA@mail.gmail.com>
	<CAAS2fgQYhi3oqncrNU+26E4JoHHfQMJAyTGtJY-ZD6J9O7NPsQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: Gregory Maxwell <greg@xiph.org>,
	Gregory Maxwell via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>,
	Erik Aronesty <erik@q32.com>
From: Matt Corallo <lf-lists@mattcorallo.com>
Message-ID: <AC8BC70A-D20E-4480-8414-49E2AF159423@mattcorallo.com>
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Full node "tip" function
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 03 May 2017 22:03:47 -0000

If we ever have a problem getting blocks, we could consider adding somethin=
g to pay to receive historical blocks but luckily that isn't a problem we h=
ave today - the available connection slots and bandwidth on the network tod=
ay appears to be more than sufficient to saturate nearly any fully-validati=
ng node=2E

On May 3, 2017 5:53:07 PM EDT, Gregory Maxwell via bitcoin-dev <bitcoin-de=
v@lists=2Elinuxfoundation=2Eorg> wrote:
>On Wed, May 3, 2017 at 9:08 PM, Erik Aronesty via bitcoin-dev
><bitcoin-dev@lists=2Elinuxfoundation=2Eorg> wrote:
>> CONS:
>
>The primary result would be paying people to sybil attack the network=2E
>It's far cheaper to run one node behind thousands of IPs than it is to
>run many nodes=2E
>
>Suggestions like this have come up many times before=2E
>_______________________________________________
>bitcoin-dev mailing list
>bitcoin-dev@lists=2Elinuxfoundation=2Eorg
>https://lists=2Elinuxfoundation=2Eorg/mailman/listinfo/bitcoin-dev