Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Inconsistent nonce value across different endpoints
See original GitHub issueDescribe the bug
The nonce seems to be inconsistent between different endpoints (when transactions are processed using MultiSend).
To Reproduce Steps to reproduce the behavior:
- GET https://safe-transaction.avalanche.gnosis.io/api/v1/safes/0xBFe691bF973ECf07cd03bC6e7B1E74DeA2DEF539/
- Observe that nonce is
41 - For the same safe, get info about the transaction with nonce
43: https://safe-transaction.avalanche.gnosis.io/api/v1/safes/0xBFe691bF973ECf07cd03bC6e7B1E74DeA2DEF539/multisig-transactions/?nonce=43 - Observe that nonce was correctly executed and processed in the service
Expected behavior
Nonce should match with the latest successful transaction (43)
Environment (please complete the following information):
- Staging or production? Production
- Which chain? Avalanche
- OS: [e.g. iOS] Non Applicable
- Browser [e.g. chrome, safari] Non Applicable
- Version [e.g. 22]: v4.3.2
Additional context
The following Ethereum transaction is tied to Gnosis Safe transaction from nonce 37 to nonce 43
https://snowtrace.io/tx/0x2de145a14e19618d4cb11201e56b6e84386f41942f6cbbf0dc4c1e6d649ead8b
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I fixed it manually but there’s indeed an issue on the indexer
We deployed a hotfix, it should be working now. Can you confirm @davide9800 ?