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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1WnxmY-0008Uj-P1
for bitcoin-development@lists.sourceforge.net;
Fri, 23 May 2014 22:17:42 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.93 as permitted sender)
client-ip=62.13.148.93; envelope-from=pete@petertodd.org;
helo=outmail148093.authsmtp.net;
Received: from outmail148093.authsmtp.net ([62.13.148.93])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WnxmX-0000hP-BJ for bitcoin-development@lists.sourceforge.net;
Fri, 23 May 2014 22:17:42 +0000
Received: from mail-c237.authsmtp.com (mail-c237.authsmtp.com [62.13.128.237])
by punt14.authsmtp.com (8.14.2/8.14.2) with ESMTP id s4NMHZQf005380
for <bitcoin-development@lists.sourceforge.net>;
Fri, 23 May 2014 23:17:35 +0100 (BST)
Received: from petertodd.org (petertodd.org [174.129.28.249])
(authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id s4NMHRE6026749
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
for <bitcoin-development@lists.sourceforge.net>;
Fri, 23 May 2014 23:17:29 +0100 (BST)
Date: Fri, 23 May 2014 18:17:26 -0400
From: Peter Todd <pete@petertodd.org>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <20140523221726.GA30143@petertodd.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 07a3f39b-e2c8-11e3-9f74-002590a135d3
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVJwpGK10IU0Fd
P1hXKl1LNVAaWXld WiVPGEoXDxgzCjYj NEgGOBsDNw4AXQZ1
LRkAXVBSFQF4Ax8L BxkUURk8dgJCZn9y bFhgVm5ZWE1lcE56
XU8aVml4GB8CHWYf UkZfcwoacwZJeFFF bQF8AnAEM3hSZClo
WlZqMmt0bDsAdGEN GltQfAobGB1WEmUq Wx0ZATMiAQgeSig/
aRYnNlUbHUBXKkgu PEE9Xl4UdRgIBUVf BAlQGGdQKFAAQUIA
X-Authentic-SMTP: 61633532353630.1024:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 174.129.28.249/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1WnxmX-0000hP-BJ
Subject: [Bitcoin-development] testnet-seed.bitcoin.petertodd.org is up again
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: Fri, 23 May 2014 22:17:42 -0000
--2fHTh5uZTiUOsy+g
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
FWIW
That said, keep in mind the github discussion(1) that was had: if all
the DNS seeds being down breaks your application, your application is
broken and insecure. The only exception is initial startup, and even
then you should have fallbacks such as hardcoded node lists and manual
peer entry. If for some reason you really do need instant startup, run
your own centralized high-availability/low-latency nodes; either way
you're depending on a centralized resource.
1) https://github.com/bitcoin/bitcoin/pull/4203
--=20
'peter'[:-1]@petertodd.org
--2fHTh5uZTiUOsy+g
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBCAAGBQJTf8j2AAoJEBmcgzuo5/CFrb4H/jNiAaM9bitqOjvphX+kDa9g
DI49LTWoVkokAxrw4jo8hn7KCQ3s+EXCONm6GaZylHXt9p4XrqBRM/PhdwOPEVWL
G8757hy2MDqYpevw0Z0AqXgb9hqbep7ao/p/pGWOlkcpkBLm3x3/Gs2VlErTwlpC
22zHrpkOwiMGphE7hrhJoEft6V2I7lb7xzTWG0Y/f74q3BnrWuDCjixq0PZYK3MS
Jaiym7QIa1pbrJNuvp3gowT+QMoX2qv7213uVAYOfeuMtcIt1mxR2zvFXNLqLtc0
4NrGM9wkCjDR1Qy33RioPHrn8l+6eBF+VzQD/CqnaawBIj2NZ4vz0w+EsUz8VTk=
=MreJ
-----END PGP SIGNATURE-----
--2fHTh5uZTiUOsy+g--
|
