capi
capi copied to clipboard
safeguard against same nonces in parallelized txs
In some cases, two txs will trigger two system_accountNextIndex
calls, which are parallelized, and produce the same nonce. This in turn invalidates one of the two txs. I believe we need some kind of nonce-management system––perhaps a dedicated Rune.