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
Currently nonces seem to be based on current account transaction count.
This means that pending transactions aren't counted.
This means that if a new transaction is submitted while another is pending, it will be assigned the same nonce.
This means that if many txs are submitted before any of them are mined, only one of them will eventually be mined.
Parity added a method (nextNonce, noted here) for getting pending transaction count, but it isn't the same as geth's method for getting the pending transaction count.
We should maybe write an adapter for the two of them to replace our nonce tracker subprovider, and use it instead of the current cache strategy.
The text was updated successfully, but these errors were encountered:
Currently nonces seem to be based on current account transaction count.
This means that pending transactions aren't counted.
This means that if a new transaction is submitted while another is pending, it will be assigned the same nonce.
This means that if many txs are submitted before any of them are mined, only one of them will eventually be mined.
Parity added a method (
nextNonce
, noted here) for getting pending transaction count, but it isn't the same as geth's method for getting the pending transaction count.We should maybe write an adapter for the two of them to replace our nonce tracker subprovider, and use it instead of the current cache strategy.
The text was updated successfully, but these errors were encountered: