From: Brooks Boyd <boydb@midnightdesign•ws>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Tor / SPV
Date: Wed, 15 Jan 2014 17:07:07 -0600 [thread overview]
Message-ID: <CANg-TZBCSvVeDTNKQSPV-Fw+uZ8np04WoE=o0J+8wULBHrsgKQ@mail.gmail.com> (raw)
In-Reply-To: <5747D5DF-879B-4A60-8BD6-18251E7D5F47@plan99.net>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
>
> 2) Secondly, we bump the protocol version, add a service flag and
> introduce a new P2P protocol command “tor?”. If a client sends a tor?
> message to a node that has the new service flag set, it will respond with a
> new “tor” message that contains a regular addr packet, with a single
> address, the IPv6-ified version of its hidden service name.
>
Rather than a separate message type that implies binding a clearnet IP to a
hidden service ID, why not add the service flag that the peer would like
Tor addresses, and the remote peer can then add IPv6-ified hidden service
addresses to "addr" messages? May need to modify the network address format
to include the ability to differentiate IPv6 clearnet vs. Tor addresses,
but then you remove the implication that a node has to give both public and
private IPs to a peer. If it's part of a batch of "addr"s, it could be my
own hidden service ID, but it could also be one that I learned from someone
else and is now propagating, for anyone to bootstrap with Tor hidden
service peers if they'd like.
Brooks
[-- Attachment #2: Type: text/html, Size: 1525 bytes --]
next prev parent reply other threads:[~2014-01-15 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 22:51 Mike Hearn
2014-01-15 23:07 ` Brooks Boyd [this message]
2014-01-15 23:32 ` Mike Hearn
2014-01-16 2:26 ` Brooks Boyd
2014-01-16 4:30 ` Miron
2014-01-16 10:25 ` Mike Hearn
2014-01-16 3:54 ` Isidor Zeuner
2014-01-15 23:37 ` Robert McKay
2014-01-16 4:29 ` Miron
2014-01-16 4:40 ` Miron
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='CANg-TZBCSvVeDTNKQSPV-Fw+uZ8np04WoE=o0J+8wULBHrsgKQ@mail.gmail.com' \
--to=boydb@midnightdesign$(echo .)ws \
--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