From: Jeff Garzik <jgarzik@exmulti.com>
To: Peter Todd <pete@petertodd.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Testnet DNS seed
Date: Fri, 25 Jan 2013 21:23:28 -0500 [thread overview]
Message-ID: <CA+8xBpdMV5qyZdXHsHoQFNLHzuxXKAFJd096Bv5RPnMX=CWgug@mail.gmail.com> (raw)
In-Reply-To: <20130124070103.GA30820@savin>
On Thu, Jan 24, 2013 at 2:01 AM, Peter Todd <pete@petertodd.org> wrote:
> Everything is running on a dedicated Amazon EC2 micro instance. Just
> IPv4 is supported right now as EC2 doesn't support IPv6; even tunnels
> are broken. I also haven't setup tor yet. I can do both if there is
> demand.
How long do you plan to run this? Indefinitely [presuming there is
interest and users]?
> I guess the next step is to create a new strTestNetDNSSeed in the
> satoshi client, although it'd be better if at least one more person had
No objection
> a testnet seed to include in the list. Probably best to leave IRC
> enabled too.
Yes, IRC must remain enabled
> Also, FWIW, it looks like the pnSeed list is way out of date...
Yes. Usually nanotube does the update when poked. That can happen,
or something different.
A nice alternative might be a simple script that transforms Pieter's
seeds.txt into pnSeed[]
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next prev parent reply other threads:[~2013-01-26 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 7:01 [Bitcoin-development] Testnet DNS seed Peter Todd
2013-01-26 2:23 ` Jeff Garzik [this message]
2013-01-27 10:27 ` Peter Todd
2013-01-27 16:14 ` Jeff Garzik
2013-01-27 16:18 ` Pieter Wuille
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='CA+8xBpdMV5qyZdXHsHoQFNLHzuxXKAFJd096Bv5RPnMX=CWgug@mail.gmail.com' \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=pete@petertodd.org \
/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