Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.47 as permitted sender)
	client-ip=209.85.216.47; envelope-from=vmartchenko@gmail.com;
	helo=mail-qw0-f47.google.com; 
MIME-Version: 1.0
Sender: vmartchenko@gmail.com
In-Reply-To: <BANLkTikNd6rqssQ1bHGhPURc7tiXLkBGwQ@mail.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>
Date: Mon, 13 Jun 2011 11:54:16 +0100
Message-ID: <BANLkTi=X4vZn_Oe6iYirp9++jwfXHJaqwg@mail.gmail.com>
From: Vladimir Marchenko <vladimir@marchenko.co.uk>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bootstrapping via BitTorrent trackers
Precedence: list

one possible bootstrap method of last resort,

1. create a convention of bitcoind listening on a specific last octest
of IPv4 address, let's say, .14 when possible. Those of us who have
access to IP space would use .14's.

2. if no other bootstrap method works, client could start scanning
x.x.x.14 addresses, perhaps in some semi-intelligent order (starting
from more pobable /8's and /16's), if enough people place bitcoind on
x.x.x.14 than after a 10-100 thousand checks it bound to find a
bitcoind peer.

It's messy, with all the excessive scanning etc... but it does not
depend on anything except a bunch of bitcoind by convention preferring
listening on x.x.x.14's.

Given that this is a method of last resort in bootrap chain it whould
hopefully not lead to DDOS on those unlucky to own *.14 and not
running bitcoind there. Also the more people are running bitcoind on
.14, the quicker it would find a peer, the less scanning to do. It is
kind of self-regualting.

For whatever it worth...


On 13 June 2011 10:56, Jeff Garzik <jgarzik@exmulti.com> wrote:
> On Mon, Jun 13, 2011 at 5:38 AM, Christian Decker
> <decker.christian@gmail.com> wrote:
>> BitTorrent trackers are used to handle several thousands of requests, so
>> they would probably scale well enough. I'm not even talking about using =
the
>> DHT trackers, but using old fashioned HTTP based trackers. The fact that
>> each bitcoin client would contact the tracker would make it very hard fo=
r an
>> attacker to get bootstrapping clients to exclusively connect to his
>> compromised clients. I would say that using a tracker such as OpenBittor=
rent
>> provides the same advantages as using an IRC channel.
>
> And how does the client discover HTTP trackers? =C2=A0You're either
> hardcoding -those- into the client, or adding an additional bootstrap
> step to discover them. =C2=A0Either way, it has the same problems as othe=
r
> current methods.
>
> The history and experience of gnutella's web caches vs. UDP host
> caches seems highly relevant here.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik@exmulti.com
>
> -------------------------------------------------------------------------=
-----
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>