Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Sjel7-0006e7-QZ for bitcoin-development@lists.sourceforge.net; Tue, 26 Jun 2012 23:01:21 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=grarpamp@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Sjel7-0006PR-1B for bitcoin-development@lists.sourceforge.net; Tue, 26 Jun 2012 23:01:21 +0000 Received: by werg55 with SMTP id g55so362881wer.34 for ; Tue, 26 Jun 2012 16:01:14 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.206.135 with SMTP id l7mr8951110weo.84.1340751674727; Tue, 26 Jun 2012 16:01:14 -0700 (PDT) Received: by 10.180.7.105 with HTTP; Tue, 26 Jun 2012 16:01:14 -0700 (PDT) In-Reply-To: <20120626141129.GA30240@vps7135.xlshosting.net> References: <20120626141129.GA30240@vps7135.xlshosting.net> Date: Tue, 26 Jun 2012 19:01:14 -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: 1Sjel7-0006PR-1B Cc: phantom-protocol@googlegroups.com Subject: Re: [Bitcoin-development] 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: Tue, 26 Jun 2012 23:01:21 -0000 > Additionally, such addresses are exchanged and relayed via the P2P network. > To do so, we reused the fd87:d87e:eb43::/48 IPv6 range. Each address in this > 80-bit range is mapped to an onion address, and treated as belonging to a > separate network. This network range is the same as used by the OnionCat > application (though we do not use OnionCat in any way), and is part of the > RFC4193 Unique Local IPv6 range, which is normally not globally routable. > > Other clients that wish to implement similar functionality, can use this > test case: 5wyqrzbvrdsumnok.onion == FD87:D87E:EB43:edb1:8e4:3588:e546:35ca. > The conversion is simply decoding the base32 onion address, and storing the > resulting 80 bits of data as low-order bits of an IPv6 address, prefixed by > fd87:d87e:eb43:. As this range is not routable, there should be no > compatibility problems: any unaware IPv6-capable code will immediately fail > when trying to connect. 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 And the one for 'garlicat' for I2P, which might be more complex due to I2P's addressing: fd60:db4d:ddb5::/48 Note that while these blocks are not expected to be routable, that people may in fact have interfaces, routing tables and packet filters on their machines configured with up to all three of those networks for the purposes therein.