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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1QWDYa-0008Ik-Q4
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 20:16:20 +0000
X-ACL-Warn:
Received: from mail-iw0-f175.google.com ([209.85.214.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QWDYZ-0000ZM-Lu
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 20:16:20 +0000
Received: by iwn19 with SMTP id 19so3248689iwn.34
for <bitcoin-development@lists.sourceforge.net>;
Mon, 13 Jun 2011 13:16:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.117.37 with SMTP id o37mr5854472ibq.184.1307996174160;
Mon, 13 Jun 2011 13:16:14 -0700 (PDT)
Received: by 10.231.19.203 with HTTP; Mon, 13 Jun 2011 13:16:14 -0700 (PDT)
X-Originating-IP: [99.173.148.118]
In-Reply-To: <329684AF-0A85-4116-A191-72562ADB9BE7@gmail.com>
References: <BANLkTin_qs4bDabnu+b3K1hTzLzr4JKHsg@mail.gmail.com>
<BANLkTimDGr-yX9zgS3qWPZALprWCsFieXg@mail.gmail.com>
<BANLkTi=oYjydw7sT=sqSN3sHMhM+pq=c6w@mail.gmail.com>
<BANLkTikNd6rqssQ1bHGhPURc7tiXLkBGwQ@mail.gmail.com>
<BANLkTi=X4vZn_Oe6iYirp9++jwfXHJaqwg@mail.gmail.com>
<BANLkTikbQpU8+NMT_-f2mVNe-cGLY-ZeuQ@mail.gmail.com>
<BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com>
<BANLkTi=XUxZOXP-U8swyfBuu7ntjo6VyUg@mail.gmail.com>
<329684AF-0A85-4116-A191-72562ADB9BE7@gmail.com>
Date: Mon, 13 Jun 2011 16:16:14 -0400
Message-ID: <BANLkTi=iOeVUJ7ktwWddH1heiNmyn5v52w@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Gavin <gavinandresen@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: 1QWDYZ-0000ZM-Lu
Cc: "bitcoin-development@lists.sourceforge.net"
<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 20:16:20 -0000
On Mon, Jun 13, 2011 at 2:41 PM, Gavin <gavinandresen@gmail.com> wrote:
>> The most practical way I see how to improve DNS bootstrapping is
>> publishing build instructions for a simple DNS server build and a
>> script which feeds it with node data. Something simple like djbdns plus
>> a perl script, or similar zerigo API script, would do. Than anyone can
>> host it. All left to do than is to hardcode a bunch of such DNS seeds
>> into the client.
>
> Adding that code to bitcoin in a contrib/dns folder seems like a good idea.
Agreed. I'll see if I can put together a couple different solutions,
and stick them in there. ETA 3-4 weeks though, given current bugfix
workload + personal issues (moving to a new house).
I had a thought related to this, but readily admit I haven't thought
this through: create an RPC in bitcoin that returns a random
selection of fresh P2P node addresses, from addr.dat. One problem I
was running into was accessing this data from outside bitcoin.
Using ArtForz' half-a-node as a base was a possibility, but creating
"getnodes" RPC seemed far easier.
djbdns (tinydns) is great for this: it is highly scalable and stable,
and its input is a -very- simple text format, easier to generate than
BIND zone files.
> I'd be happy to run a dns seed.
Great! A big missing piece is simply trusted people running DNS seeds
on stable connectivity, once the DNS software is there.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
