public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: damian@willtech•com.au
To: Prayank <prayank@tutanota•de>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Rebroadcast mechanism in Bitcoin P2P network
Date: Fri, 10 Dec 2021 19:49:55 -0800	[thread overview]
Message-ID: <1fbf0ef8b1b42979361b5df0b09c2dcd@willtech.com.au> (raw)
In-Reply-To: <MqZttWy--3-2@tutanota.de>

Good Afternoon,

Thank-you for your good work cataloguing and writing about the 
contributions to Bitcoin.

It is that the solution to privacy is to use privacy-enhancing network 
communications, such as TOR. I am not against a mechanism to rebroadcast 
transactions more robustly if the mempool of adjoining nodes has 
forgotten about them, but the truth is, all transactions originate from 
some node, and there are methods that allow an individual node to be 
identified as the likely source of a transaction unless privacy-enabled 
networks are utilised. Having a different method to cause rebroadcast 
does not obfuscate the origin.

KING JAMES HRMH
Great British Empire

Regards,
The Australian
LORD HIS EXCELLENCY JAMES HRMH (& HMRH)
of Hougun Manor & Glencoe & British Empire
MR. Damian A. James Williamson
Wills

et al.


Willtech
www.willtech.com.au
www.go-overt.com
duigco.org DUIGCO API
and other projects


m. 0487135719
f. +61261470192


This email does not constitute a general advice. Please disregard this 
email if misdelivered.
On 2021-12-10 07:13, Prayank via bitcoin-dev wrote:
> Hello World,
> 
> I had started working on this blog dedicated to Hal Finney in August:
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-August/019367.html
> 
> I have been able to track more than 10 Issues and Pull Requests from
> different Bitcoin projects that are focused on privacy. Wrote 3 blog
> posts and will write more often as I learn new things. There is a
> section called 'Hall of Fame' and 7 developers are listed in hof who
> worked on one or more pull requests that helped improve privacy in
> Bitcoin projects: Andrew Chow, chimp1984, jmacxx, Luke Dashjr, Samuel
> Dobson, Vasil Dimov and wpaulino.
> 
> Last post is about 'Rebroadcast mechanism' used in Bitcoin full node
> implementations:
> https://prayank23.github.io/camouflage//blog/rebroadcast/
> 
> Problem: Rebroadcast mechanism used in Bitcoin Core and Knots,
> rebroadcasts only our transactions. This helps spy nodes to link
> bitcoin addresses with IP addresses and also know that wallets are
> enabled for a node.
> 
> Solution by Amiti Uttarwar: New rebroadcast mechanism in which
> transactions are re-broadcasted based on fee rate and mempool age.
> 
> I have shared other details, my opinion and links to comments by Suhas
> Daftuar in the blog post since related pull request has been in draft
> mode for some time now.
> 
> --
> 
> Prayank
> 
> A3B1 E430 2298 178F
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


  reply	other threads:[~2021-12-11  3:50 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 [this message]
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
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=1fbf0ef8b1b42979361b5df0b09c2dcd@willtech.com.au \
    --to=damian@willtech$(echo .)com.au \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=prayank@tutanota$(echo .)de \
    /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