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
Transactions can be applied via p2p out of order. This can result in nonce errors regarding gossip, leading to transactions not being added to the mempool. The more sequential transactions sent, the higher chance of transactions being applied out of order and not being included in blocks despite being applied to the API node.
We need the applicator to decode transaction nonces and make a best effort to apply transactions according to their nonce.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
New feature
Transactions can be applied via p2p out of order. This can result in nonce errors regarding gossip, leading to transactions not being added to the mempool. The more sequential transactions sent, the higher chance of transactions being applied out of order and not being included in blocks despite being applied to the API node.
We need the applicator to decode transaction nonces and make a best effort to apply transactions according to their nonce.
Anything else?
No response
The text was updated successfully, but these errors were encountered: