RFC-0002: Introducing Side-loading Verification Keys in o1js #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 Proposal Overview
We're excited to propose the introduction of side-loading verification keys in
o1js
smart contracts and provable-programs. This RFC (Request for Comments) aims to improve the developer experience by increasing flexibility and allow for the creation of new, innovative design patterns.🎯 Why It Matters
Mina developers using
o1js
are limited to static verification keys compiled during their smart contract or provable-program creation, restricting dynamic interactions. By enabling side-loading of these keys, we open a world of possibilities, allowing for more complex, adaptable, and user-friendly applications within the Mina ecosystem.🔍 Highlights of the RFC
o1js
has the potential to significantly improve application development within the Mina ecosystem, presenting broader applications and new design patterns.📣 Seeking Community Input
This proposal is a stepping stone and needs your contributions. Your input is vital to shaping a robust and effective implementation.
🔗 RFC Details
For a comprehensive understanding of the proposal, challenges, and anticipated impact, please refer to the full RFC document.