-
Notifications
You must be signed in to change notification settings - Fork 273
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
Execution error: Invalid transaction nonce of contract at address #2104
Comments
I see the same thing. |
Same Issue.
|
Same issue, funds are locked can't move them. Execution error: Invalid transaction nonce of contract at address ContractAddress(PatriciaKey(StarkFelt("="))). Expected: Nonce(StarkFelt("0x0000000000000000000000000000000000000000000000000000000000000002")); got: Nonce(StarkFelt("0x0000000000000000000000000000000000000000000000000000000000000000")). |
Same as above. Anyone found a solution? |
@benpatterson1 @Aravinthrselva @me2again @Dannyvanz please consider giving a 👍 to the issue so it can be easily filtered and prioritized. |
same issue {"execution error": "Invalid transaction nonce of contract at address ContractAddress (PatriciaKey (StarkFelt ""))). Account nonce: |
can you share your public address with me? |
i fixed it. thanks a lot |
How did you resolve the issue? |
First, I accessed my accounts with v5.5.2. I then pasted the v5.12.8 file onto v5.5.2. After closing and opening the browser, my accounts were still there. It even showed the amount of assets inside. But when I wanted to make a Transaction, I got the nonce problem again. Then I went to the manage extension section and pressed the update button for argent. and everything went back to normal. |
I'm getting the following error when trying to submit a swap transaction.
I think it's worth mentioning that I have a REVERTED transaction that is still being shown as pending on my wallet, which is a little bit annoying, I don't know if the issues are related.
TX: https://starkscan.co/tx/0x3d2f6b0bd6b5993008a138ee9a1499a8d5958dbf550de2efc4bd7edad9c4367
The text was updated successfully, but these errors were encountered: