In brief
Historical testnet pages preserve context without turning old network behavior into current instructions.
What this page explains#
Historical testnet pages preserve context without turning old network behavior into current instructions. 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, DOC-TOCCATA, RK-PARAMS, RK-RELEASE-V2-0-0. 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 TN10, TN11, And Historical Testnet Context, the model is built around these anchors: TN10 and TN11 are currently documented public testnet contexts when supported by Kaspa documentation and params evidence; endpoint availability remains an observation, not a protocol fact; Toccata-era experiments should not be generalized to mainnet; dates and source refresh notes are required; current testnet guidance lives on separate pages. 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. TN10 and TN11 are currently documented public testnet contexts when supported by Kaspa documentation and params evidence. 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.
2. endpoint availability remains an observation, not a protocol fact. 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.
3. Toccata-era experiments should not be generalized to mainnet. 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.
4. dates and source refresh notes are required. 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. current testnet guidance lives on separate pages. 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 TN10 and TN11 are currently documented public testnet contexts when supported by Kaspa documentation and params evidence. | Use WIKI-TESTNETS, DOC-TOCCATA, RK-PARAMS; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 2 | Check endpoint availability remains an observation, not a protocol fact. | Use WIKI-TESTNETS, DOC-TOCCATA, RK-PARAMS; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 3 | Check Toccata-era experiments should not be generalized to mainnet. | Use WIKI-TESTNETS, DOC-TOCCATA, RK-PARAMS; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 4 | Check dates and source refresh notes are required. | Use WIKI-TESTNETS, DOC-TOCCATA, RK-PARAMS; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 5 | Check current testnet guidance lives on separate pages. | Use WIKI-TESTNETS, DOC-TOCCATA, RK-PARAMS; 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
- testnets-production-readiness
- tn12-covenant-testnet