From: alicexbt <alicexbt@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Denial of Service using Package Relay
Date: Thu, 06 Jul 2023 16:22:44 +0000 [thread overview]
Message-ID: <Ga2AELVMhRn2JlAC1-85LivVhcBhXzsf5ypHXMt_lg9RpwKTxeRxIRr8g8UHUihvxIVNKua6FIGRCjkt4CuNcDtZy2MetpOucpZYoKPW5sw=@protonmail.com> (raw)
Hi Bitcoin Developers,
I think its possible to use [package relay][0] for DoS attack in coinjoin. A few other projects could also be affected by packages. Since its a proposal that adds new P2P messages, transaction relay etc. its as important as any soft fork. Let me know if I am missing something.
Consider there are 2 coinjoin implementations: A and B
1) Register input in A
2) Double spend same input with zero fee to your own address
3) Register unconfirmed UTXO from 2 in B
4) B relays a package in which coinjoin transaction (child) pays for 2 (parent)
Users and coinjoin implementation B, both are incentivized to attack in this case.
Attacker could also use a different approach and register same input in A, B although there are some tradeoffs:
- If input gets included in a coinjoin transaction broadcasted by A, there is nothing much B can do about it. RBF with multiple users isn't easy and costly.
- Implementation with less users participating in a round would have an advantage.
[0]: https://gist.github.com/sdaftuar/8756699bfcad4d3806ba9f3396d4e66a
/dev/fd0
floppy disk guy
Sent with Proton Mail secure email.
next reply other threads:[~2023-07-06 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 16:22 alicexbt [this message]
2023-07-06 17:24 ` Andrew Chow
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='Ga2AELVMhRn2JlAC1-85LivVhcBhXzsf5ypHXMt_lg9RpwKTxeRxIRr8g8UHUihvxIVNKua6FIGRCjkt4CuNcDtZy2MetpOucpZYoKPW5sw=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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