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#
Tooling readiness pages keep moving APIs, pre-check tools, wallet support, and mainnet safety gates visible. 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, TOOL-SILVERSCRIPT-README, TOOL-VPROGS-README, TOOL-SILVERSCRIPT-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 Tooling Readiness And Production Caveats, the model is built around these anchors: SilverScript carries experimental tooling caveats that must stay visible; vProgs architecture is prototype/readiness-sensitive until pinned source and demo evidence are refreshed; wallet SDK field preservation is a readiness gate; mainnet-facing claims need release and source details; Open Questions remain visible until independently closed. 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 carries experimental tooling caveats that must stay visible. SilverScript pages help readers author and inspect scripts while preserving the protocol boundary. A compiler or macro can generate useful script structure, but generated output still has to be reviewed against txscript, covenant context, pricing, signing, and negative tests.
2. vProgs architecture is prototype/readiness-sensitive until pinned source and demo evidence are refreshed. Readiness pages are evidence gates. A testnet result is useful only with network name, date, release or branch, node/wallet/tool versions, and accepted evidence. Release notes and source paths support stronger claims; old testnet observations remain historical unless refreshed.
3. wallet SDK field preservation is a readiness gate. 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. mainnet-facing claims need release and source details. Readiness pages are evidence gates. A testnet result is useful only with network name, date, release or branch, node/wallet/tool versions, and accepted evidence. Release notes and source paths support stronger claims; old testnet observations remain historical unless refreshed.
5. Open Questions remain visible until independently closed. 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 SilverScript carries experimental tooling caveats that must stay visible. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, TOOL-SILVERSCRIPT-README; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 2 | Check vProgs architecture is prototype/readiness-sensitive until pinned source and demo evidence are refreshed. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, TOOL-SILVERSCRIPT-README; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 3 | Check wallet SDK field preservation is a readiness gate. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, TOOL-SILVERSCRIPT-README; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 4 | Check mainnet-facing claims need release and source details. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, TOOL-SILVERSCRIPT-README; label tooling/runtime behavior separately from L1 settlement or protocol enforcement. |
| 5 | Check Open Questions remain visible until independently closed. | Read DOC-TOCCATA-SILVERSCRIPT, DOC-TOCCATA-BASED-APPS, TOOL-SILVERSCRIPT-README; 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#
- minimal-dapp-templates
- silverscript-vprogs-based-apps