In brief
This page is source-sensitive. Treat application, covenant, proof, and readiness wording as bounded by the listed public sources and Open Questions.
What this page explains#
Tags and costs are high-risk source claims because they decide which verifier runs and whether the transaction has enough budget. 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, RK-ZK-TAGS, RK-ZK-PRECOMPILES-MOD, RK-OPCODES, RK-MASS. 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 OpZkPrecompile Tags And Costs, the model is built around these anchors: the ZK precompile opcode and enabled-covenant context come from opcode and precompile source paths; Groth16 and RISC Zero Succinct use different source-defined tags; unknown tags fail by source-defined rules; base costs and per-input costs affect compute budget; cost constants require source refresh before exact numbers are published. 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. the ZK precompile opcode and enabled-covenant context come from opcode and precompile source paths. ZK-and-covenant pages are about binding a verified statement to the state transition the application actually cares about. The proof may check a statement, but the script still has to bind the prior state, successor output, verifier identity, public input or journal, fee/resource context, and accepted-state evidence.
2. Groth16 and RISC Zero Succinct use different source-defined tags. RISC Zero Succinct material has a different shape from circuit-specific Groth16. The image ID, journal or digest, receipt/seal data, claim data, and verifier assumptions define what execution claim is being checked. The Kaspa-facing page must then connect that checked claim to script stack format, compute cost, covenant binding, negative cases, and accepted-state evidence.
3. unknown tags fail by source-defined rules. 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. base costs and per-input costs affect compute budget. Proof verification consumes metered script work. The page has to connect verifier tags and proof sizes to pricing or mass evidence, then show how under-budget, malformed, or mismatched verifier inputs fail before accepted-state claims are made.
5. cost constants require source refresh before exact numbers are published. Proof verification consumes metered script work. The page has to connect verifier tags and proof sizes to pricing or mass evidence, then show how under-budget, malformed, or mismatched verifier inputs fail before accepted-state claims are made.
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#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check the ZK precompile opcode and enabled-covenant context come from opcode and precompile source paths. | Read DOC-TOCCATA-INLINE-ZK, RK-ZK-TAGS, RK-ZK-PRECOMPILES-MOD; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 2 | Check Groth16 and RISC Zero Succinct use different source-defined tags. | Read DOC-TOCCATA-INLINE-ZK, RK-ZK-TAGS, RK-ZK-PRECOMPILES-MOD; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 3 | Check unknown tags fail by source-defined rules. | Read DOC-TOCCATA-INLINE-ZK, RK-ZK-TAGS, RK-ZK-PRECOMPILES-MOD; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 4 | Check base costs and per-input costs affect compute budget. | Read DOC-TOCCATA-INLINE-ZK, RK-ZK-TAGS, RK-ZK-PRECOMPILES-MOD; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 5 | Check cost constants require source refresh before exact numbers are published. | Read DOC-TOCCATA-INLINE-ZK, RK-ZK-TAGS, RK-ZK-PRECOMPILES-MOD; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
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#
- 02-inline-zk-covenant-model
- zk-groth16-risczero
- 04-groth16-overview