From: Jeff Garzik <jgarzik@exmulti•com>
To: Gavin <gavinandresen@gmail•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bootstrapping via BitTorrent trackers
Date: Mon, 13 Jun 2011 16:16:14 -0400 [thread overview]
Message-ID: <BANLkTi=iOeVUJ7ktwWddH1heiNmyn5v52w@mail.gmail.com> (raw)
In-Reply-To: <329684AF-0A85-4116-A191-72562ADB9BE7@gmail.com>
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
prev parent reply other threads:[~2011-06-13 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 8:55 Christian Decker
2011-06-13 9:09 ` Jeff Garzik
2011-06-13 9:38 ` Christian Decker
2011-06-13 9:56 ` Jeff Garzik
2011-06-13 10:54 ` Vladimir Marchenko
2011-06-13 11:48 ` Christian Decker
2011-06-13 16:51 ` Jeff Garzik
2011-06-13 18:00 ` Vladimir Marchenko
2011-06-13 18:41 ` Gavin
2011-06-13 20:16 ` Jeff Garzik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=iOeVUJ7ktwWddH1heiNmyn5v52w@mail.gmail.com' \
--to=jgarzik@exmulti$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gavinandresen@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox