What is a prover and a verifier?

In a proof system, the prover makes a claim and builds a proof, and the verifier checks that proof. The verifier accepts only a valid proof, so the prover's claim does not have to be trusted.

How the two roles work

The prover knows a secret, such as a private key, and wants to show that a statement about it is true. It runs a computation over the secret and sends back a proof.

The verifier receives the public statement and the proof. It runs a check that uses only those two, and it learns whether the statement is true.

Interactive and non-interactive proofs

In an interactive proof, the verifier sends random challenges and the prover answers them over several rounds. Each answer depends on the challenge, so the prover cannot prepare the answers in advance.

Many modern proofs, including STARKs and zk-SNARKs, skip the back-and-forth. The prover sends one proof, and anyone can check it later.

Why the roles matter for privacy

In a zero-knowledge proof, the verifier learns only that the statement is true. A prover can show that it owns a coin worth enough for a payment, without revealing which coin it is.

In Redacted

In bunker mode, every spend from your private balance is proved with a STARK, and the verifier checks a few random spots of that proof against a tree of hashes.

Bunker mode →

Related terms

Sources: Zero-knowledge proofs, ethereum.org · Fast Reed-Solomon Interactive Oracle Proofs of Proximity, ECCC 2017

Updated November 1, 2026. All terms