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: Tue, 29 Oct 2024 16:43:11 +0000 [thread overview]
Message-ID: <ZyEQn6UzyC9rQebc@petertodd.org> (raw)
In-Reply-To: <d78f0253-b09a-4718-ba4f-805c1b25a036n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
On Wed, Oct 23, 2024 at 08:43:50PM -0700, /dev /fd0 wrote:
> Hi Peter,
>
> > This kind of idea has been proposed multiple times and rejected.
>
> This is the first time packages are used in bitcoin. My proposal is limited
> to packages.
>
> > 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.
>
> Can you share an example?
For example in Lightning you can do closes to arbitrary addresses. An
adversary could pick an address that they know you will use in a package
to cause package propagation to fail, effectively resulting in a form of
transaction pinning.
There's no reason to add this complexity for essentially zero gain.
> Packages will be used with covenants, inscriptions etc. apart from L2
> protocols and I think there would be lot of address-reuse which can be
> prevented by redefining the packages early.
Packages tell chainalysis services that the transactions are related and
probably created by the same person anyway. Avoiding address reuse in
them doesn't improve privacy meaningfully.
--
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 visit https://groups.google.com/d/msgid/bitcoindev/ZyEQn6UzyC9rQebc%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-10-29 16:52 UTC|newest]
Thread overview: 6+ 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
2024-10-24 3:43 ` /dev /fd0
2024-10-29 16:43 ` Peter Todd [this message]
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=ZyEQn6UzyC9rQebc@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