Swarm.
Emission status, observed TAO and the evidence behind each change.
Updated 8 Sep 2026, 12:25 UTCFinalized block 9,022,735
- SN124 · TAO emission switch
- Enabled
- Share of network TAO delivered
- 1.32%
- Subnet TAO · latest block
- 0.006599 τ
SN124 changes.
Historical coverage is partial. See coverage & method ↗
No verified changes in this selection yet. See coverage below.
Subnet details.
| Subnet | TAO status | TAO · latest block | Share of delivered TAO | Last verified change |
|---|---|---|---|---|
| SN124Swarm | Enabled | 0.006599 τ | 1.32% | Not yet indexed |
Enabled is the root-controlled switch. It does not promise a positive payment. Amounts are one-block observations.
Know what you’re looking at.
Amounts describe one finalized block. Historical coverage is partial; published explanations are verified separately from chain events.
Read the measurement and coverage details
Continuous event scanning begins after block 9,022,219. Indexed through 9,022,735 (8 Sep 2026, 12:25 UTC). Earlier history is reconstructed from roughly daily samples and verified against individual events. Brief off/on cycles can be missing from that backfill. No recorded change does not prove that none occurred.
TAO delivered is SubnetTaoInEmission + SubnetExcessTao at the displayed finalized block: pool injections and executed chain buys. Its percentage uses the sum across registered non-root subnets. Pool injections may include earlier emissions released from a reservoir. These observed flows are not a nominal allocation, daily total or estimate of miner income.
Participant alpha emissions are separate and available in the API. Turning off the TAO switch does not necessarily stop alpha rewards. Subnet numbers can be reused; current status includes the registration block, while events retain their historical block evidence. Names are the latest available labels, not historical identity records.
Source failures keep the last successful snapshot visible as delayed. An unavailable value is never treated as a suspension. Reasons require a published statement; chain events alone do not explain a decision.
Official switch documentation ↗ · Event implementation ↗ · Snapshot JSON ↗ · OpenAPI ↗