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#
Based apps use L1 ordering evidence with off-chain execution and settlement, not generic smart-contract calls. 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, KIP-0021, RK-SEQCOMMIT. 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 Based Apps, the model is built around these anchors: consensus ordering evidence, lane data, and app/runtime payload interpretation must be source-checked separately; off-chain execution reconstructs ordered activity as application responsibility, not base-protocol execution; proof generation may compress settlement claims, but production wording remains unknown until verifier, settlement, and network evidence are attached; L1 covenant settlement verifies only the submitted settlement condition; indexers and proof services carry operational responsibility. 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. consensus ordering evidence, lane data, and app/runtime payload interpretation must be source-checked separately. Sequencing and based-app material depends on ordered accepted activity. The L1 can provide ordering evidence, while off-chain execution, proof generation, settlement, replay, and access-window handling are application responsibilities. The guide should make it clear which layer orders activity, which layer computes state, which layer proves or commits the result, and which source can verify each boundary.
2. off-chain execution reconstructs ordered activity as application responsibility, not base-protocol execution. Sequencing and based-app material depends on ordered accepted activity. The L1 can provide ordering evidence, while off-chain execution, proof generation, settlement, replay, and access-window handling are application responsibilities. The guide should make it clear which layer orders activity, which layer computes state, which layer proves or commits the result, and which source can verify each boundary.
3. Review question (needs checking): proof generation may compress settlement claims, but production wording remains unknown until verifier, settlement, and network evidence are attached. Sequencing and based-app material depends on ordered accepted activity. The L1 can provide ordering evidence, while off-chain execution, proof generation, settlement, replay, and access-window handling are application responsibilities. The guide should make it clear which layer orders activity, which layer computes state, which layer proves or commits the result, and which source can verify each boundary.
4. L1 covenant settlement verifies only the submitted settlement condition. Sequencing and based-app material depends on ordered accepted activity. The L1 can provide ordering evidence, while off-chain execution, proof generation, settlement, replay, and access-window handling are application responsibilities. The guide should make it clear which layer orders activity, which layer computes state, which layer proves or commits the result, and which source can verify each boundary.
5. indexers and proof services carry operational responsibility. 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 consensus ordering evidence, lane data, and app/runtime payload interpretation must be source-checked separately. | Read DOC-TOCCATA-BASED-APPS, KIP-0021, RK-SEQCOMMIT; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 2 | Check off-chain execution reconstructs ordered activity as application responsibility, not base-protocol execution. | Read DOC-TOCCATA-BASED-APPS, KIP-0021, RK-SEQCOMMIT; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 3 | Check proof generation may compress settlement claims, but production wording remains unknown until verifier, settlement, and network evidence are attached. | Read DOC-TOCCATA-BASED-APPS, KIP-0021, RK-SEQCOMMIT; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 4 | Check L1 covenant settlement verifies only the submitted settlement condition. | Read DOC-TOCCATA-BASED-APPS, KIP-0021, RK-SEQCOMMIT; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 5 | Check indexers and proof services carry operational responsibility. | Read DOC-TOCCATA-BASED-APPS, KIP-0021, RK-SEQCOMMIT; 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#
- declarations-and-covenant-macros
- silverscript-vprogs-based-apps
- user-ops-payloads-and-lanes
