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#
Settlement pages answer who reconstructs activity, who proves it, who submits it, and who tracks state after restart. 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 DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE, RK-INDEXES, RK-VIRTUAL-PIPELINE, TOOL-VPROGS-ARCH. 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 Settlement And Indexer Responsibility, the model is built around these anchors: indexers recover accepted activity; execution services produce deterministic state transitions; proof services compress or attest computation; L1 scripts verify submitted settlement conditions rather than indexer state itself; restart and replay evidence is part of app safety. 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. indexers recover accepted activity. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
2. execution services produce deterministic state transitions. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
3. proof services compress or attest computation. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
4. L1 scripts verify submitted settlement conditions rather than indexer state itself. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
5. restart and replay evidence is part of app safety. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
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 indexers recover accepted activity. | Read DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE, RK-INDEXES; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 2 | Check execution services produce deterministic state transitions. | Read DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE, RK-INDEXES; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 3 | Check proof services compress or attest computation. | Read DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE, RK-INDEXES; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 4 | Check L1 scripts verify submitted settlement conditions rather than indexer state itself. | Read DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE, RK-INDEXES; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 5 | Check restart and replay evidence is part of app safety. | Read DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE, RK-INDEXES; 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-zk-pipeline
- silverscript-vprogs-based-apps
- minimal-dapp-templates