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#
The Kaspa Groth16 source path explains verifying key/proof data, public input arity, metering, parsing, and verification failure cases. 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 RK-ZK-GROTH16, RK-ZK-GROTH16-ERRORS, RK-ZK-TXSCRIPT-TESTS, RK-ZK-TAGS, ARK-GROTH16. 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 Groth16 Kaspa Verifier Source Path, the model is built around these anchors: stack order, verifying key, proof, public-input count, and public inputs are source-level review items; public input count and field validity matter; arity mismatches fail; trailing bytes and malformed data are negative cases; verifier success still does not validate successor output by itself. 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. stack order, verifying key, proof, public-input count, and public inputs are source-level review items. Script validation still owns the surrounding transaction rule. Even if a proof verifies, the script must receive the expected stack items, check the relevant transaction context, and enforce the successor output or state commitment that the application requires.
2. public input count and field validity matter. Groth16 material should identify the statement, circuit, verifying key, proof bytes, and public inputs before discussing Kaspa script integration. A valid Groth16 proof means the verifier accepted that statement under that key and input set. It does not by itself prove that the successor output, covenant ID, network, fee, or accepted-state evidence is correct.
3. arity mismatches fail. Groth16 material should identify the statement, circuit, verifying key, proof bytes, and public inputs before discussing Kaspa script integration. A valid Groth16 proof means the verifier accepted that statement under that key and input set. It does not by itself prove that the successor output, covenant ID, network, fee, or accepted-state evidence is correct.
4. trailing bytes and malformed data are negative cases. Groth16 material should identify the statement, circuit, verifying key, proof bytes, and public inputs before discussing Kaspa script integration. A valid Groth16 proof means the verifier accepted that statement under that key and input set. It does not by itself prove that the successor output, covenant ID, network, fee, or accepted-state evidence is correct.
5. verifier success still does not validate successor output by itself. 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.
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 stack order, verifying key, proof, public-input count, and public inputs are source-level review items. | Read RK-ZK-GROTH16, RK-ZK-GROTH16-ERRORS, RK-ZK-TXSCRIPT-TESTS; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 2 | Check public input count and field validity matter. | Read RK-ZK-GROTH16, RK-ZK-GROTH16-ERRORS, RK-ZK-TXSCRIPT-TESTS; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 3 | Check arity mismatches fail. | Read RK-ZK-GROTH16, RK-ZK-GROTH16-ERRORS, RK-ZK-TXSCRIPT-TESTS; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 4 | Check trailing bytes and malformed data are negative cases. | Read RK-ZK-GROTH16, RK-ZK-GROTH16-ERRORS, RK-ZK-TXSCRIPT-TESTS; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 5 | Check verifier success still does not validate successor output by itself. | Read RK-ZK-GROTH16, RK-ZK-GROTH16-ERRORS, RK-ZK-TXSCRIPT-TESTS; 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#
- 04-groth16-overview
- zk-groth16-risczero
- 06-risc-zero-succinct-overview