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
|
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 <jgarzik@exmulti.com>) id 1QW3YB-0004sI-Ft
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 09:35:15 +0000
X-ACL-Warn:
Received: from mail-iw0-f175.google.com ([209.85.214.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QW3Y7-0001Nk-0v
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 09:35:15 +0000
Received: by iwn19 with SMTP id 19so2568181iwn.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 13 Jun 2011 02:35:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.82.139 with SMTP id b11mr5179190ibl.134.1307956193048;
Mon, 13 Jun 2011 02:09:53 -0700 (PDT)
Received: by 10.231.19.203 with HTTP; Mon, 13 Jun 2011 02:09:53 -0700 (PDT)
X-Originating-IP: [99.173.148.118]
In-Reply-To: <BANLkTin_qs4bDabnu+b3K1hTzLzr4JKHsg@mail.gmail.com>
References: <BANLkTin_qs4bDabnu+b3K1hTzLzr4JKHsg@mail.gmail.com>
Date: Mon, 13 Jun 2011 05:09:53 -0400
Message-ID: <BANLkTimDGr-yX9zgS3qWPZALprWCsFieXg@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Christian Decker <decker.christian@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: 0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1QW3Y7-0001Nk-0v
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bootstrapping via BitTorrent trackers
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, 13 Jun 2011 09:35:15 -0000
On Mon, Jun 13, 2011 at 4:55 AM, Christian Decker
<decker.christian@gmail.com> wrote:
> We have quite a few bootstrapping mechanisms, starting with the overly
> complex (IMHO) IRC bootstrapping, which is often suspected as bot-activity.
> Then we have a few hardcoded nodes and some fallback nodes. I was wondering
> why we didn't adopt BitTorrent tracker bootstrapping until now? It's
> basically all it does. Given a hash (SHA1 hash of the genesis bloc would be
> nice ^^) it gives you a list of other nodes with the same hash.
It seems to offer few benefits over DNS seeding, while potentially
potentially creating a vulnerable hot spot in the DHT. Sybil attacks
on DHTs are well documented.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
