From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TzUs0-0002hD-IM for bitcoin-development@lists.sourceforge.net; Sun, 27 Jan 2013 16:14:12 +0000 X-ACL-Warn: Received: from mail-pa0-f43.google.com ([209.85.220.43]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TzUrw-0005j3-Rm for bitcoin-development@lists.sourceforge.net; Sun, 27 Jan 2013 16:14:12 +0000 Received: by mail-pa0-f43.google.com with SMTP id fb10so1069537pad.2 for ; Sun, 27 Jan 2013 08:14:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=5jU2Z3CXh/jVQrn+rPwvmJagi3YNIBWcE7/02qVdsMY=; b=bmvq8Z/u/UHQ3NlBbj9WUIA9jxAnJ0HqiC5RPWmSRbVyYQusoklksVv+/rNvubfgVK ywnroGenbOTRMxQP5OVp/phXe1KJxRi6rLUJKMJAs0MnEGeGN/nTcxvqSu4MsQuiJ5Be qGEEAZVWJCcvUbUvUUl1KI1BDgl/BUjxV5zh7yp/8CrDNpNZGAlekSB8XA1HN6tcJMlc dXBUBLZSTDs/bBcwxSvXlz+M0KkNs/1KZ52Cc4eamzryMHusTO921USzOfBc6gJrECm+ Z57nWE/q3KteuZh+hI2OxJ4+te1vjX3kKjuVrUp4NEqKgRzpZw7ufKfKM3vClITOGWMK UXSQ== MIME-Version: 1.0 X-Received: by 10.68.238.136 with SMTP id vk8mr30829382pbc.86.1359303242879; Sun, 27 Jan 2013 08:14:02 -0800 (PST) Received: by 10.68.129.199 with HTTP; Sun, 27 Jan 2013 08:14:02 -0800 (PST) X-Originating-IP: [2001:4830:1603:2:21c:c0ff:fe79:c8c2] In-Reply-To: <20130127102752.GA7134@savin> References: <20130124070103.GA30820@savin> <20130127102752.GA7134@savin> Date: Sun, 27 Jan 2013 11:14:02 -0500 Message-ID: From: Jeff Garzik To: Peter Todd Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQn5ne9+rMoxvr4fB3/YPqirhWcMwuDdoZsOSEELiq6+XT4uFieUC+kBwVnIYyoy1DxAjdcJ X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1TzUrw-0005j3-Rm Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Testnet DNS seed X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 16:14:12 -0000 On Sun, Jan 27, 2013 at 5:27 AM, Peter Todd wrote: > On Fri, Jan 25, 2013 at 09:23:28PM -0500, Jeff Garzik wrote: >> On Thu, Jan 24, 2013 at 2:01 AM, Peter Todd 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. Cool. ACK on adding your seed to the ref client. >> > 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 Correct. > 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?) That's fine. The main point was to create something scripted and repeatable. Then pnSeed[] becomes easier to maintain _and_ easier to audit. Right now it is a bit opaque with a list of hex constants. A script or makefile rule could do cd src ../contrib/gen-seeds.py > seeds.h and seeds might look like #ifndef __SEEDS_AUTOGEN_H__ etc. unsigned int pnSeed[] = { 0xABCD1234, /* IP addr 12.34.56.78 */ }; I think Satoshi liked them opaque and not easily searchable, so printing the readable IP address in a comment may not be desired. Anyway, that output would make updating the list more transparent and easy to maintain. -- Jeff Garzik exMULTI, Inc. jgarzik@exmulti.com