This is not exactly an "attack" but it would be pretty frustrating for a new or inexperienced crypto user. Honestly I don't want anyone getting into crypto to have a bad experience, no matter what coin they are interested in.
This is from a post on the Trezor sub. User was sent BTC dust with a very low fee, then couldn't get is his own transaction to confirm because the wallet included the unconfirmed dust transaction in his:
I figured out why transaction is uncofirmed. Because one of the dust transactions is unconfirmed too. So this is serious problem: Why Trezor web app included unconfirmed input in my transation and now I depend on when this shitty dust will be confirmed, if it ever will!
So there is an exploit. Send dust transaction to address know to be used by trezor user and which have some funds. And make this transaction unconfirmable, i.e. set zero fee. In this condition trezor web app in some reason uncludes unconfirmed dust transaction in input of a new transaction sent by trezor user. User gets unconfirmed forever transaction on inputs and so his transaction also doomed to be unconfirmed.
[link] [comments]
source https://www.reddit.com/r/btc/comments/lfs8yj/interesting_unintended_consequence_of_high_fees/
No comments:
Post a Comment