From: Jeff Garzik <jgarzik@exmulti.com>
To: Christian Decker <decker.christian@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bootstrapping via BitTorrent trackers
Date: Mon, 13 Jun 2011 05:09:53 -0400 [thread overview]
Message-ID: <BANLkTimDGr-yX9zgS3qWPZALprWCsFieXg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin_qs4bDabnu+b3K1hTzLzr4JKHsg@mail.gmail.com>
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
next prev parent reply other threads:[~2011-06-13 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 8:55 [Bitcoin-development] Bootstrapping via BitTorrent trackers Christian Decker
2011-06-13 9:09 ` Jeff Garzik [this message]
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
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=BANLkTimDGr-yX9zgS3qWPZALprWCsFieXg@mail.gmail.com \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=decker.christian@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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