This RFC proposes an enhancement to the current developer experience of working with verification keys in o1js for example in smart contracts and provable-programs. Currently users are unable to provide a specific verification key for the contract or program to use when verifying a proof. By enabling the side-loading of verification keys, this approach allows for greater flexibility, permitting a prover to use any verification key from a tree of accepted keys, rather than being constrained to a single pre-defined key.
🔑 RFC-0002: Generic Recursive Proving Primitives (Side-loading Verification Keys)
This RFC proposes an enhancement to the current developer experience of working with verification keys in o1js for example in smart contracts and provable-programs. Currently users are unable to provide a specific verification key for the contract or program to use when verifying a proof. By enabling the side-loading of verification keys, this approach allows for greater flexibility, permitting a prover to use any verification key from a tree of accepted keys, rather than being constrained to a single pre-defined key.