What is zkVerify?

So you've generated a proof. Now what?

You've spent compute time, ran your prover, and generated a zero-knowledge proof. It's sitting there — a cryptographic receipt that says "this computation happened correctly."

But here's the question nobody talks about enough:

Who actually checks it?

That's the job of a verifier. And for a long time, "the verifier" meant Ethereum — which is expensive, slow for certain proof types, and frankly not built for this job.

zkVerify was built specifically for this job.

## One blockchain. One job. <div style={{ marginTop: "1.5rem", marginBottom: "1.5rem" }}> !zkVerify </div>

zkVerify is a public, decentralized Layer 1 blockchain with a single purpose: verify zero-knowledge proofs, fast and cheap, for anyone.

It doesn't run general smart contracts. It doesn't try to be another EVM chain. It does one thing — accepts your proof, verifies it, records the result on-chain, and hands you a receipt you can use anywhere.

Think of zkVerify as a specialised courthouse for ZK proofs. Ethereum is a city that also has a courthouse. zkVerify is the courthouse — purpose-built, faster, and a fraction of the cost.

Why not just verify on Ethereum?

Verifying a single ZK proof on Ethereum consumes between 200,000 and 300,000 gas units depending on the proof type. During periods of network congestion that translates to $20 to $60 per proof.

That's fine for a handful of proofs. It's a product-killer if you're running a ZK rollup processing thousands per day.

There's also a second problem: not all proof types are even verifiable on the EVM. Most modern zkVMs use STARK-based proving backends. STARKs produce large proofs that are prohibitively expensive to verify on Ethereum — so teams wrap them inside a Groth16 proof just to make them EVM-verifiable. That adds latency, complexity, and cost at every step.

zkVerify solves both. It verifies proofs at 90%+ lower cost than Ethereum, and it supports native STARK verification — no wrapping required.

What makes zkVerify different

Proof-agnostic — bring whatever proof type your stack uses. zkVerify supports all major proof systems through dedicated verifier modules called verification pallets.

Built on Substrate — the same framework as Polkadot. Modular architecture, upgradeable pallets, Delegated Proof-of-Stake consensus.

EVM-compatible via VFlow — zkVerify's built-in EVM parachain lets you connect MetaMask, use Foundry and Hardhat, and work with standard Solidity tooling directly.

Native token: VFY — used for transaction fees, staking, and governance. Fixed supply of 1 billion VFY, also deployed on Base.

Where zkVerify sits in your stack

<div style={{ marginTop: "1.5rem", marginBottom: "1.5rem" }}> !zkVerify </div>

Your Ethereum contract never sees the proof. It only sees a compact Merkle inclusion proof — roughly the same size as a standard storage read. That's where the 90% cost reduction actually comes from.