-
Notifications
You must be signed in to change notification settings - Fork 992
transactions not always confirming #2223
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
Comments
Same here, I did multiple transactions between nodes with 0 confirmations and Coins are not Spendable anymore. |
I see the following errors in my wallet log which I believe are related to this problem. I notice that the re-post will also sometimes fail with this error. These tx do eventually post after trying a few times.
and from grin server log:
|
For the owner_api there is no repost_tx method, and calling the post_tx method again does not seem to work. I get these results:
|
I saw the "failed to validate tx" error in the server in my own tx confirmation issue when I tried to re-finalize my transaction. It had been already transmitted and confirmed. The error message could definitely improve in the wallet's side ("you are trying to re-transmit an already confirmed transaction"?). I managed to fix my wallet state by running |
I dont believe they are already confirmed. My wallet shows them as confirmed=false. Here is a (small) sample of my currently unconfirmed tx:
|
You might as well try |
It worked, but it is definitely a bug if 0 confirmation transactions behave like this. |
Yes, it sounds like a bug in the wallet to me. |
Im closing this. My issue was resolved with this fix: |
NOTE: This may be due to #2266 - I was previously missing the error from finalize step so these tx remaining unconfirmed are probably caused by that.
I have a very low success rate getting transactions to confirm on FlooNet. Most dont confirm without being re-posted at least once. Here is a partial log of a wallet getting payments that remain unconfirmed:
The text was updated successfully, but these errors were encountered: