zkVerify is a modular and decentralised proof verification network developed by Horizen Labs Research. It is designed to address the high computational and economic costs associated with zero-knowledge (ZK) proof verification across blockchains. The protocol separates proof verification from Layer 1 (L1) chains, enabling specialised infrastructure optimised for verifying proofs efficiently and at scale. By acting as a dedicated verification layer, zkVerify supports a wide range of proof systems, including Groth16, Plonk, Halo2, STARK, and emerging models such as Binius and Circle STARKs. Its architecture allows developers to integrate any proving system into decentralised applications, rollups, bridges, or identity frameworks without being constrained by L1 performance or cost limitations.

zkVerify reduces verification costs by up to 90% compared to on-chain execution, while maintaining verifiability and transparency. Proofs are submitted through a Proof Submission Interface, verified by native Rust verifiers, aggregated into Merkle trees, and finalised through attestations recorded on an L1 contract. This modular design supports scalability and continuous integration of new proving methods without requiring network-level forks.

The VFY token serves as the native utility and settlement asset of the zkVerify network. It underpins core network operations by providing economic incentives for validators, covering verification costs, and maintaining system integrity.

Fee payment: Users and applications pay verification and attestation fees in VFY for submitting ZK proofs to the network.
Staking and security: Validators stake VFY to secure consensus on proof validation and attestation publication. Misbehaviour, such as incorrect attestations, may result in stake penalties.
Governance: Token holders participate in protocol governance, influencing parameters like attestation frequency, proof verification policies, and new proof-type integrations.
Ecosystem incentives: VFY is distributed to participants who contribute computing resources or build integrations that expand zkVerify’s ecosystem.

zkVerify operates as a Proof-of-Stake mainchain specialised for proof verification. Its core components include:

• Mainchain: An L1 blockchain that executes verification, manages verifier modules written in Rust, and commits results to a Merkle tree.
• Proof Submission Interface: An RPC and transaction layer that accepts heterogeneous proof submissions from zkRollups, zkApps, and zkBridges.
• Attestation Mechanism: A protocol that aggregates proofs into Merkle trees and issues signed attestations referencing their Merkle roots.
• zkVerify L1 Contract: A smart contract that stores attestations and enables public verification through Merkle inclusion proofs.

The consensus is a Proof-of-Stake protocol where validators produce and confirm blocks containing verified proofs. Once proofs are verified, zkVerify produces attestations that can be published to multiple destination chains, such as Ethereum or Bitcoin rollup layers.

According to Figure 10 on page 10, zkVerify aggregates proofs from heterogeneous proving systems as leaves of a Merkle tree, which serves as a natural aggregation structure across different ZK technologies.

1. Proofs generated by zkApps, zkRollups, or zkBridges are submitted to zkVerify via its Proof Submission Interface.
2. zkVerify verifies each proof using its native Rust verifier modules.
3. Verified proofs are stored on-chain and aggregated into Merkle trees.
4. A digitally signed attestation containing the Merkle root is published to the zkVerify contract once predefined policies are met (e.g., time or proof-count thresholds).
5. Destination chains can use these attestations to confirm that their proofs were verified without reprocessing the verification logic.

This workflow allows applications to delegate computationally heavy proof verification to zkVerify while maintaining cryptographic trust guarantees.

zkVerify’s modular verification model supports several key applications:

ZK Rollups: Enables faster finality and lower costs by verifying transaction batches directly, avoiding recursive aggregation and expensive STARK-to-SNARK conversions.
Bitcoin zkRollups: Provides an external verification layer for proofs generated off-chain, mitigating Bitcoin Script limitations.
ZK Applications: Reduces verification costs for identity systems, DeFi privacy layers, and voting platforms.
Standardisation: Creates a unified verification protocol compatible with multiple proof types, promoting cross-chain interoperability and scalability.