Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Take into account previous parties in the same transaction when setting account preconditions #114

Open
mitschabaude opened this issue Apr 15, 2022 · 0 comments

Comments

@mitschabaude
Copy link
Member

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.

gabrielbosio pushed a commit to lambdaclass/o1js that referenced this issue Nov 17, 2023
…ier-index

[develop] Add lookup verifier index
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant