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#
RISC Zero Succinct pages explain zkVM receipts, image IDs, journal commitments, seals, and the difference between upstream concepts and Kaspa stack expectations. 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 RISCZERO-PROOF, RISCZERO-RECEIPTS, DOC-TOCCATA-INLINE-ZK. 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 RISC Zero Succinct Overview, the model is built around these anchors: a zkVM proof attests to program execution under an image ID; journal data becomes the public output surface; receipt integrity is an upstream concept; Kaspa source defines accepted stack format; larger runtime tradeoffs need readiness labels. 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 zkVM proof attests to program execution under an image ID. 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.
2. journal data becomes the public output surface. 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. receipt integrity is an upstream concept. 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.
4. Kaspa source defines accepted stack format. 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.
5. larger runtime tradeoffs need readiness labels. Readiness pages are evidence gates. A testnet result is useful only with network name, date, release or branch, node/wallet/tool versions, and accepted evidence. Release notes and source paths support stronger claims; old testnet observations remain historical unless refreshed.
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 a zkVM proof attests to program execution under an image ID. | Read RISCZERO-PROOF, RISCZERO-RECEIPTS, DOC-TOCCATA-INLINE-ZK; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 2 | Check journal data becomes the public output surface. | Read RISCZERO-PROOF, RISCZERO-RECEIPTS, DOC-TOCCATA-INLINE-ZK; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 3 | Check receipt integrity is an upstream concept. | Read RISCZERO-PROOF, RISCZERO-RECEIPTS, DOC-TOCCATA-INLINE-ZK; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 4 | Check Kaspa source defines accepted stack format. | Read RISCZERO-PROOF, RISCZERO-RECEIPTS, DOC-TOCCATA-INLINE-ZK; verify proof format, tag, cost, public input or journal binding, and script failure cases. |
| 5 | Check larger runtime tradeoffs need readiness labels. | Read RISCZERO-PROOF, RISCZERO-RECEIPTS, DOC-TOCCATA-INLINE-ZK; 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#
- 05-groth16-kaspa-verifier-source-path
- zk-groth16-risczero
- 07-risc-zero-kaspa-verifier-source-path