summaryrefslogtreecommitdiff
path: root/d5/2786ba50a3263ba4cfd40f5fd7fface9344583
blob: 412644d7c4b63c4c9a902f2bb2b1c48660b254e8 (plain)
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-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1QWAM1-0001b9-B9
	for bitcoin-development@lists.sourceforge.net;
	Mon, 13 Jun 2011 16:51:09 +0000
X-ACL-Warn: 
Received: from mail-iy0-f175.google.com ([209.85.210.175])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1QWAM0-0001PB-6w
	for bitcoin-development@lists.sourceforge.net;
	Mon, 13 Jun 2011 16:51:09 +0000
Received: by iye7 with SMTP id 7so5532089iye.34
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 13 Jun 2011 09:51:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.117.37 with SMTP id o37mr5700643ibq.184.1307983862907;
	Mon, 13 Jun 2011 09:51:02 -0700 (PDT)
Received: by 10.231.19.203 with HTTP; Mon, 13 Jun 2011 09:51:02 -0700 (PDT)
X-Originating-IP: [99.173.148.118]
In-Reply-To: <BANLkTikbQpU8+NMT_-f2mVNe-cGLY-ZeuQ@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>
	<BANLkTi=X4vZn_Oe6iYirp9++jwfXHJaqwg@mail.gmail.com>
	<BANLkTikbQpU8+NMT_-f2mVNe-cGLY-ZeuQ@mail.gmail.com>
Date: Mon, 13 Jun 2011 12:51:02 -0400
Message-ID: <BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Christian Decker <decker.christian@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: 1QWAM0-0001PB-6w
Cc: 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 16:51:09 -0000

On Mon, Jun 13, 2011 at 7:48 AM, Christian Decker
<decker.christian@gmail.com> wrote:
> The advantages over IRC and DNS Seeds are:
> =A0- sporadic HTTP requests to a tracker, as opposed to keeping an IRC
> connection open at all times

No advantage over DNS (you're talking about IRC)

> =A0- no virus/botnet like behaviour (automatically join IRC channel with
> cryptic name), ISPs tend to bother network admins (like myself) with aler=
ts
> when they see this...

No advantage over DNS (you're talking about IRC)

> =A0- adapts faster than DNS Seeds which require configuration changes on =
seed
> should the nodes become unreachable

False.  A proper DNS seed actively samples the bitcoin network for live nod=
es.

> =A0- we already use HTTP to determine our external IP, so it would be a
> consolidation of transports

Irrelevant -- it's still a bunch of additional code.  We "already use"
DNS lookups as well, so I could apply similar logic to DNS seeding.

> =A0- more peers than DNS Seeds (better load balancing)

This is an invalid assumption, based on an overly simplistic sampling.
 DNS seeds are perfectly capable of returning new and useful peers on
each query.

--=20
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com