zkVerify

• Name: zkVerify
• URL: https://zkverify.io/
• Category: zero-knowledge proof verification blockchain / verification layer / proof-receipt settlement infrastructure
• Summary: zkVerify is a proof-verification chain. The point is receipt generation and verifier policy, not proof generation. Useful when the real question is which proof systems get standardized, cheap verification and how applications later prove that verification elsewhere.
• What it does:
  • Accepts proof submissions from rollups and zk applications through chain extrinsics and SDK tooling, then verifies them using built-in verifier pallets specialized by proof system
  • Aggregates verified proofs into receipt batches and exposes Merkle paths so applications can later prove inclusion against destination-chain contracts
  • Supports multiple proof systems and runtimes, including Groth16, EZKL, UltraHonk, UltraPlonk, Risc Zero, Plonky2, SP1, and Intel TDX-based TEE proofs
  • Operates as a public proof-of-stake chain with RPC, boot, and validator node roles, plus staking incentives around the VFY token
  • Publishes open source node software, docs, and integration materials that make the operator and settlement model much clearer than the marketing site alone
• Key claims:
  • The official site and docs describe zkVerify as a high-performant, public, decentralized blockchain dedicated to zero-knowledge proof verification
  • The core-architecture docs say the chain is an L1 proof-of-stake blockchain built on Substrate, specialized in zk-proof verification with dedicated verifier pallets and a native VFY token used for verification
  • The proof-submission-flow docs explain that valid proofs emit ProofVerified events, failed verification attempts still pay fees to mitigate DoS, and successful submissions can be aggregated into Merkle-root receipts retrievable through RPC calls
  • The docs describe a permissionless aggregation engine where participants can publish aggregation proofs and earn fees, which makes zkVerify more than a simple verifier library
  • Node-operator docs explicitly document RPC, boot, and validator node roles plus hardware requirements, reinforcing that this is an actual networked verification chain rather than only an SDK or hosted API
• Whitepaper: No canonical standalone whitepaper or litepaper was found in the official materials reviewed during this pass. The primary-source surface is the official site, docs portal, proof-system and node-operator docs, and open-source repositories; see ../whitepapers/zkverify-primary-sources-2026-04-26.md.
• Sources:
  • https://zkverify.io/
  • https://docs.zkverify.io/
  • https://docs.zkverify.io/architecture/core-architecture
  • https://docs.zkverify.io/architecture/proof-submission-interface
  • https://docs.zkverify.io/architecture/supported_proofs
  • https://docs.zkverify.io/node-operators/getting_started
  • https://github.com/zkVerify/zkVerify
  • https://raw.githubusercontent.com/zkVerify/zkVerify/main/README.md

Internal linkages

• Best anchors: aligned-layer, succinct, and boundless.

• Last reviewed: 2026-04-26 UTC