From: Pieter Wuille <bitcoin-dev@wuille•net>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Rebroadcast mechanism in Bitcoin P2P network
Date: Sun, 12 Dec 2021 15:15:16 +0000 [thread overview]
Message-ID: <cd6J1hP7ryGspj5LgGk8uwSsh5FGoDwW9UCp4qHhbSn3MXgzMw1slbo8xwWv9kZxn95CcPPE5elPiOktz4-1drpiOgfi-TtGzr66cdS6AuI=@wuille.net> (raw)
In-Reply-To: <10dcd9a9-0c39-7f4f-acde-04912a32e103@peersm.com>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
On Sunday, December 12th, 2021 at 9:23 AM, Aymeric Vitte via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Using the Tor network to bypass censorship for bitcoin can work but is a very poor solution, the Tor network is very centralized, very small, watched and controlled, with plenty of features that do not apply to other protocols than those made to be used with the Tor Browser, Pieter gave a simple example, that you can solve easily changing the circuits, the problem remains that you really need to be a super expert to escape all the dangers of the Tor network, not even sure it's possible unless you use something else than the Tor project code
FWIW, I wasn't talking about anything related to Tor's protocol or organization at all. What I meant is that because creating a hidden service has ~0 cost, it is trivial for anyone to spin up an arbitrary number of Bitcoin hidden services. Thus, if one runs a node that only connects to hidden services, it is fairly easily eclipsable.
It's just one example of a downside of (a particular way of) using Tor. That doesn't mean I recommend against using Tor for Bitcoin traffic at all; my point was simply that there are trade-offs, and aspects of privacy of the P2P protocol that Tor does not address, and thus one shouldn't assume that all problems are solved by "just use Tor".
Cheers,
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1658 bytes --]
next prev parent reply other threads:[~2021-12-12 15:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 15:13 Prayank
2021-12-11 3:49 ` damian
2021-12-11 16:21 ` Pieter Wuille
2021-12-12 11:48 ` Aymeric Vitte
2021-12-12 13:38 ` Karl
2021-12-12 14:23 ` Aymeric Vitte
2021-12-12 15:15 ` Pieter Wuille [this message]
2021-12-13 12:40 ` Aymeric Vitte
2021-12-12 22:32 ` damian
2021-12-12 18:49 Prayank
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='cd6J1hP7ryGspj5LgGk8uwSsh5FGoDwW9UCp4qHhbSn3MXgzMw1slbo8xwWv9kZxn95CcPPE5elPiOktz4-1drpiOgfi-TtGzr66cdS6AuI=@wuille.net' \
--to=bitcoin-dev@wuille$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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