public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Testnet DNS seed
Date: Sun, 27 Jan 2013 05:27:52 -0500	[thread overview]
Message-ID: <20130127102752.GA7134@savin> (raw)
In-Reply-To: <CA+8xBpdMV5qyZdXHsHoQFNLHzuxXKAFJd096Bv5RPnMX=CWgug@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

On Fri, Jan 25, 2013 at 09:23:28PM -0500, Jeff Garzik wrote:
> 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]?

Indefinitely. It's a pretty cheap thing to run, about $7.5/month. If
anyone else wants I can give them a machine image copy easily too.

> > 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[]

seed.txt? You mean the dumpfile produced by bitcoin-seeder? That has
uptime info, although only a months worth if I understand it correctly.

pnSeed probably should be filtered with SORB's dynamic ip list or
similar too, and additionally add an expiry time. (1 year?)

-- 
'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-01-27 10:28 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
2013-01-27 10:27   ` Peter Todd [this message]
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=20130127102752.GA7134@savin \
    --to=pete@petertodd.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@exmulti.com \
    /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