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, there are issues and custom workarounds for setting the correct nonce precondition in the case one account has multiple nonce-incrementing parties within one transaction. The original plan of just using a nonce fetched from an API doesn't work - the precondition has to be incremented according to previous parties.
The same is probably true of other account preconditions. Therefore, we should devise a general system for keeping track of account updates within one transaction. After the account state cache is integrated, we should add an additional data structure which keeps track of updates to that account states at the "current state" of the current transaction -- which can be used when setting preconditions.
The text was updated successfully, but these errors were encountered:
Currently, there are issues and custom workarounds for setting the correct nonce precondition in the case one account has multiple nonce-incrementing parties within one transaction. The original plan of just using a nonce fetched from an API doesn't work - the precondition has to be incremented according to previous parties.
The same is probably true of other account preconditions. Therefore, we should devise a general system for keeping track of account updates within one transaction. After the account state cache is integrated, we should add an additional data structure which keeps track of updates to that account states at the "current state" of the current transaction -- which can be used when setting preconditions.
The text was updated successfully, but these errors were encountered: