-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot double spend [350k sat] #7049
Comments
I wish there was a way to make use of UTXOs that have been used in a still unconfirmed transaction. I'm thinking either the coin selection tab could show them as grayed out but would be able to manually select them. (There'd be a small chance it could create invalid transactions when tiring to spend outputs of different still unconfirmed parent transactions.) But IMO much simpler, What if we could simply ignore a specific transaction in the mempool to then be able to craft a custom double spend? I'm setting a 350k sat bounty if someone can help us double spend that large consolidating transaction by just double spending a single UTXO. (without having to manually edit electrum wallet files with a text editor at a dozen or more places) |
I assume you mean the "Cancel (double spend)" feature, which spends back the inputs to your wallet.
|
Because it's a very large consolidation, and I'd like to invalidate a single UTXO with a higher fee. Thanks will try this out. |
Ah that won't work I am afraid. BIP125 rule 3 says the absolute fee needs to increase. |
Doesn't seems to be doing anything, I disconnected the wallet before. EDIT: Nevermind, it worked with " " |
Is there a general way to donate to electrum? I'll try anyway and report back if any miners overlooked rule #3 |
Electrum does not accept donations, but you can donate to the operators of Electrum servers. |
We'd have wanted to use the double spend feature but can't.
I suspect it could either be because we haven't produced any change (Send MAX)
or because all outputs are being sent to the local wallet.
The text was updated successfully, but these errors were encountered: