Dated status check

Kaspa status check - May 2026

This May status check now includes a June 29 follow-up for people checking what is live on mainnet, what changed in Toccata release status, what remains roadmap, and which Kaspa claims need tighter wording.

Last checked: June 30, 2026. Status-sensitive claims should be refreshed at emission checkpoints, after new primary source updates, or when app/tooling evidence changes.

Snapshot

What is live now

Base network

Proof of Work, UTXO ownership, blockDAG structure, GHOSTDAG ordering, and Crescendo-era 10 BPS mainnet.

L1 readout

The June 29 public REST check showed kaspa-mainnet, virtual DAA 473,005,279, 1,102,009 blocks, and about 27.542 billion KAS.

Issuance

The public block-reward endpoint returned 2.59565436 KAS per block. The official emission schedule steps down monthly.

What changed

New source notes to add

Official framing

The redesigned Kaspa.org now presents real-time decentralization as the public north-star framing.

Roadmap order

Kaspa.org presents Toccata next, DAGKnight after Toccata, and a separate proposed 2027 hard-fork bucket for 100 BPS and partition-resilient payment work.

Toccata release

Rusty Kaspa v2.0.1 is the current Toccata release. v2.0.0 provides the activation score: DAA 474,165,565, roughly June 30, 2026 at 16:15 UTC.

KIP alignment

KIP-16 and KIP-20 are listed as proposed plus implemented and activated in TN10; KIP-17 and KIP-21 are listed as implemented and activated in TN10 in the June 29 raw KIP check. Treat this as testnet/design evidence. Mainnet activation has its own evidence path.

Open KIP PRs

KIP-24 adds transaction-v1 fields and hashing context for compute budgets, covenant bindings, user lanes, and ZK-friendly txids. KIP-22 proposes P2MR ScriptPublicKey work for quantum-resistance and MAST-style scripts. Both remain open PRs.

TN10 activation tests

Rusty Kaspa's tn10-toc2 pre-release scheduled a Testnet-10 activation point at DAA score 467,579,632. The tn10-toc3 pre-release scheduled final Toccata ZK hardening at DAA score 476,232,000; a June 29 Testnet-10 REST check showed virtual DAA 503,616,667. Treat it as testnet evidence.

Argent

Michael Sutton's Argent repo is early actor-style Silverscript tooling research. Study it as prototype evidence; it is not audited, stable, production-ready, or mainnet activation evidence.

Builder tooling

Python SDK v2.0.0 and v2.0.1 added Toccata-aligned wallet, lane-proof, SMT-sync, and covenant-binding support. Rusty Kaspa's merged ZK SDK PR adds an R0ScriptBuilder helper for RISC Zero proof scripts.

Emission check

The official schedule shows 27.5 KAS/sec from May 8, 25.9565436 from June 7, and 24.49971475 from July 7. "Emission cliff" is loose wording.

Current watchlist

What is pending or later

TrackStatusWhat to verify next
Toccataactivation recordv2.0.1 is the current Toccata release; v2.0.0 provides the activation score. Verify node upgrades and observable post-activation mainnet behavior.
Covenant-style L1 rulesTargetedUse Toccata evidence for L1 rules only; do not describe testnet or proposal evidence as mainnet programmability.
vProgsRoadmapWatch framework progress, developer examples, proof paths, and later activation evidence.
DAGKnightResearchWatch research and implementation branches; do not call it current mainnet consensus.
100 BPS / partition-resilient paymentsResearchWatch for specifications, code, test evidence, and activation records before treating the proposed 2027 bucket as a shipped path.

Claims corrected

Wording fixes this month

Instant finality

Say fast inclusion and probabilistic confirmation confidence.

Toccata activation

Use activated protocol wording after DAA 474,165,565, then keep app and tooling claims separate.

Emission cliff

Say monthly emission step-down and quote the official schedule values.

DAGKnight live

Use research and upgrade-direction language. Current mainnet behavior needs activation evidence.

100 BPS live

Say 10 BPS is live; 100 BPS is a proposed future hard-fork/research bucket.

KIP evidence

Say merged TN10 KIPs are testnet/design evidence. Mainnet activation needs activation records and observed mainnet behavior.

One API is proof

Use public API reads for snapshots, then confirm status changes against releases, KIPs, nodes, and accepted mainnet behavior.

Share links

Use the exact page for the argument