-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Bug] transactions gets stuck in "pending" and are not retried #10873
Comments
Here is another instance of this happening in which restarting chia solved the problem https://www.reddit.com/r/chia/comments/tnp1v4/24_hours_pending_transaction_dust_storm/ |
I have a similar problem. Accepted an offer and forgot to add a fee. After 12h pending I canceled it. 2 days later I have still peding balance of a CH21 token (-1) and XCH (+0.25). The offer is listed as "canceled". Edit: 11h later. still pending, even after two restarts (current mempool 56). Version1.3.1 What platform are you using?Windows What ui mode are you using?GUI |
Something new on this topic? It is still pending and I can't access my CH21 token.^^ |
Annoying. Why does nobody write "delete unconfirmed transactions" (which is hidden in that 3dots menu). And why is there no info in the UI what to do and what problems it can cause If someone deletes the unconfirmed transactions? It makes no sense that it stays unconfirmed for days. And why is there no standard fee. Or better like in my Ethereum Wallet where I can choose from three or so options? Not even a current USD price is shown. This software is very alpha and absolute not ready for market. |
Fix here: #11167 |
What happened?
Prerequisites
How to reproduce
What happens
When a transaction is stuck, it will show its state as "Pending" via
chia wallet get_transaction
. The tx will never be included in the mempool and thus never confirm.Current workaround
Restarting the wallet service (
chia start -r wallet
) sometimes results in the tx transitioning to "In mempool" state and confirm within a minute. In the past few weeks the amount of wallet service restarts required to get a stuck transaction "unstuck" this way was 1-7.Version
1.3.1
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output
No response
The text was updated successfully, but these errors were encountered: