ZK First Contact And Vocabulary

What this page explains#

ZK pages begin by defining proof, statement, prover, verifier, public input, witness, circuit, zkVM program, receipt, journal, tag, and precompile. This page sits in ZK, Groth16, And RISC Zero Succinct. It gives the topic a plain-language handle first, then shows the working idea, the mechanism, the source trail, and any limits that still matter. This category separates proof verification from application validity. Groth16 and RISC Zero Succinct can verify selected statements, while covenant scripts, successor checks, source limits, and accepted evidence still carry separate responsibility.

The writing follows a simple Kaspa documentation pattern: answer the practical question first, then link outward for details. The closest public sources for this page are DOC-TOCCATA-INLINE-ZK, PAPER-GROTH16, RISCZERO-PROOF. Local notes can help choose what to explain, but public-facing references resolve to upstream websites, repositories, papers, release pages, or docs.

How to think about it#

The practical model starts by naming the layer that owns the topic: wallet use, node operation, consensus, transaction validation, Toccata script behavior, tooling, or research. From there, the page shows which public source can support the explanation and where the explanation becomes incomplete.

For ZK First Contact And Vocabulary, the model is built around these anchors: a proof is a checked statement, not the whole app state; public inputs or journals carry explicit commitments; private witness stays outside the public transaction; verifier identity matters; precompile tags choose the verifier path. This model is useful, but it does not encode every constant, branch, error type, or edge case. Those details belong in the source path and the source notes.

How it works#

1. a proof is a checked statement, not the whole app state. ZK verification is a constrained script operation, not a general declaration that an application transition is sound. Tags select verifier paths, costs decide whether the transaction can afford the check, and public inputs or journals bind the proof to the state claim. The covenant or application still has to validate the surrounding transition, observe acceptance, and test negative cases.

2. public inputs or journals carry explicit commitments. ZK verification is a constrained script operation, not a general declaration that an application transition is sound. Tags select verifier paths, costs decide whether the transaction can afford the check, and public inputs or journals bind the proof to the state claim. The covenant or application still has to validate the surrounding transition, observe acceptance, and test negative cases.

3. private witness stays outside the public transaction. ZK verification is a constrained script operation, not a general declaration that an application transition is sound. Tags select verifier paths, costs decide whether the transaction can afford the check, and public inputs or journals bind the proof to the state claim. The covenant or application still has to validate the surrounding transition, observe acceptance, and test negative cases.

4. verifier identity matters. ZK verification is a constrained script operation, not a general declaration that an application transition is sound. Tags select verifier paths, costs decide whether the transaction can afford the check, and public inputs or journals bind the proof to the state claim. The covenant or application still has to validate the surrounding transition, observe acceptance, and test negative cases.

5. precompile tags choose the verifier path. ZK verification is a constrained script operation, not a general declaration that an application transition is sound. Tags select verifier paths, costs decide whether the transaction can afford the check, and public inputs or journals bind the proof to the state claim. The covenant or application still has to validate the surrounding transition, observe acceptance, and test negative cases.

This mechanism section separates proof verification from application validity. A verifier result still needs script binding, covenant checks, transaction validity, and accepted-state evidence before an app claim is closed.

How to check it#

When using this page for ZK material, separate proof verification from application validity. Check the verifier path, proof format, public inputs or journal, compute cost, covenant binding, failure cases, and accepted evidence before claiming a transition is valid.

Related Pages#

• zk-groth16-risczero
• 02-inline-zk-covenant-model