Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SjoV4-0006Ms-2b for bitcoin-development@lists.sourceforge.net; Wed, 27 Jun 2012 09:25:26 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.169 as permitted sender) client-ip=209.85.212.169; envelope-from=grarpamp@gmail.com; helo=mail-wi0-f169.google.com; Received: from mail-wi0-f169.google.com ([209.85.212.169]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SjoV0-00015t-6o for bitcoin-development@lists.sourceforge.net; Wed, 27 Jun 2012 09:25:26 +0000 Received: by wibhm2 with SMTP id hm2so1786221wib.4 for ; Wed, 27 Jun 2012 02:25:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.82.42 with SMTP id f10mr3064528wiy.22.1340789116027; Wed, 27 Jun 2012 02:25:16 -0700 (PDT) Received: by 10.180.7.105 with HTTP; Wed, 27 Jun 2012 02:25:15 -0700 (PDT) In-Reply-To: References: <20120626141129.GA30240@vps7135.xlshosting.net> <4FEAA936.10300@infosecurity.ch> Date: Wed, 27 Jun 2012 05:25:15 -0400 Message-ID: From: grarpamp To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.0 (-) 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 commonly abused enduser mail provider (grarpamp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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.6 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SjoV0-00015t-6o Subject: Re: [Bitcoin-development] [tor-talk] Tor hidden service support 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: Wed, 27 Jun 2012 09:25:26 -0000 GregM, wasn't sure how to answer your question, and as to conflicts [1]. I think I grasped it in my reply to something on tor-talk, which is on its way here pending moderation due to bcc. I put that part below. The FYI referred to seednodes as they exist on Tor / I2P today. > You are going to want to include the block of the Phatom project as well: >> https://code.google.com/p/phantom/ >> fd00:2522:3493::/48 > Perhaps some argument to add blocks to the IsRoutable check is in > order? Then people who use overlay networks that are actually > routable but which use otherwise private space can just add the > relevant blocks. / [1] Well bitcoin wouldn't know to offload traffic to any of those / blocks, or a specific host on them, if you had them set up locally / via *Cat or Phantom... for bitcoin use. It would probably end up / half useful similar to the above FYI. But that would just affect / bitcoin, not whatever else you were running on them.