Open ChrisCates opened 4 months ago
This is an awesome idea!
I think there can be a couple more requirements/investigation areas that can be added to this RFC to create an artefact that looks at investigating those deemed most relevant and impactful.
Provable Programs as Signature Schemes
o1js
but simply require different sets of signers for verification.Contracts threshold signature verification
1
or n
) and just using a contract method, I think it would be fantastic to look at using the o1js
ECDSA features to natively verify, particularly to verify threshold signatures schemes.@teddyjfpender, thank you for the feedback. Adding these two use cases as an extension to an npm module definitely makes a ton of sense to me.
If possible, could you share some Github repositories demonstrating the usage in O1JS? I will update and fine tune the RFC after reviewing some example source code.
Thank you!
The goal of this RFC is to standardize access control over various functions in Mina Smart Contracts. As of now, there are three core flows:
Single Signature
Multi Signature
Role Based Access Control
The Access Control Standard should take inspiration from Open Zeppelin formatting and standards, and, leverage Typescript decorations in order to make access control among functions easy to implement.