Some wallets have inccorect nonce from rpc. about iotex-core HOT 16 CLOSED

Hey Qevan, as per conversation, I've collected some of the addresses which reported this issue - Can't tansfer out IOTX from their wallets.

===============================

1. io1mq7a7xey4gjefpxcnk50ttkqxnft0meg3yu2dq
2. io1ducahpprkmxzdmy3zs3jt9su8semwcev9s2mku
3. io1zl4sx7lt8vmpxzcv4v34tckjruvjz08hfln8k8

Update (0405 GMT 3rd Feb 2024)
4) io198ws3fld0eq3597kqf499xd2k0cdfg232pmxv9

Update (0039 GMT 5th Feb 2024)
5) io1k4jq4y4evken4ahw98rjr6gkl0s338jlydjckk

Update (2358 GMT 5th Feb 2024)
6) io1dy3xy8fgepv5g7hl7f0h3pn9rvnpueh5zdmhwa
7) io127fxrul5ykcwec6pjy4rrlrpng0xwuppd2fzac

===============================

I'll update when I find more

from iotex-core.

@anwar139 @satyashr I just checked that the state of these accounts is unchanged in the blockchain, where there is no outbounding transactions from these accounts. We're fixing the pending transaction issue. Your tokens can be safely transfered out once it's fixed.

from iotex-core.

@Liuhaai any estimation time?

from iotex-core.

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

from iotex-core.

let's keep it open until the fix is released.

from iotex-core.

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.

from iotex-core.

This is my IOPAY wallet :
io1zl4sx7lt8vmpxzcv4v34tckjruvjz08hfln8k8

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?

from iotex-core.

Any ETA for when the bug will be fixed?

from iotex-core.

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.

from iotex-core.

Can you try transferring out from the reported wallet again? @satyashr

from iotex-core.

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.

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."

from iotex-core.

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

from iotex-core.

The address of the Chinese community with the same problem：
1）io1g0djt0dld0u6cj58fgkkf0e8mfjvdvm2tk0cn0
2）io1rhrj50y8fr8n9umuy8xht7jj3krxhlt4j9spwr

from iotex-core.

@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.

from iotex-core.

@Liuhaai thanks for the update

from iotex-core.

Thanks for the work fam!
And sorry if this late ping annoys you :p

from iotex-core.