Release notes and code need to identify the rules that nodes will enforce.
Toccata status
Kaspa Toccata status.
Toccata is the hard-fork track for covenant-style Kaspa programmability. As of May 15, 2026, public sources describe it as TN12/testnet work ahead of mainnet activation, not as live mainnet behavior.
Citable summary: Toccata targets Kaspa L1 covenants, ZK proof hooks, sequencing commitments, and based-app foundations; call it pending until release and mainnet activation evidence exists.
Current state
Status by area.
The activation path needs explicit parameters, date, height, score, or equivalent network logic.
Mainnet transactions, wallet flows, indexer reads, and explorer behavior need to show the new rules after activation.
What would make this live: release, activation parameters, upgraded node behavior, observable mainnet behavior, and wallet or tooling support.
| Area | Status | What it means |
|---|---|---|
| TN12 covenant testing | Testnet | Useful evidence for developer flows and opcode testing, but not mainnet activation. |
| Silverscript | Targeted | High-level scripting language and examples for native Kaspa Script work. |
| KIP-21 sequencing commitments | Targeted | Helps apps prove the activity they care about without replaying the full DAG. As of May 15, 2026, keep final-interface wording conditional until KIP, release, and activation artifacts agree. |
| zk verification hooks | Targeted | Proof checks can help app verification, but external facts still need anchors. |
| Mainnet activation | Pending | Needs release, rehearsal, activation logic, hardcoded date or parameters, and observable mainnet behavior. |
| Full vProgs composition | Roadmap | Later architecture for richer app-to-app behavior, not the immediate Toccata surface. |
Wording
Use this wording.
As of May 15, 2026, Toccata should be described as a targeted hard-fork track with live TN12 testing, not as activated Kaspa mainnet behavior. Mainnet claims need release and activation evidence.
Vault rules, asset rules, escrow paths, assurance contracts, proof checks, sequencing commitments, and standalone based-app foundations.
Mature native DeFi, full vProgs, full app-to-app atomic composition, or production wallet/indexer readiness.
TN12 status, KIP-21 proposal state, branch merge, audit/rehearsal, release notes, activation parameters, SDK support, wallet support, and indexer support.