From: Peter Todd <pete@petertodd•org>
To: /dev /fd0 <alicexbtong@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Redefine packages to discourage address reuse
Date: Wed, 23 Oct 2024 10:35:52 -0400 [thread overview]
Message-ID: <ZxkJyPVhk2uQLPOl@petertodd.org> (raw)
In-Reply-To: <b383aad2-1abc-4b82-9851-1750b1b52f12n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
On Sat, Oct 19, 2024 at 11:19:15PM -0700, /dev /fd0 wrote:
> 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.
This kind of idea has been proposed multiple times and rejected.
In this particular case, an especially bad problem with it is there are
probably L2 protocols that actually need to reuse addresses in certain
circumstances. There are likely to also be situations where an adversary
can trigger unintentional address reuse, and thus get transactions
pinned by this filter.
For these reasons alone, NACK.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
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/ZxkJyPVhk2uQLPOl%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-23 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 6:19 /dev /fd0
2024-10-20 7:33 ` Abubakar Ismail
2024-10-24 3:38 ` /dev /fd0
2024-10-23 14:35 ` Peter Todd [this message]
2024-10-24 3:43 ` /dev /fd0
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=ZxkJyPVhk2uQLPOl@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=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