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
In this example, if AuthorizationTuple bumped the nonce for sender, by the time Transaction started its process and read sender.nonce its value would be 2.
Furthermore, since both calls to AuthorizationTuple are processed first, the nonce for them would be 0 and 1 respectively, when they should be 1 and 2.
I'm not sure if there's a way to solve this but have not thought that much about it.
Looks like nonce auto increment does not account for auth tuple coming from sender
The text was updated successfully, but these errors were encountered: