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 vProgs ZK pipeline connects transaction processing, batch aggregation, proof generation, journal/state transition, and settlement as tooling or architecture material, not as base-protocol authority. This page sits in SilverScript, vProgs, And Based Apps. 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 distinguishes tooling convenience from protocol behavior. SilverScript can author or lower scripts, vProgs can organize based-app execution, and settlement/indexer responsibilities remain part of the application design.
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 TOOL-VPROGS-ZK, TOOL-VPROGS-README, 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 vProgs ZK Pipeline, the model is built around these anchors: transaction processor consumes ordered activity in the vProgs architecture at the pinned tooling source; batch processor and aggregator shape proof inputs in the tooling architecture; RISC Zero backend creates proof evidence as prototype/operator-dependent tooling; journal and state transition must bind to settlement before a public app-validity claim is promoted; Kaspa covenant and ZK source still validate only submitted L1 conditions. 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. transaction processor consumes ordered activity in the vProgs architecture at the pinned tooling source. vProgs and settlement pages are application-architecture pages. They have to say who observes ordered activity, who computes state, who produces proofs or attestations, who submits settlement, and how restart or replay recovers evidence. That responsibility map is as important as the success path.
2. batch processor and aggregator shape proof inputs in the tooling architecture. vProgs and settlement pages are application-architecture pages. They have to say who observes ordered activity, who computes state, who produces proofs or attestations, who submits settlement, and how restart or replay recovers evidence. That responsibility map is as important as the success path.
3. RISC Zero backend creates proof evidence as prototype/operator-dependent tooling. vProgs and settlement pages are application-architecture pages. They have to say who observes ordered activity, who computes state, who produces proofs or attestations, who submits settlement, and how restart or replay recovers evidence. That responsibility map is as important as the success path.
4. journal and state transition must bind to settlement before a public app-validity claim is promoted. vProgs and settlement pages are application-architecture pages. They have to say who observes ordered activity, who computes state, who produces proofs or attestations, who submits settlement, and how restart or replay recovers evidence. That responsibility map is as important as the success path.
5. Kaspa covenant and ZK source still validate only submitted L1 conditions. vProgs and settlement pages are application-architecture pages. They have to say who observes ordered activity, who computes state, who produces proofs or attestations, who submits settlement, and how restart or replay recovers evidence. That responsibility map is as important as the success path.
This mechanism section separates authoring tools, runtime organization, proof workflow, indexer replay, and L1 settlement. Tooling convenience does not become protocol behavior without upstream source support.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check transaction processor consumes ordered activity in the vProgs architecture at the pinned tooling source. | Read TOOL-VPROGS-ZK, TOOL-VPROGS-README, RISCZERO-PROOF; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 2 | Check batch processor and aggregator shape proof inputs in the tooling architecture. | Read TOOL-VPROGS-ZK, TOOL-VPROGS-README, RISCZERO-PROOF; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 3 | Check RISC Zero backend creates proof evidence as prototype/operator-dependent tooling. | Read TOOL-VPROGS-ZK, TOOL-VPROGS-README, RISCZERO-PROOF; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 4 | Check journal and state transition must bind to settlement before a public app-validity claim is promoted. | Read TOOL-VPROGS-ZK, TOOL-VPROGS-README, RISCZERO-PROOF; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 5 | Check Kaspa covenant and ZK source still validate only submitted L1 conditions. | Read TOOL-VPROGS-ZK, TOOL-VPROGS-README, RISCZERO-PROOF; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
When using this page for tooling or based-app work, identify which layer authors scripts, observes ordering, computes state, produces proof material, submits settlement, and recovers after restart. Tool output and runtime architecture need L1 source or settlement evidence before they become protocol claims.
Related Pages#
- vprogs-architecture
- silverscript-vprogs-based-apps
- settlement-and-indexer-responsibility