Separate computation validity from input privacy. Inspect the proof system, disclosed data, trust assumptions and data availability.
Name what is proven
Validity is not secrecy
Review setup and code
Define the claim
A proof links a public statement to private inputs or computation. It only attests to rules encoded in the circuit, not the truth of an outside data source.
Separate guarantees
A validity proof can confirm a state transition without repeating all computation. A rollup using such proofs does not automatically hide transfers.
Inspect assumptions
Trust varies with the protocol, initial setup, verifier contract and security of proof generation code.
Check data
Reconstructing state or exiting a network may require accessible data in addition to a valid proof.
Checks to make
| Topic | Check |
|---|---|
| Define the claim | Name what is proven |
| Separate guarantees | Validity is not secrecy |
| Inspect assumptions | Review setup and code |
| Check data | Test availability |
Frequently asked questions
Does a proof certify the whole system?
No. It covers a claim defined by its circuit and inputs.
Does a ZK rollup hide every payment?
No. Validity and privacy are separate properties.
Verifiable sources
Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Reviewed September 25, 2026
