Transaction pending, zero confirmations for days....
caracasmc opened this issue · 8 comments
I have a transaction that has been sitting with zero confirmations for days now. What can be done?
Hey @caracasmc!
You probably ran into JoinMarket-Org/joinmarket-clientserver#1588 .
Can you confirm that locking/unlocking solves the issue and your UTXO confirmation count is correctly displayed?
My wallet is locked and unlocked every time I open the JAM UI. Is that what you are referring to? On another note, my transaction remains unconfirmed even in the Mempool. Was the fee too low possibly? The transaction ID on mempool shows fees were :
| Fee | ~30k sat ~$20 |
|---|---|
| Fee rate | >9 sat/vB |
Okay, thanks for the clarification. Then this is not a problem of Jam/JM per se.
There are some issues with state corruption where UTXOs show zero confirmation when it already is confirmed long ago, that's why I was confused. Either wait till it is confirmed, increase the fee with RBF (replace by fee) from the wallet you initiated the transaction or use CPFP (child pays for parent) by sending it to another Jar with a high fee (normal send, not collaborative - as you'd need 5 confirmations for that).
PS: Edited the exact amounts in your reply.
How does the CPFP process work exactly? I choose the current Jar with the stuck transaction and sweep it to another jar via a non-callaborative transaction and set the fees higher so that it goes through? And once it goes through, how exactly does that affect the original stuck transaction with all the collaborators and multiple inputs and outputs?
Any recommendation as to what fee rate I should set for the CPFP transaction?
How does the CPFP process work exactly?
From: https://bitcoinops.org/en/topics/cpfp/
Child Pays For Parent (CPFP) is a fee bumping technique where a user spends an output from a low-feerate unconfirmed transaction in a child transaction with a high feerate in order to encourage miners to include both transactions in a block.
Basically, the "effective feerate" should be the average of both transactions.
I choose the current Jar with the stuck transaction and sweep it to another jar via a non-callaborative transaction and set the fees higher so that it goes through?
Yes, that is one way to do it!
And once it goes through, how exactly does that affect the original stuck transaction with all the collaborators and multiple inputs and outputs?
If the parent transaction is confirmed, so is (must be) the child transaction!
Any recommendation as to what fee rate I should set for the CPFP transaction?
I am afraid you cannot be given any adequate recommendations for specific values here.
@caracasmc Did you resolve your situation successfully?