Add FAQ about restricting methods to specific addresses#745
Add FAQ about restricting methods to specific addresses#745
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
| ``` | ||
|
|
||
| - Require a private key as a private input, and check that `privateKey.toPublicKey().assertEquals(this.address)` | ||
| - Require a signature as an input. |
There was a problem hiding this comment.
by Require a signature as an input. do we mean to use the default value of signature? like https://docs.minaprotocol.com/zkapps/o1js/permissions#default-permissions
or do we want to set explicitly set the input field permission to signature? (or something else entirely?)
I was looking for a doc to link to, and found out that I need to learn more about what this means.
Permissions doc https://docs.minaprotocol.com/zkapps/o1js/permissions
signature: Fields that have their permission set tosignaturecan only be manipulated by account updates that are accompanied and authorized by a valid signature.
Or do we mean something as described in https://docs.minaprotocol.com/zkapps/o1js/interact-with-mina#signing-transactions-and-explicit-account-updates ?
Signature authorization – used to update user accounts. Signatures are verified against the account's public key.
|
@garwalsh for questions like this, let's link to a doc for more learning. See my (many) questions, thanks |
Co-authored-by: Barrie Byron <barrie@o1labs.org>
3 participants
No description provided.