public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Karl <gmkarl@gmail.com>
To: Aymeric Vitte <aymeric@peersm.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Rebroadcast mechanism in Bitcoin P2P network
Date: Sun, 12 Dec 2021 08:38:18 -0500	[thread overview]
Message-ID: <CALL-=e5mv5cr=Oqip0ob8P2XCbWPgOc67nnRjn7_OuDXPYUpVg@mail.gmail.com> (raw)
In-Reply-To: <86d49c80-2f8f-245c-5fdb-17c6ca6b5f2b@peersm.com>

[-- Attachment #1: Type: text/plain, Size: 794 bytes --]

On Sun, Dec 12, 2021, 7:42 AM Aymeric Vitte via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Indeed, I reiterate that using the Tor network for Bitcoin or whatever
> protocol not related to the Tor Browser (ie browsing and HS) does not make
> sense, for plenty of reasons
>

Please cite this.  It is very hard to believe.

Personally, I have encountered network blocking of bitcoin peers, and Tor
is one way to reconnect with the network when this happens.


Regardless, reasonable rebroadcasting of nonlocal transactions is a
hands-down good thing.  This does not make them anonymous, but it does make
it a little harder to track their origin, and additionally it makes their
transmission more robust.

Every extra measure is a good thing, as everything eventually fails.

>

[-- Attachment #2: Type: text/html, Size: 1678 bytes --]

  reply	other threads:[~2021-12-12 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 15:13 [bitcoin-dev] Rebroadcast mechanism in Bitcoin P2P network 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 [this message]
2021-12-12 14:23         ` Aymeric Vitte
2021-12-12 15:15           ` Pieter Wuille
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='CALL-=e5mv5cr=Oqip0ob8P2XCbWPgOc67nnRjn7_OuDXPYUpVg@mail.gmail.com' \
    --to=gmkarl@gmail.com \
    --cc=aymeric@peersm.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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