From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] [tor-talk] Tor hidden service support
Date: Wed, 27 Jun 2012 05:25:15 -0400 [thread overview]
Message-ID: <CAD2Ti2_+4YzoO-9Qg8c68WkTkU39_Z1taBHCKuG6UJYL1vaZ4A@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti28hu6PccXpu4ObcbzWwFq+tchYaCoVY7S=9yakaB-nKjQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-06-27 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 14:11 [Bitcoin-development] " Pieter Wuille
2012-06-26 23:01 ` grarpamp
2012-06-27 0:14 ` Gregory Maxwell
[not found] ` <CAD2Ti29tMRCoW0rBSH738=0LpMfnGSJoSGYubV2-qQ9a6SC=zQ@mail.gmail.com>
[not found] ` <4FEAA936.10300@infosecurity.ch>
[not found] ` <CAD2Ti28hu6PccXpu4ObcbzWwFq+tchYaCoVY7S=9yakaB-nKjQ@mail.gmail.com>
2012-06-27 9:25 ` grarpamp [this message]
2012-06-27 8:47 ` Andy Parkins
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=CAD2Ti2_+4YzoO-9Qg8c68WkTkU39_Z1taBHCKuG6UJYL1vaZ4A@mail.gmail.com \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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