-
Notifications
You must be signed in to change notification settings - Fork 110
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
Feature/set timing permission #685
Conversation
triggered manual workflow run: https://github.com/o1-labs/snarkyjs/actions/runs/3891134963 |
actually this is probably missing |
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 good to me with one comment, pre-approving. but should be made to pass the tests still (next push should trigger CI automatically)
@@ -245,6 +246,7 @@ let Permissions = { | |||
setTokenSymbol: Permission.signature(), | |||
incrementNonce: Permission.signature(), | |||
setVotingFor: Permission.signature(), | |||
setTiming: Permission.signature(), |
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.
These are the permissions that get applied by default when you deploy a zkApp. I think to prevent the "malicious zkApp developer" case that you outlined, the default for setTiming
should be "proof". Note: we changed the default for send
to "proof" as well on main
, even though here it's still "signature"
…even-more-annoying-changes
…setTiming-permission
This does raise the obvious question about why there's hard-coded JSON..
…n-more-annoying-changes
…setTiming-permission
9233f73
to
3863a78
Compare
No description provided.