From: Vladimir Marchenko <vladimir@marchenko•co.uk>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bootstrapping via BitTorrent trackers
Date: Mon, 13 Jun 2011 19:00:59 +0100 [thread overview]
Message-ID: <BANLkTi=XUxZOXP-U8swyfBuu7ntjo6VyUg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com>
Jeff is absolutely correct, stating that DNS bootstrapping can
potentially be very robust.
Consider, for example, that seeds can be hosted by services like
zerigo, who provide decent management API's, as well as by thousands
of small VPS operated by people all over the world. Moreover, if
namecoin lives up to it's promises than some seeds can be hosted using
it's tlds, and as such we would get around centralised ICANN/registrar
weakness.
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.
Hardcoding seeds is not good enough? Get a convention that anyone
owning a bitcoin.* domain should point seed.bitcoin.* to a decent DNS
seed. Than clients simply scan 100-200 tld's to find working
seed.bitcoin.*
I am not quite sure, though, is if this would enable some attacks by
poisoned seeds.
Vladimir.
next prev parent reply other threads:[~2011-06-13 18:01 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 [this message]
2011-06-13 18:41 ` Gavin
2011-06-13 20:16 ` Jeff Garzik
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=XUxZOXP-U8swyfBuu7ntjo6VyUg@mail.gmail.com' \
--to=vladimir@marchenko$(echo .)co.uk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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