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
119
120
121
122
123
124
125
126
127
128
|
Return-Path: <odinn.cyberguerrilla@riseup.net>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 56A8B84
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 05:21:18 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DBD4D132
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 19 Aug 2015 05:21:16 +0000 (UTC)
Received: from cotinga.riseup.net (unknown [10.0.1.161])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(Client CN "*.riseup.net",
Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
by mx1.riseup.net (Postfix) with ESMTPS id 70778C1047;
Tue, 18 Aug 2015 22:21:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
t=1439961676; bh=TJSTNIVhQmjscmnRrrK03xNjutCwBAkvDEqmq/AjXsg=;
h=Date:From:To:CC:Subject:References:In-Reply-To:From;
b=HofzZ5R2suyhBlYpTKVb4gMMEDYUzBPhoX07Tp2JGwTBROuaSgiOXKnuo96aOWI+w
0Tkzls7p9AYBM7J7fwoP4J1KhH8ntH6KwP4vKfrRxLl0T63VgU/IDUrQ9IKlFzOsCT
hw1NpjXxsBZaZXJJBLvJVQoiqPpOIGJN1YS26V/0=
Received: from [127.0.0.1] (localhost [127.0.0.1])
(Authenticated sender: odinn.cyberguerrilla)
with ESMTPSA id CC8331C0258
Message-ID: <55D4124B.6070700@riseup.net>
Date: Tue, 18 Aug 2015 22:21:15 -0700
From: odinn <odinn.cyberguerrilla@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Chris Pacia <ctpacia@gmail.com>, Peter Todd <pete@petertodd.org>
References: <6EC9DDF352DC4838AE9B088AB372428A25E1F42A@DS04> <20150817212912.GA15817@muck>
<CAB+qUq79BgiTGFS1yLxxogg8907jCUtNDmBhnikLWc1fqofNyg@mail.gmail.com>
In-Reply-To: <CAB+qUq79BgiTGFS1yLxxogg8907jCUtNDmBhnikLWc1fqofNyg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, RCVD_IN_DNSWL_LOW, RP_MATCHES_RCVD,
UNPARSEABLE_RELAY autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Incentives to run full nodes
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 19 Aug 2015 05:21:18 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Potentially relevant...
"Incentivizing the running of full nodes"
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2014-June/006028
.html
(However, the issue to which I referred here is now closed)
View whole thread:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2014-June/thread
.html#6028
On 08/17/2015 02:44 PM, Chris Pacia via bitcoin-dev wrote:
>
> On Aug 17, 2015 5:29 PM, "Peter Todd via bitcoin-dev"
> <bitcoin-dev@lists.linuxfoundation.org
> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote: From the
> point of view of a
>> wallet, it's not very secure to use Hearn-style SPV mode, and
>> volunteers running full nodes doesn't help things. Sybil
>> attacking the IP address space is pretty easy in comparison to
>> aquiring hashing power sufficient to create false confirmations,
>> so any attacker able to do the former will likely be running the
>> full node you're connecting too anyway. Ultimately, Hearn-style
>> SPV is a close approximation to just trusting anyone with a
>> non-trivial amount of hashing power. (and getting that is
>> surprisingly easy, e.g. w/ SPV mining)
>
> Can you explain how the spv node fails against an attacker with a
> non-trivial amount of hash power where a full node doesn't? To
> attack an spv wallet that is waiting for 6 or 10 confirmations, you
> would not only need to Sybil them but also summon a massive amount
> of hashing power to create a chain of headers (while forgoing the
> opportunity to mine valid blocks with that hash power).
>
> But could someone with that much hash power not Sybil a full node
> and give them a chain for valid blocks (but on an orphan fork)? The
> failure model doesn't seem specific to spv to me.
>
>
>
> _______________________________________________ bitcoin-dev mailing
> list bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJV1BJLAAoJEGxwq/inSG8CUAoH/3SwFKxhRBFA8SFAj7ia2Af8
ITEOkLyNM23lxW4yUdHhxtPiHbvXDXctZ9LESgp39kmE3MEYZW7IhcmJ7WRBNNVq
sTXANa5B/o+LwYbVDdS8Rt/p8dTs+xxPWreuycLJFwoOFbhbqp8wFqdJvZb/w45F
MSTBeXUOVr65sBW5zSrindGxCzmi33b9FoTWHdZ0wQtyDInk3goixWFRJ5n95/nI
msA8iIDvPQBv0naXR9/3CiEvJz274TSBvlvhOR5IBKTv9pxamX/fjWDUe/Z6uyg1
3469EtimDb+BVhlEvcPPJBOwAOKQnRLdi2N4xVg+2csFtknBkc45uuxjvaq/yis=
=75Cp
-----END PGP SIGNATURE-----
|
