Zero knowledge is a proof property, not a privacy guarantee
A zero-knowledge proof can show that a statement is true without revealing the secret information used to prove it. Public inputs, the sending address, and application data can still reveal information outside that proof.
What does the proof hide?
Example: proving membership without naming the member
Imagine a club wants to check that you are a member. A proof can show that you meet this rule without revealing which member you are. The secret used to make the proof is called the witness. Facts the verifier can see are called public inputs. The proof only hides what its design keeps private. An address linked to your name can still identify you.
- Statement: The rule being proved, such as membership in a group.
- Witness: The secret information used to support that rule.
- Public input: Information the verifier can see as part of the check.
Keep in mind: If you send the proof from an address linked to your name, the address can still identify you.
Test a privacy claim with a disclosure map
List what each participant receives
For the membership example, write three columns on paper: information sent to the website, public inputs to the proof, and information recorded onchain. Put the browser session in the first column and the sending address in the last if those apply. Hiding the membership secret only answers the question about that secret.
Ask whether the advertised benefit is privacy or correctness
A proof may help verify a computation without making its inputs confidential. Read the application’s explanation of the statement it proves and the data it publishes. If those details are missing, the word ZK is not enough to fill the gap. RPC metadata is another separate disclosure path to check when a wallet sends the request.
What does a zero-knowledge proof establish?
A zero-knowledge proof can show that a rule is met while hiding the secret information used to prove it. A membership system, for example, can prove eligibility without publishing which member is acting. What it hides depends on the rule and which information stays public.
The application can still leak
Public inputs, contract events, transaction senders, and browser telemetry may reveal information outside the proof. If a user submits an otherwise private action from an already identified account, the proof does not conceal that account automatically. Review the full path from the interface to settlement.
Does a validity proof make transactions private?
No. A rollup can use validity proofs to establish correct execution while leaving transaction data visible. The presence of “ZK” in a product name therefore does not tell you whether balances or transaction partners are confidential. Ask which data is private, from whom, and under which assumptions.
Questions worth asking
Look for a documented threat model, audits with clearly stated scope, handling of secret material, and an explanation of public inputs. Audit coverage does not remove risk. For builders, the Ethereum development library linked in our technology hub provides a route into the underlying contract concepts before working with proof systems.
Revisit the public ledger boundary before evaluating privacy claims.
Check the source
This is an original, AI-assisted educational explanation. Sources and limitations are provided for verification; it is not personalized financial advice. Read the editorial policy or report a correction.
