-
Notifications
You must be signed in to change notification settings - Fork 547
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
Add access
permission to accounts
#12003
Conversation
3f24c25
to
a832cfd
Compare
a832cfd
to
66dae59
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great!
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
!ci-build-me |
| `Set_delegate -> | ||
Boolean.true_ | ||
| `Access -> | ||
failwith |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why put a crasher here? seems unsafe?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no sensible default value for access
, so this ensures that we call it correctly everywhere.
!ci-build-me |
!ci-build-me |
This PR adds an
access
permission to accounts, which prohibits zkApp accounts from being accessed if the authorization is incorrect. This ensures that an 'empty update' to e.g. a token zkApp can't be used to pass unauthorized sub-calls.Testing is still TODO; opening this to see if CI finds any glaring errors in existing tests.
Checklist:
Fixes 2-pass transaction application model #12548