-
Notifications
You must be signed in to change notification settings - Fork 324
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
Some wallets have inccorect nonce from rpc. #4156
Comments
Hey Qevan, as per conversation, I've collected some of the addresses which reported this issue - Can't tansfer out IOTX from their wallets. ===============================
Update (0405 GMT 3rd Feb 2024) Update (0039 GMT 5th Feb 2024) Update (2358 GMT 5th Feb 2024) =============================== I'll update when I find more |
This is my IOPAY wallet : I've Quite a few IOTEX stuck in TrustWallet, can you please help resolve this Issue ASAP? I need to transfer my fund to exchanges? |
@Liuhaai any estimation time? |
Any ETA for when the bug will be fixed? |
Another address added No.5 - was attempting to transfer from a ledger. Similar symptom(s), managed to get hash, but later on, transaction dropped and the hash is no longer traceable on iotexscan |
This could be a widespread issue, people haven't tried to move IOTEX from Self Custody wallet to exchanges! Please give us the ETA on when it will be fixed. |
Can you try transferring out from the reported wallet again? @satyashr |
Quoting Jeremi from 1 of the tickets on Discord. I removed unnecessary messages. "Hey, the issue has been fixed in the code, for what it seems, but the iotex-core node software still needs to be updated across the entire network before the fix is available to use." |
let's keep it open until the fix is released. |
I'm experiencing this problem as well. I haven't accessed my wallet in 3 years and when I tried a few days ago to make a transfer (out of iopay) everything is still pending and nothing is showing up on iotexscan. io127fxrul5ykcwec6pjy4rrlrpng0xwuppd2fzac |
added 1 more address 6). I wanted to add this address earlier, but seeing the thread was closed I thought it was unnecessary because I assumed fix will be released soon. |
The address of the Chinese community with the same problem: |
@anwar139 @satyashr @gopinath87607 @Reallyfresh @Charliecharlie-git Thanks for your patience. The fix has been deployed to our nodes. You can use our RPC (https://babel-api.mainnet.iotex.io/) to connect to the network. The transaction might take longer than usual to be minted since some of the delegates haven't upgraded to v1.13.1. However, we are notifying our delegates to upgrade their nodes. The status of the transaction can be checked at (https://iotexscan.io/?format=0x). Let me know if your transfer still fails. |
@Liuhaai thanks for the update |
Thanks for the work fam! |
There are a couple examples where the nonce returned by rpc not correct.
This prevent users from sending new txns. They txns could get pending and dropped after timing out.
The text was updated successfully, but these errors were encountered: