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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1VBDob-00030v-K3
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 00:59:25 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.43 as permitted sender)
client-ip=74.125.82.43; envelope-from=gavinandresen@gmail.com;
helo=mail-wg0-f43.google.com;
Received: from mail-wg0-f43.google.com ([74.125.82.43])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VBDoa-0001kx-OI
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Aug 2013 00:59:25 +0000
Received: by mail-wg0-f43.google.com with SMTP id z12so3044395wgg.22
for <bitcoin-development@lists.sourceforge.net>;
Sun, 18 Aug 2013 17:59:18 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.109.35 with SMTP id hp3mr6136699wib.52.1376873958555;
Sun, 18 Aug 2013 17:59:18 -0700 (PDT)
Received: by 10.194.156.163 with HTTP; Sun, 18 Aug 2013 17:59:18 -0700 (PDT)
In-Reply-To: <20130819001357.GA4281@savin>
References: <20130819001357.GA4281@savin>
Date: Mon, 19 Aug 2013 10:59:18 +1000
Message-ID: <CABsx9T3MFqmLchc1Uu20BhiVKsYWFtt0eneVSey846y2hdQ7Rg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary=e89a8f3ba25b33473804e44273f0
X-Spam-Score: -0.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
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1VBDoa-0001kx-OI
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bloom io attack effectiveness
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 Aug 2013 00:59:25 -0000
--e89a8f3ba25b33473804e44273f0
Content-Type: text/plain; charset=ISO-8859-1
Peter said:
"In any case given that SPV peers don't contribute back to the network
they should obviously be heavily deprioritized and served only with
whatever resources a node has spare."
This seems very much like a "cut off your nose to spite your face" solution.
SPV peers are INCREDIBLY IMPORTANT to the growth of Bitcoin; much more
important than nodes that have the bandwidth and disk I/O capability of
being a full node. Bitcoin will be just fine if there are never more than
10,000 big, beefy, full nodes forming the backbone of the network, but will
be NOTHING if we don't support tens of millions of lightweight SPV devices.
Ok, that's an exaggeration, Bitcoin would be just fine in an Electrum model
where tens of millions of lightweight devices rely 100% on a full node to
operate. But I would prefer the more decentralized, less-trust-required SPV
model.
--
--
Gavin Andresen
--e89a8f3ba25b33473804e44273f0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Peter said:<div>"<span style=3D"font-size:13px;font-f=
amily:arial,sans-serif">In any case given that SPV peers don't contribu=
te back to the network</span><br></div><div><span style=3D"font-family:aria=
l,sans-serif;font-size:13px">they should obviously be heavily deprioritized=
and served only with</span><br style=3D"font-family:arial,sans-serif;font-=
size:13px">
<span style=3D"font-family:arial,sans-serif;font-size:13px">whatever resour=
ces a node has spare."</span></div><div><font face=3D"arial, sans-seri=
f"><br></font></div><div><font face=3D"arial, sans-serif">This seems very m=
uch like a "cut off your nose to spite your face" solution.</font=
></div>
<div><font face=3D"arial, sans-serif"><br></font></div><div><div class=3D"g=
mail_extra"><font face=3D"arial, sans-serif">SPV peers are INCREDIBLY IMPOR=
TANT to the growth of Bitcoin; much more important than nodes that have the=
bandwidth and disk I/O capability of being a full node. =A0Bitcoin will be=
just fine if there are never more than 10,000 big, beefy, full nodes formi=
ng the backbone of the network, but will be NOTHING if we don't support=
tens of millions of lightweight SPV devices.</font></div>
<div class=3D"gmail_extra"><font face=3D"arial, sans-serif"><br></font></di=
v><div class=3D"gmail_extra"><font face=3D"arial, sans-serif">Ok, that'=
s an exaggeration, Bitcoin would be just fine in an Electrum model where te=
ns of millions of lightweight devices rely 100% on a full node to operate. =
But I would prefer the more decentralized, less-trust-required SPV model.<b=
r>
</font><div><br></div>-- <br>--<br>Gavin Andresen<br>
</div></div></div>
--e89a8f3ba25b33473804e44273f0--
|