RISC Zero Succinct Transition Starter

What this page explains#

The RISC Zero starter is a conceptual checklist until a concrete public upstream recipe is verified, and it makes image ID, journal digest, receipt/seal, and verifier boundaries explicit. 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-RISC0, RK-ZK-RISC0-RCPT, RK-ZK-RISC0-CLAIM, RISCZERO-RECEIPTS. 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 Transition Starter, the model is built around these anchors: define the zkVM program image; bind journal output to state transition; serialize receipt, seal, claim, image, journal, and verifier inputs for Kaspa source expectations; budget verification work; test wrong image, wrong journal, wrong successor, and stale head as review guidance. 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. define the zkVM program image. 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. bind journal output to state transition. A proof output is useful only when the application binds it to the old state, new state, covenant ID or script context, and public input or journal. Without that binding, a valid proof may still be irrelevant to the UTXO transition being spent.

3. serialize receipt, seal, claim, image, journal, and verifier inputs for Kaspa source expectations. 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. budget verification work. 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.

5. test wrong image, wrong journal, wrong successor, and stale head as review guidance. 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#

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#

• 10-groth16-transition-starter
• zk-groth16-risczero
• 12-testing-evidence-and-readiness