Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 6C879C0012 for ; Sun, 12 Dec 2021 13:38:33 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 5B48760D68 for ; Sun, 12 Dec 2021 13:38:33 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp3.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wYAI477HZLW for ; Sun, 12 Dec 2021 13:38:32 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by smtp3.osuosl.org (Postfix) with ESMTPS id 78CE760720 for ; Sun, 12 Dec 2021 13:38:32 +0000 (UTC) Received: by mail-lf1-x12b.google.com with SMTP id e24so595904lfc.0 for ; Sun, 12 Dec 2021 05:38:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=polcoNgDDAttI60k2wdVyRHRNLmQ6+yvcMUOVLaE/7U=; b=LTx4dAhhr3QkctnQ8QUyjGJDjh9y9WpY9SbxLr0prrGlfB9uXJLfgY+CxrSk/lHMDH fCE9EVVotB0N3A5m8EIkXwqodV4Q4I8K6aVzjJbA/BMtFnzydmMas/VkcoavEGXJbvht wTf+uZjkQBlQgM3wK4K/hfDNXM59GU6gAH/8v6kGZ/JYWsI5LRkfHZ9VPQf2qdWALp3O /h2hucql+cZrSS0n+iZwDfSon2GTVvuccgD4CJnI9eRn2nmsimJpkW7eB9/8nLos2Ulu NU/CtoS0Oo5+z/nLx9vBMXjX1bjWkh1uYDqNboR4Si6fn2g7gi8EyoE6Y2BBwIfDkt4A HKAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=polcoNgDDAttI60k2wdVyRHRNLmQ6+yvcMUOVLaE/7U=; b=3vzaurhvVJ1Prj5s4eJNiiCm4ETyjrfsbEJeoAe7VMifVGPUu7wPSwTOpgvuwDiAQX VDrMfj8HcpTxJXBn6d87D6oLlx3EIjEtNvljObOLFKACq0iRvegcSSyolszacLdqX0re 0V+znGlEqUnN4pdmhpUXkn2ysbfvEIvySBFi5gj5/+77u/9gKZ54f9OjVALIPmCpfO51 6lWJxsdiYYkX3G4nRf2hee6RzoW+89Am4XEX2D1phixsfVzcaDIRIU9xnXbcCDCJRPjk LU/h1GakZveVA81d5OVyoeMraNHBnSDS4HWvOlvrdJ1Qv+px9oaCqBz5Y7uSWRJUSDnv NQRg== X-Gm-Message-State: AOAM530IOgRT5ORSaCS6t7k6BW7aQWYRv6sbfOMnUJDFg6nV79/Y8gNU eSYK/56x/dGEyMUG4vHP4sfLbIohA+WojwUwczmFyLToG9w= X-Google-Smtp-Source: ABdhPJxjtmvslfWkPYTcKXmddachdgFxLoucxWIC4gPaMo5T+Adex/WK0gcaKSWqo2CrXfU6Bm6H+QqX4narXF8e82U= X-Received: by 2002:ac2:4907:: with SMTP id n7mr23007882lfi.86.1639316310291; Sun, 12 Dec 2021 05:38:30 -0800 (PST) MIME-Version: 1.0 References: <1fbf0ef8b1b42979361b5df0b09c2dcd@willtech.com.au> <86d49c80-2f8f-245c-5fdb-17c6ca6b5f2b@peersm.com> In-Reply-To: <86d49c80-2f8f-245c-5fdb-17c6ca6b5f2b@peersm.com> From: Karl Date: Sun, 12 Dec 2021 08:38:18 -0500 Message-ID: To: Aymeric Vitte , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000597cc905d2f3120d" X-Mailman-Approved-At: Sun, 12 Dec 2021 13:44:09 +0000 Subject: Re: [bitcoin-dev] Rebroadcast mechanism in Bitcoin P2P network X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Dec 2021 13:38:33 -0000 --000000000000597cc905d2f3120d Content-Type: text/plain; charset="UTF-8" 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. > --000000000000597cc905d2f3120d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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

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.= =C2=A0 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.
=


R= egardless, reasonable rebroadcasting of nonlocal transactions is a hands-do= wn good thing.=C2=A0 This does not make them anonymous, but it does make it= a little harder to track their origin, and additionally it makes their tra= nsmission more robust.

E= very extra measure is a good thing, as everything eventually fails.
<= div bgcolor=3D"#FFFFFF" text=3D"#000000">

--000000000000597cc905d2f3120d--