Vault Covenant Starter

What this page explains#

A vault starter is design-question guidance until a concrete upstream vault implementation, wallet flow, and accepted-evidence path are verified. This page sits in Covenants. 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 keeps the UTXO model visible while explaining stateful patterns. A covenant does not mutate account storage in place; it validates a spend and the successor output that carries the next state.

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, RK-COVENANTS, RK-WALLET. 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 Vault Covenant Starter, the model is built around these anchors: owner authorization must be explicit and source-backed before the pattern is promoted; delay or recovery logic remains design guidance until a concrete upstream vault implementation is checked; successor value policy is safety-critical and remains unknown without script-level negative tests; wallet signing and accepted evidence are separate; production use needs independent 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. Review question (needs checking): owner authorization must be explicit and source-backed before the pattern is promoted. Covenant mechanics stay anchored in UTXOs, but the page's main question is state continuity. The current output is spent, the script inspects transaction context, and the successor output must carry the allowed next state. Covenant IDs, authorization groups, script context, and indexer head tracking are helper surfaces; they do not replace the actual successor validation rule.

2. Review question (needs checking): delay or recovery logic remains design guidance until a concrete upstream vault implementation is checked. Covenant mechanics stay anchored in UTXOs, but the page's main question is state continuity. The current output is spent, the script inspects transaction context, and the successor output must carry the allowed next state. Covenant IDs, authorization groups, script context, and indexer head tracking are helper surfaces; they do not replace the actual successor validation rule.

3. Review question (needs checking): successor value policy is safety-critical and remains unknown without script-level negative tests. Covenant mechanics stay anchored in UTXOs, but the page's main question is state continuity. The current output is spent, the script inspects transaction context, and the successor output must carry the allowed next state. Covenant IDs, authorization groups, script context, and indexer head tracking are helper surfaces; they do not replace the actual successor validation rule.

4. wallet signing and accepted evidence are separate. Covenant mechanics stay anchored in UTXOs, but the page's main question is state continuity. The current output is spent, the script inspects transaction context, and the successor output must carry the allowed next state. Covenant IDs, authorization groups, script context, and indexer head tracking are helper surfaces; they do not replace the actual successor validation rule.

5. production use needs independent review. Covenant mechanics stay anchored in UTXOs, but the page's main question is state continuity. The current output is spent, the script inspects transaction context, and the successor output must carry the allowed next state. Covenant IDs, authorization groups, script context, and indexer head tracking are helper surfaces; they do not replace the actual successor validation rule.

This mechanism section keeps the covenant rule, the spent output, the successor output, covenant ID, authorization context, and indexer responsibility separate. Local case studies stay local experience unless rewritten against public sources.

How to check it#

When using this page for covenant design, verify the spent output, script context, authorization rule, successor output, state encoding, and negative cases separately. Indexer head tracking and local design notes are supporting evidence, not replacements for the covenant rule.

Related Pages#

• counter-covenant-starter
• covenants
• dice-rollregistry-case-study