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#
Template pages organize counter, vault, ZK transition, based lane, and dice-style lessons into source-labeled starters. 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-COVENANT-STATE, DOC-TOCCATA-INLINE-ZK, TOOL-SILVERSCRIPT-REPO, TOOL-VPROGS-REPO. 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 Minimal dApp Templates, the model is built around these anchors: templates are learning scaffolds, not upstream-endorsed recipes unless a concrete upstream template is cited; each template needs positive path and negative tests; lane, payload, covenant, wallet, RPC, and indexer fields must be preserved; local lessons are labeled local experience; production use needs fresh upstream review. 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. templates are learning scaffolds, not upstream-endorsed recipes unless a concrete upstream template is cited. Mempool and relay behavior describe what a node is willing to hold, replace, forward, or package; they are not final acceptance. Block templates are candidate work for miners, and they can change as node state or policy changes. The guide names each stage separately: built, signed, submitted, admitted, relayed, templated, mined, and accepted.
2. each template needs positive path and negative tests. Mempool and relay behavior describe what a node is willing to hold, replace, forward, or package; they are not final acceptance. Block templates are candidate work for miners, and they can change as node state or policy changes. The guide names each stage separately: built, signed, submitted, admitted, relayed, templated, mined, and accepted.
3. lane, payload, covenant, wallet, RPC, and indexer fields must be preserved. 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. local lessons are labeled local experience. 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. production use needs fresh upstream review. 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 templates are learning scaffolds, not upstream-endorsed recipes unless a concrete upstream template is cited. | Read DOC-TOCCATA-COVENANT-STATE, DOC-TOCCATA-INLINE-ZK, TOOL-SILVERSCRIPT-REPO; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 2 | Check each template needs positive path and negative tests. | Read DOC-TOCCATA-COVENANT-STATE, DOC-TOCCATA-INLINE-ZK, TOOL-SILVERSCRIPT-REPO; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 3 | Check lane, payload, covenant, wallet, RPC, and indexer fields must be preserved. | Read DOC-TOCCATA-COVENANT-STATE, DOC-TOCCATA-INLINE-ZK, TOOL-SILVERSCRIPT-REPO; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 4 | Check local lessons are labeled local experience. | Read DOC-TOCCATA-COVENANT-STATE, DOC-TOCCATA-INLINE-ZK, TOOL-SILVERSCRIPT-REPO; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 5 | Check production use needs fresh upstream review. | Read DOC-TOCCATA-COVENANT-STATE, DOC-TOCCATA-INLINE-ZK, TOOL-SILVERSCRIPT-REPO; 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#
- settlement-and-indexer-responsibility
- silverscript-vprogs-based-apps
- tooling-readiness-and-production-caveats