-
Notifications
You must be signed in to change notification settings - Fork 871
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
Closing transaction stuck in mempool with low fee #7313
Comments
Sorry to be late here, what is the sequence of commands that you follow to do CPFP? |
It's a force close, by the message in the |
As in this case here, I simply spent my output at a higher fee with lightning-cli withdraw But in the case of a force close, whose peer has disappeared (i think forever) and whose fees have been too low for more than 4 months, what can be done? |
This is precisely why we needed the anchors. If you broadcasted the force close tx, your lightning node cannot spend your output before the relative timelock, with respect to the blockheight when the transaction was confirmed, but since it has not been confirmed, the "time" is frozen. The counterparty (your peer) doesn't have the timelock in his output, he is the one who can CPFP. |
Ok, I think I understand that nothing can be done, except hoping that the mempool returns to 2 sat/vbyte 🙂 |
Yes, either:
what if your peer completely lost his node's database and hdwallet? In the worst case your peer will wake up and punish you taking all the funds which where anyways mostly on his side. |
Interesting! |
I know it's a common problem, but I can't solve this.
I have already done CPFP by spending the output of the closing transaction with a higher fee, but in this case, I cannot see my UTXO.
Stuck transaction is:
https://mempool.space/tx/78f2f987c8b829b5dd85f51eff06f2e3327aa8d3caf3ad065ac24da816307269
To_us_msat is
"to_us_msat": 14020345
I imported all the descriptors into Sparrow Wallet, but I can't see that address
bc1qkh28n3jglp0zh9qtxtsfmxdq00xgwldtykvv3lf46mfqpzg9zuhsdj00lg
Am I missing something trivial?
The text was updated successfully, but these errors were encountered: