From: /dev /fd0 <alicexbtong@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Redefine packages to discourage address reuse
Date: Sat, 19 Oct 2024 23:19:15 -0700 (PDT) [thread overview]
Message-ID: <b383aad2-1abc-4b82-9851-1750b1b52f12n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1382 bytes --]
Hi Bitcoin Developers,
Address re-use is bad for privacy and such transactions affect everyone
involved. A mempool policy to reject such transactions will be useless,
however packages could be redefined to avoid address re-use in package
transactions.
BIP 331 defines packages as a list of unconfirmed transactions,
representable by a connected Directed Acyclic Graph (a directed edge exists
between a transaction that spends the output of another transaction). With
the new definition, transactions with address reuse cannot be a part of
package relayed by nodes with SENDPACKAGES P2P message.
The only downside that I could think of is the scanning time required to
check address reuse. Maybe others could suggest solutions for this problem
or we can limit the address reuse check only for the chain of transactions.
I am not sure if BIP author would agree with this change and a new BIP wont
make a difference if its not implemented in bitcoin core.
/dev/fd0
floppy disk guy
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/b383aad2-1abc-4b82-9851-1750b1b52f12n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1775 bytes --]
reply other threads:[~2024-10-20 7:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b383aad2-1abc-4b82-9851-1750b1b52f12n@googlegroups.com \
--to=alicexbtong@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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