public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Miron <c1.sf-bitcoin@niftybox.net>
To: Brooks Boyd <boydb@midnightdesign.ws>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Tor / SPV
Date: Wed, 15 Jan 2014 20:30:11 -0800	[thread overview]
Message-ID: <1389846611.19590.24.camel@mimiz> (raw)
In-Reply-To: <CANg-TZAyr8LyRQ5e4DpQA8fXEbGq6kxv=peB9oYB+bU_xA98ww@mail.gmail.com>


On Wed, 2014-01-15 at 20:26 -0600, Brooks Boyd wrote:
>         My goal here is not necessarily to hide P2P nodes - we still
>         need lots of clearnet P2P nodes for the forseeable future no
>         matter what. Rather we're just using hidden services as a way
>         to get authentication and encryption. Actually the 6-hop
>         hidden service circuits are overkill for this application, a
>         3-hop circuit would work just as well for most nodes that
>         aren't Tor-exclusive. 
>         
> 
> 
...
> communication to Tor doesn't change that. I agree the six-hop circuits
> would be overkill for that; I wonder if the network slowdown you get

BTW, I believe that the number of hops can be reduced below 3 on both
sides (client/server).  For Orchid, this will require a change to
CircuitPathChooser.  For other Tor implementations, it might require
using the control port to custom-build a circuit.







  reply	other threads:[~2014-01-16  4:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 22:51 [Bitcoin-development] Tor / SPV Mike Hearn
2014-01-15 23:07 ` Brooks Boyd
2014-01-15 23:32   ` Mike Hearn
2014-01-16  2:26     ` Brooks Boyd
2014-01-16  4:30       ` Miron [this message]
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=1389846611.19590.24.camel@mimiz \
    --to=c1.sf-bitcoin@niftybox.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=boydb@midnightdesign.ws \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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