blob: 27b74015e1d00dfb2b4c919359074ee5cabbd08f (
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1QWC56-0005vG-8N
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 18:41:48 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.216.175 as permitted sender)
client-ip=209.85.216.175; envelope-from=gavinandresen@gmail.com;
helo=mail-qy0-f175.google.com;
Received: from mail-qy0-f175.google.com ([209.85.216.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QWC55-0005fa-JP
for bitcoin-development@lists.sourceforge.net;
Mon, 13 Jun 2011 18:41:48 +0000
Received: by qyk35 with SMTP id 35so1263424qyk.13
for <bitcoin-development@lists.sourceforge.net>;
Mon, 13 Jun 2011 11:41:42 -0700 (PDT)
Received: by 10.229.22.138 with SMTP id n10mr4112703qcb.175.1307990502101;
Mon, 13 Jun 2011 11:41:42 -0700 (PDT)
Received: from [10.241.208.137] (66.sub-174-252-35.myvzw.com [174.252.35.66])
by mx.google.com with ESMTPS id
j18sm4720670qck.27.2011.06.13.11.41.39
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 13 Jun 2011 11:41:40 -0700 (PDT)
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>
<BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com>
<BANLkTi=XUxZOXP-U8swyfBuu7ntjo6VyUg@mail.gmail.com>
In-Reply-To: <BANLkTi=XUxZOXP-U8swyfBuu7ntjo6VyUg@mail.gmail.com>
Mime-Version: 1.0 (iPhone Mail 8E401)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
Message-Id: <329684AF-0A85-4116-A191-72562ADB9BE7@gmail.com>
X-Mailer: iPhone Mail (8E401)
From: Gavin <gavinandresen@gmail.com>
Date: Mon, 13 Jun 2011 14:41:35 -0400
To: Vladimir Marchenko <vladimir@marchenko.co.uk>
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is freemail (gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.0 RFC_ABUSE_POST Both abuse and postmaster missing on sender domain
X-Headers-End: 1QWC55-0005fa-JP
Cc: "bitcoin-development@lists.sourceforge.net"
<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 18:41:48 -0000
> 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. =
I'd be happy to run a dns seed.=
|
