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#
TN12 covenant-testnet guidance is source-sensitive and must name network selection, branch or release assumptions, and evidence checks. This page sits in Testnets And Production Readiness. 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 treats readiness as evidence discipline. Testnet success, explorer observations, wallet signing, release checks, and production review each answer different questions and must not be substituted for each other.
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 RK-TESTNET12, DOC-TOCCATA, RK-NETWORK, RK-ADDRESSES, RK-RELEASE-V2-0-1. 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 TN12 Covenant Testnet, the model is built around these anchors: testnet suffix and address context are the first checks; node and wallet commands require current source details; faucets, explorers, and APIs are volatile; do not copy upstream sample private keys or locally generated key material into this guide; use placeholders; accepted evidence must be timestamped. 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. testnet suffix and address context are the first checks. Network identity is the first readiness check. The page records the exact testnet or mainnet context, address prefix or suffix assumptions, node command or release, and the endpoint being observed so that evidence from one network is not reused as evidence for another.
2. node and wallet commands require current source details. Commands are current-state-sensitive. A guide can describe the shape of the workflow, but exact commands need a checked release, branch, or docs page, plus the node sync state and wallet version used for the observation.
3. faucets, explorers, and APIs are volatile. Faucets, explorers, and hosted APIs are volatile service surfaces. They can provide timestamped observations, but they do not define consensus behavior. The page records retrieval date, endpoint, network, response shape, and the source path that backs any stronger protocol claim.
4. do not copy upstream sample private keys or locally generated key material into this guide; use placeholders. Readiness examples must never publish real private keys, seeds, mnemonics, or funded wallet material. Test examples should use placeholders or regenerated throwaway context, and any local secret handling stays outside public wiki citations.
5. accepted evidence must be timestamped. Accepted evidence needs a timestamped chain of custody: built transaction, signed transaction, broadcast or submission result, accepted transaction or UTXO-state evidence, and any explorer or indexer observation used to confirm it. Local logs alone stay scoped to local experience.
This mechanism section treats readiness as dated evidence: network, release, branch or commit, tool version, observation, and accepted/rejected result are all part of the claim.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check testnet suffix and address context are the first checks. | Use RK-TESTNET12, DOC-TOCCATA, RK-NETWORK; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 2 | Check node and wallet commands require current source details. | Use RK-TESTNET12, DOC-TOCCATA, RK-NETWORK; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 3 | Check faucets, explorers, and APIs are volatile. | Use RK-TESTNET12, DOC-TOCCATA, RK-NETWORK; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 4 | Check do not copy upstream sample private keys or locally generated key material into this guide; use placeholders. | Use RK-TESTNET12, DOC-TOCCATA, RK-NETWORK; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 5 | Check accepted evidence must be timestamped. | Use RK-TESTNET12, DOC-TOCCATA, RK-NETWORK; add date, network, release or commit, tool version, and accepted/rejected evidence. |
When using this page for readiness, record the date, network, release or commit, tool versions, endpoint or explorer observation, and accepted or rejected result. Testnet success, local logs, and live API observations remain scoped evidence until release and source checks support broader wording.
Related Pages#
- tn10-tn11-and-historical-testnet-context
- testnets-production-readiness
- tn10-tn12-readiness