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#
Explain authoring, compiler/lowering, based app architecture, vProgs runtime layers, settlement, indexers, and readiness caveats. 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-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE, TOOL-SILVERSCRIPT-REPO, TOOL-SILVERSCRIPT-README. 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 SilverScript, vProgs, And Based Apps, the model is built around these anchors: SilverScript authoring is a convenience layer for writing covenant scripts, not a replacement for protocol review.; Compiler and lowering pages explain how higher-level declarations become scripts and what still needs manual review.; Declaration macros are teaching aids for common covenant patterns, but their output must still be reviewed against state rules.; Based apps use L1 ordering evidence with off-chain execution and settlement, not generic smart-contract calls.; User operation pages teach payload encoding, gas, lane namespace, and ordering evidence.. 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. SilverScript authoring is a convenience layer for writing covenant scripts, not a replacement for protocol review.. 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. Compiler and lowering pages explain how higher-level declarations become scripts and what still needs manual review.. 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. Declaration macros are teaching aids for common covenant patterns, but their output must still be reviewed against state rules.. 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. Based apps use L1 ordering evidence with off-chain execution and settlement, not generic smart-contract calls.. 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. User operation pages teach payload encoding, gas, lane namespace, and ordering evidence.. 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.
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 SilverScript authoring is a convenience layer for writing covenant scripts, not a replacement for protocol review.. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 2 | Check Compiler and lowering pages explain how higher-level declarations become scripts and what still needs manual review.. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 3 | Check Declaration macros are teaching aids for common covenant patterns, but their output must still be reviewed against state rules.. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 4 | Check Based apps use L1 ordering evidence with off-chain execution and settlement, not generic smart-contract calls.. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 5 | Check User operation pages teach payload encoding, gas, lane namespace, and ordering evidence.. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, DOC-TOCCATA-DECISION-GUIDE; 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.
Expanded Category Guide#
This category carries tooling and application architecture. It should explain SilverScript, vProgs, based apps, payloads, lanes, settlement, and indexer responsibility without treating tooling as base protocol proof.
Use this category as a curated path. Start with the category README to understand the boundary, then read the mechanism pages, then follow source-path or open-gap pages for claims that need stronger evidence. If a page contains needs checking rows, keep those claims visibly unresolved until a reader reads the cited public source directly.
The category should not be treated as final authority by folder name alone. The authority comes from page Source Notes, Source Lists, public URLs, and the status labels attached to each claim.
Related Pages#
- silverscript-vprogs-based-apps
- silverscript-authoring
Topic pages#
- SilverScript Authoring: SilverScript authoring is a convenience layer for writing covenant scripts, not a replacement for protocol review.
- SilverScript Compiler And Lowering: Compiler and lowering pages explain how higher-level declarations become scripts and what still needs manual review.
- Declarations And Covenant Macros: Declaration macros are teaching aids for common covenant patterns, but their output must still be reviewed against state rules.
- Based Apps: Based apps use L1 ordering evidence with off-chain execution and settlement, not generic smart-contract calls.
- User Ops, Payloads, And Lanes: User operation pages teach payload encoding, gas, lane namespace, and ordering evidence.
- Based Lane Starter: A based lane starter walks from lane design to ordering observation and settlement evidence.
- vProgs Architecture: vProgs is treated as evolving reference/runtime work that needs tooling-readiness labels.
- vProgs ZK Pipeline: 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.
- Settlement And Indexer Responsibility: Settlement pages answer who reconstructs activity, who proves it, who submits it, and who tracks state after restart.
- Minimal dApp Templates: Template pages organize counter, vault, ZK transition, based lane, and dice-style lessons into source-labeled starters.
- Tooling Readiness And Production Caveats: Tooling readiness pages keep moving APIs, pre-check tools, wallet support, and mainnet safety gates visible.
Topic notes#
This category is accepted when the subpages explain the actual topics, not merely the source links. Each subpage carries public source IDs, claim labels, Open Questions, and a path from first contact into source review.