Use for behavior available on Kaspa mainnet now: Proof of Work, UTXO ownership, GHOSTDAG ordering, Crescendo-era 10 BPS, wallets, nodes, and explorers.
Claims reference
Claims need a status label
A claim without a label invites confusion. Put it in one lane first: live mainnet, testnet evidence, targeted upgrade, roadmap, research, unsupported, or out of scope.
Last checked: June 30, 2026.
How to use it
Start with the claim, then ask what evidence it has
App and project catalog context stays outside this site's status labels unless the claim is specifically about L1 transaction data, accepted transactions, or miner fees.
Use for TN10/TN12 activation or covenant proof work, accepted testnet transactions, rejected mutation cases, and developer-flow evidence. It does not prove mainnet activation.
Use for near-term work when release artifacts, activation parameters, or implementation evidence exist but mainnet behavior still needs a current check.
Use for vProgs, full cross-app composition, and richer app architecture that still needs shipped software and users.
Use for DAGKnight, 100 BPS research, partition-resilient payments, RTD-derived oracle/attestation flows, TangVM, and coordination-market systems.
Copy rules
Status comes first
| Topic | Safe wording | Avoid |
|---|---|---|
| Finality | Fast mined inclusion and probabilistic confirmation confidence. | Instant finality or immediate irreversibility. |
| Polychain | Polychain belongs in the VC-funded DAGLabs prehistory. Premine and pre-sale allocation claims need separate token-allocation evidence. | Ignoring Polychain context or treating it as proof of a premine. |
| Fair launch | No premine, insider allocation, or pre-sales; every coin came from mining, including the post-launch DAGLabs/Polychain-related early mining estimate. | DAGLabs/Polychain premine language, flawless distribution, or no early contributor mining. |
| Original codebase | Original Kaspad was Golang and source-backed as an adaptation of btcd. | A specific Bitcoin Core version without a durable source. |
| App and project tooling | Out of scope unless the claim is specifically about L1 transaction data, accepted transactions, or miner fees. | App activity proves mainnet activation or native smart contracts. |
| TN10 | Testnet-10 Toccata activation and hardening evidence, including tn10-toc2 and tn10-toc3. | TN10 test activation is mainnet activation. |
| TN12 | Testnet evidence for covenant developer flows and opcode testing. | TN12 txids or rejections prove mainnet covenant enforcement. |
| Toccata | Rusty Kaspa v2.0.1 is the current Toccata release. Rusty Kaspa v2.0.0 sets the activation score at DAA score 474,165,565. KIP/TN10 evidence is testnet/design evidence; the mainnet label comes from the activation record and upgraded-node behavior. | Mainnet Toccata has activated just because the release exists. |
| Emission | Monthly step-down schedule; May 2026 is 27.5 KAS/sec, June 7 is 25.9565436 KAS/sec, and July 7 is 24.49971475 KAS/sec. | July 2026 is a one-day emission cliff. |
| vProgs | Later app architecture for apps that prove richer logic while sharing Kaspa ordering. | Mainnet app infrastructure has already shipped. |
| Argent | Experimental actor-style frontend for Silverscript covenant contracts. | Argent proves production smart contracts, audits, a stable ABI, or mainnet activation. |
| DAGKnight | Research and future consensus direction. | DAGKnight is current mainnet behavior. |
| ZK hooks | ZK can prove computation over chosen inputs; external facts still need anchors. | A proof alone proves prices, other chains, reserves, or real-world events. |
Editor rule
One sentence test catches most mistakes
If a sentence adds no actor, action, evidence, status label, constraint, consequence, distinction, or reader judgment, delete it.
Keep public wording tied to Status, Claims, and Sources. Use one status label, then write the point directly.