Can't seem to unbond atoms
See original GitHub issueVersion
develop
Description
I have an account that has delegated fermions to three different validators. I’m attempting to unbond my atoms but I get this error:
Error sending transaction: bad nonce sequence, got 8, expected 9
Log
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
If you were to remove all of the bonds between all atoms in a ...
This sounds like a fun thought experiment! Let's assume that you are not actually changing the atoms or rules of chemistry. Your body...
Read more >Unbond - PyMOLWiki
unbond removes all bonds between two selections. Atoms bound normally, but not the representation ... Atoms unboud with the unbound command.
Read more >No, Scientists Will Never Be Able To Remove The ... - Forbes
It's absolutely true that atoms are mostly empty space. But removing even that empty space is impossible, and this is why.
Read more >[RFC] atom effects · Issue #211 · pmndrs/jotai - GitHub
It seems like there are three possibilities for each use case. can be implemented as derived atoms; can't be implemented as derived atoms, ......
Read more >Struggling to Learn Atom V23 | Alibre Forum
I have a "nothing special" mouse: a Dell optical mouse with two buttons and mouse wheel between them. It works properly with every...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Update: I tried unbonding from all three validators at once and it works. However, the process is incredibly slow. On the order of 30 seconds of waiting. And the UI does not tell me that something is happening in the background, I just have to have faith.
If the error is not there anymore, let’s close this issue and open a new one.