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; 
MIME-Version: 1.0
In-Reply-To: <CAD2Ti28hu6PccXpu4ObcbzWwFq+tchYaCoVY7S=9yakaB-nKjQ@mail.gmail.com>
References: <20120626141129.GA30240@vps7135.xlshosting.net>
	<CAD2Ti2_7dc00bad0stAzYHgPG9f6Y91fYodyczTch73-psk7Sw@mail.gmail.com>
	<CAD2Ti29tMRCoW0rBSH738=0LpMfnGSJoSGYubV2-qQ9a6SC=zQ@mail.gmail.com>
	<4FEAA936.10300@infosecurity.ch>
	<CAD2Ti28hu6PccXpu4ObcbzWwFq+tchYaCoVY7S=9yakaB-nKjQ@mail.gmail.com>
Date: Wed, 27 Jun 2012 05:25:15 -0400
Message-ID: <CAD2Ti2_+4YzoO-9Qg8c68WkTkU39_Z1taBHCKuG6UJYL1vaZ4A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Bitcoin-development] [tor-talk]  Tor hidden service support
Precedence: list

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.