You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When converting the csv files to JSON before signing, the CLI is sometimes generating the wrong nonce, even on a wallet that has had no other transactions to it and only has one transaction in the set
The text was updated successfully, but these errors were encountered:
I can't think of any reason this would fail for a single transaction, as I'm just using getNonce() from Stacks.js
I can see how this could be a problem if you are sending multiple transactions from the same multisig address, since the transactions (and therefore nonce lookups) are done in parallel, so you might get the same nonce for multiple transactions from that address. What I could do here is to add an intermediate function that caches the results of getNonce() for each address, and if we've already fetched the nonce from the network once, increment the last value instead of fetching again
When converting the csv files to JSON before signing, the CLI is sometimes generating the wrong nonce, even on a wallet that has had no other transactions to it and only has one transaction in the set
The text was updated successfully, but these errors were encountered: