In brief
Testnets are environments for testing network behavior, not proof of mainnet behavior.
What this page explains#
Testnets are environments for testing network behavior, not proof of mainnet behavior. 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 WIKI-TESTNETS, RK-TESTNET12, DOC-TOCCATA, RK-NETWORK, RK-ADDRESSES. 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 Testnets, the model is built around these anchors: record both the Rusty Kaspa NetworkId or CLI suffix and the address prefix; testnet addresses use the testnet prefix while the numeric testnet is network context rather than address-prefix context; faucets and explorers are volatile resources; testnet evidence needs timestamps; mainnet claims need separate release/source details. 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. record both the Rusty Kaspa NetworkId or CLI suffix and the address prefix. 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. testnet addresses use the testnet prefix while the numeric testnet is network context rather than address-prefix context. 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.
3. faucets and explorers are volatile resources. 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. testnet evidence needs timestamps. 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. mainnet claims need separate release/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.
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 record both the Rusty Kaspa NetworkId or CLI suffix and the address prefix. | Use WIKI-TESTNETS, RK-TESTNET12, DOC-TOCCATA; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 2 | Check testnet addresses use the testnet prefix while the numeric testnet is network context rather than address-prefix context. | Use WIKI-TESTNETS, RK-TESTNET12, DOC-TOCCATA; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 3 | Check faucets and explorers are volatile resources. | Use WIKI-TESTNETS, RK-TESTNET12, DOC-TOCCATA; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 4 | Check testnet evidence needs timestamps. | Use WIKI-TESTNETS, RK-TESTNET12, DOC-TOCCATA; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 5 | Check mainnet claims need separate release/source details. | Use WIKI-TESTNETS, RK-TESTNET12, DOC-TOCCATA; 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#
- testnets-production-readiness
- tn10-tn11-and-historical-testnet-context