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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1Rc6B0-0005Rk-0q
for bitcoin-development@lists.sourceforge.net;
Sun, 18 Dec 2011 02:08:34 +0000
X-ACL-Warn:
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Rc6Az-0008PT-3G
for bitcoin-development@lists.sourceforge.net;
Sun, 18 Dec 2011 02:08:33 +0000
Received: by vcbf1 with SMTP id f1so3298715vcb.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 17 Dec 2011 18:08:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.91.109 with SMTP id cd13mr8903182vdb.92.1324170475374; Sat,
17 Dec 2011 17:07:55 -0800 (PST)
Received: by 10.52.178.167 with HTTP; Sat, 17 Dec 2011 17:07:55 -0800 (PST)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <4EED378A.8090303@parhelic.com>
References: <CABr1YTebhitO4g-SarZ7H=aoG9a8zW1wd0rfR32o8i0vODbLJw@mail.gmail.com>
<82659F61-0449-47BB-88DC-497E0D02F8A1@ceptacle.com>
<CALxbBHUXEJLRDZ=RS1vuvkm7rDjFUPir0sU__f6TJXiTTQxWzA@mail.gmail.com>
<CABsx9T0puk3CWH1cfNHMSVEoCPaLJJWNJ+H5ObCERZrzMbrTyA@mail.gmail.com>
<CABsx9T06-GA5+KNdr_XzP_M4Av8nEsnMXL29tk078wooZg=RZw@mail.gmail.com>
<1324158558.26106.140661012932641@webmail.messagingengine.com>
<4EED378A.8090303@parhelic.com>
Date: Sat, 17 Dec 2011 20:07:55 -0500
Message-ID: <CA+8xBpc5ke2W7kc8NQr6nWrvNmB-AmBTC2uTTW3H+KqJLUpBcg@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Jordan Mack <jordanmack@parhelic.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Rc6Az-0008PT-3G
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Protocol extensions
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: Sun, 18 Dec 2011 02:08:34 -0000
On Sat, Dec 17, 2011 at 7:44 PM, Jordan Mack <jordanmack@parhelic.com> wrote:
> While using DHT for storage of the block chain is an intriguing concept,
> I do not see how it is feasible. As Gavin noted, DHT is a system that is
> difficult to impossible to guarantee against data loss or manipulation.
>
> Even if we found a way to store the block chain in DHT, how would
> transactions be verified? As Gavin noted, you could ask the network, but
> cannot necessarily trust the peers you are connected to. Verification of
> the full block chain allows the client to trust no one.
Well, the block chain data itself is internally self-validating. As
long as you know the latest block's hash -- a big "if" -- there is no
problem downloading all other block chain data from DHT or any other
untrusted source.
In a malicious case, you would notice latest-hash differs from
non-malicious and wind up downloading multiple chains, when walking
hashes backwards through a DHT/lookup table. So, a bit more work but
nothing fundamentally less secure _on a trust basis_.
Of course, I was focusing on data validation, which ignores other
factors such as DoS'ing the DHT.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|