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.
Know what the proof proves
A validity proof checks a precisely defined assertion, not the whole system’s security. Inspect input data, availability, circuit, upgrades and cryptographic assumptions.
- Ask whether a trusted setup is required.
- Privacy also depends on public data and the application.
Practical case: decision and limits
An app advertises “ZK” as if everything were private. Ask what is hidden, from whom and what remains public. A validity proof can verify computation without concealing system amounts or addresses. It also cannot guarantee the truth of external input data. Separate cryptographic properties, data availability, key management and upgrade powers.
A concrete verification
Write the proven claim: correct computation does not establish external data’s truth.
Proving that an age threshold has been met
A verifiable credential can prove that a person meets a minimum age without revealing their date of birth, provided the mechanism supports that type of proof. The verifier still needs to decide which issuers it trusts and check conditions such as credential validity. The proof confirms the statement specified by the system. Reused identifiers or session metadata can still let someone link separate presentations.
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.
Can a proof alone let me exit a rollup?
Not necessarily. A valid proof attests encoded rules; reconstructing your state and preparing an exit may also require corresponding data. Check publication, retention and exit procedures if the operator becomes unavailable.
Verifiable sources
Ethereum.org: Zero-knowledge proofs
Ethereum.org: Zero-knowledge rollups- W3C: Zero-knowledge proofs for verifiable credentials
Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated November 15, 2026
Prepare and continue reading

Useful background
- Understand blockchain simply
A blockchain is a shared ledger whose history is stored and checked by multiple computers. Transactions are signed, broadcast, verified and grouped into blocks under common rules. It does not make every user anonymous or every application safe.
- Blockchain privacy: what is public, traceable or selectively disclosed
An address is not necessarily a name, yet its public history can be clustered and linked to identity through a service, reuse, publication or network metadata. Privacy is a set of practices, not a switch that guarantees anonymity.

Continue to the next step
- Layer 2 and bridges: move faster without losing track of risk
A Layer 2 executes or batches operations, then publishes data or proofs to a base layer. A bridge moves or represents an asset between systems. Each step adds contracts, operators, delays and security assumptions that need checking.
- Full nodes: validation, syncing and maintenance
A full node applies validation rules to the chain it receives. It is neither a rewarded account nor a privacy guarantee; usefulness also depends on whether your wallet really uses it.




