From: Mike Hearn <mike@plan99•net>
To: Bazyli Zygan <b@grabhive•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Tor and Bitcoin
Date: Tue, 30 Jul 2013 14:41:53 +0200 [thread overview]
Message-ID: <CANEZrP3rqTW_DEZ75B9tg6kNPtfX4ENBJupaJD1axSLsxMdCwQ@mail.gmail.com> (raw)
In-Reply-To: <FB36762E8B574F7AAB7D25618841CF01@grabhive.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
Various ideas are possible:
* Use the Tor SOCKS proxy in such a way that it creates a guaranteed
independent circuit to a different exit node each time you connect. This
gets you back to the slightly stronger clearnet heuristic of "if I saw a
bunch of peers announce my tx, then it's probably valid". I don't know if
this is possible.
* Have a set of hard-coded long term stable hidden peers, that are run by
known community members who are not going to collaborate to defraud people.
Of course if they're run by people who are well known that rather defeats
the point of them being hidden, but you benefit from the fact that the
.onion names double as authentication tokens.
* Talk the Tor protocol directly and have the app explicitly pick its own
diverse set of exit nodes, one per p2p connection. This is likely to be
complicated. Last time I looked Tor doesn't provide any kind of library or
API.
I agree that it's a kind of theoretical attack right now, but then again,
I'm not aware of any countries that block Bitcoin either. The thing with
Thailand seems like it might be the result of some confusion over who
exactly can make laws in that country. I'd be more concerned about
Argentina, but we're a long way from ISPs searching for people to arrest by
looking for port 8333.
Supporting SOCKS (really: blocking sockets) would be a good thing anyway.
Using blocking sockets also means we'd get SSL support, so if at some point
Bitcoin nodes start supporting SSL we'd be able to use it more easily.
[-- Attachment #2: Type: text/html, Size: 1928 bytes --]
next prev parent reply other threads:[~2013-07-30 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 12:01 Bazyli Zygan
2013-07-30 12:41 ` Mike Hearn [this message]
2013-07-30 14:01 ` Jeff Garzik
2013-07-30 17:02 ` Wendell
2013-07-30 17:20 ` Bazyli Zygan
2013-07-30 18:30 ` Peter Todd
2013-07-30 19:36 ` Wendell
2013-07-30 20:11 ` Peter Todd
2013-07-30 20:12 ` Peter Todd
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=CANEZrP3rqTW_DEZ75B9tg6kNPtfX4ENBJupaJD1axSLsxMdCwQ@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=b@grabhive$(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