zkVerify blog

zkVerify - Version 0.3.0 Release Announcement

a new version of zkverify is being released

INTRODUCTION

At block height 423518, a hard fork was performed and the new runtime for zkVerify is now officially enabled. Below, you will find the updates that our development team has implemented as well as links to the documentation.

DETAILS ABOUT THE UPDATE

New Verifiers:

Two new verifiers, one for Groth16 proofs, and one for RISC Zero, are now implemented and ready to use on zkVerify.

Why it matters:

  • RISC Zero is a common and easy to use framework that enables developers to write code to prove generic computation. It’s employed by a variety of zk-applications, and some rollups in the Bitcoin space. We’re hopeful that our developer community can begin to write applications that use RISC Zero and send the proofs for verification on zkVerify.
  • Groth16 proofs are one of the more commonly used proofs for applications in the Ethereum network. In fact, many applications that use RISC Zero have to convert their proofs to Groth16 proofs in order to submit them for verification on Ethereum. Additionally, some commonly used libraries like Circom and SnarkJS allow developers to produce Groth16 proofs.

Whether you’re a developer interested in using RISC Zero, or are a developer who has an application already generating Groth16 proofs, we encourage you to submit your proofs to zkVerify in order to achieve fast, and cost effective proof verification.

Fflonk Verifier:

An update to the fflonk verifier now enables users to submit any type of fflonk proof to zkVerify for verification. This includes proofs generated via Circom/SnarkJS employing fflonk as backend.

Why it matters:

Previously, only fflonk proofs generated by a specific version of Polygon CDK were accepted.

Finally, a bug that we found with block finalization was fixed and means that block finalization will be more stable going forward.

WHAT’S NEXT

As of this update, zkVerify supports four different proof types. Polygon CDK, and zkSync Era rollups can find a proof verification home on zkVerify, as well as application developers who are using RISC Zero and / or are generating Groth16 proofs.

In our next update, we’re looking at delivering:

  • Attestations to two new blockchains in order to reach a wider range of developer communities and display zkVerify’s interoperability.
  • One, or possibly two new proof verifiers.
  • And a variety of network and protocol updates that will be important as we continue on zkVerify’s journey to mainnet.