-
Notifications
You must be signed in to change notification settings - Fork 118
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 #500
Conversation
..and manually confirm that the arbitrary token interaction example doesn't work anymore
* all other permissions combined. For normal accounts it can safely be set to `none`, but for token contracts this has to be more restrictive, to | ||
* prevent unauthorized token interactions -- for example, it could be `proofOrSignature`. | ||
*/ | ||
access: Permission; |
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.
Any thoughts on how we default this to non-none somehow when working with tokens? Happy path needs to be the secure one
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.
We could export a TokenContract
which is SmartContract
but with defaults changed to be secure for token contracts
And have all our examples and docs for tokens point to this
Not ready for merge yet! Still has tests failing, revealed by this manual run: https://github.com/o1-labs/snarkyjs/actions/runs/3524467107/jobs/5909909541 |
…add-access-permission
…implicit-account-creation-fee
now that the Mina companion is merged, this needs updated bindings from |
access
permission to accounts MinaProtocol/mina#12003access
permission of "Either" (proof of signature) for all example token contracts