TAO—Block—Subnets85 / 128active
Repo text not synced yet — the worker fetches it on its schedule.
What miners actually race on — the mission definition, its tasks and scoring, and the mission-score board. Not the same thing as emission share.
Taonets hasn't verified where this subnet's race mission lives yet and the chain registration names no repo at all. The repo watch below tracks the registered repo only.
What the validator network actually scored this epoch — read from the chain's Incentive vector, normalized on chain.
Winner-take-all right now: the whole incentive — and with it essentially all emission — lands on a single uid. That is why concentration views here show a ~100% top share: it's the payout structure of this race, not an anomaly.
These are each miner's normalized incentive from the chain's Incentive vector — the only race score Bittensor stores. It is a share of the validators' consensus weight: all rows sum to 1, so uid #56's 0.802 on Minos means it holds 80.2% of the validated weight — and since emission follows incentive exactly, it also takes ~80% of the miner-side payout. There is no absolute score (an “87/100”) on chain; numbers like that live in each subnet's own off-chain platform. Uids absent from the list received zero validated weight this epoch.
Absolute submission scores (an “87/100”) are computed by validators off chain and never published on chain — subtensor no longer even stores a pre-normalization Scores vector, so the incentive shares above are the only race score that exists on chain. When a subnet publishes scores through its own mission API, they appear in the mission panel above instead.
live chain reads
scores read 4d ago · block 9,485,346 · epoch 26,348
and what they can't
Incentive is the score the validator network converged on for each uid this epoch — it's what pays: emission follows it. It is normalized on chain to sum to 1, so it reads as a share of validated weight. Hidden per-validator test sets (e.g. a private eval split) are computed off chain and never published — the chain no longer even stores a pre-normalization Scores vector — so taonets shows exactly what the chain shows, no reconstruction.
did the race change? the head commit is the probe
Repo watch is bootstrapping — the worker is registering every registered repo's current head commit as its baseline (a few passes on the metered API quota, without a token). Change detection starts once the baseline is set.
archived per epoch since taonets started tracking (epoch 26,325)
| Epoch | Block | Time | Winner uid | Winner coldkey | Race score | Top incentive | Qualifier mean incentive | Qualifiers |
|---|---|---|---|---|---|---|---|---|
| Nov 11 | ||||||||
| 26,348 | 9,485,196 | Nov 11, 19:42 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,347 | 9,484,897 | Nov 11, 18:42 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,346 | 9,484,457 | Nov 11, 17:14 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,345 | 9,484,178 | Nov 11, 16:18 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,344 | 9,483,865 | Nov 11, 15:15 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,343 | 9,483,395 | Nov 11, 13:41 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,342 | 9,483,106 | Nov 11, 12:43 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,341 | 9,482,663 | Nov 11, 11:15 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,340 | 9,482,358 | Nov 11, 10:14 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,339 | 9,482,052 | Nov 11, 09:12 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,338 | 9,481,605 | Nov 11, 07:43 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,337 | 9,481,301 | Nov 11, 06:42 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,336 | 9,480,848 | Nov 11, 05:12 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,335 | 9,480,555 | Nov 11, 04:13 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,334 | 9,480,282 | Nov 11, 03:19 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,333 | 9,479,809 | Nov 11, 01:44 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,332 | 9,479,495 | Nov 11, 00:41 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| Nov 10 | ||||||||
| 26,331 | 9,479,202 | Nov 10, 23:43 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,330 | 9,478,970 | Nov 10, 22:56 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,329 | 9,478,498 | Nov 10, 21:22 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,328 | 9,478,179 | Nov 10, 20:18 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,327 | 9,477,709 | Nov 10, 18:44 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,326 | 9,477,271 | Nov 10, 17:17 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
| 26,325 | 9,477,020 | Nov 10, 16:26 | #0 | 5DhtXP8…2JrLd | — | 1.000 | 1.000 | 1 |
The chain does not store past Incentive vectors — history begins when taonets started watching (last 24 epochs kept), and every epoch is archived from live reads only. Gap rows mark stretches the worker never saw — they are downtime, not data. Winner coldkeys read at archival are exact; ones marked current were resolved later from the present ownership map. Race scores are the mission's own published scores for the settled round covering each epoch — retrospective (unknown until the round closed), in the mission's own units, never incentive.
who held the top incentive each day — 90 days back to 2026-08-13
| Day (UTC) | Winner uid | Winner coldkey | Top incentive | Block |
|---|---|---|---|---|
| 2026-11-10 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,472,101 |
| 2026-11-09 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,469,724 |
| 2026-11-08 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,462,545 |
| 2026-11-07 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,455,367 |
| 2026-11-06 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,448,180 |
| 2026-11-05 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,440,996 |
| 2026-11-04 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,433,815 |
| 2026-11-03 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,426,636 |
| 2026-11-02 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,419,457 |
| 2026-11-01 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,412,271 |
| 2026-10-31 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,405,090 |
| 2026-10-30 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,397,916 |
| 2026-10-29 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,390,731 |
| 2026-10-28 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,383,546 |
| 2026-10-27 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,376,366 |
| 2026-10-26 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,369,181 |
| 2026-10-25 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,361,996 |
| 2026-10-24 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,354,815 |
| 2026-10-23 | #0 | 5DhtXP8…2JrLd | 1.000 | 9,347,628 |
| 2026-10-22 | #0 | 5GndoVh…CaXTP | 1.000 | 9,340,455 |
| 2026-10-21 | #0 | 5GndoVh…CaXTP | 1.000 | 9,333,755 |
| 2026-10-20 | #0 | 5GndoVh…CaXTP | 1.000 | 9,326,102 |
| 2026-10-19 | #0 | 5GndoVh…CaXTP | 1.000 | 9,318,923 |
| 2026-10-18 | #0 | 5GndoVh…CaXTP | 1.000 | 9,311,745 |
| 2026-10-17 | #0 | 5GndoVh…CaXTP | 1.000 | 9,304,561 |
| 2026-10-16 | #0 | 5GndoVh…CaXTP | 1.000 | 9,297,386 |
| 2026-10-15 | #0 | 5GndoVh…CaXTP | 1.000 | 9,290,205 |
| 2026-10-14 | #0 | 5GndoVh…CaXTP | 1.000 | 9,283,036 |
| 2026-10-13 | #0 | 5GndoVh…CaXTP | 1.000 | 9,275,855 |
| 2026-10-12 | #0 | 5GndoVh…CaXTP | 1.000 | 9,268,675 |
| 2026-10-11 | #0 | 5GndoVh…CaXTP | 1.000 | 9,261,495 |
| 2026-10-10 | #0 | 5GndoVh…CaXTP | 1.000 | 9,254,316 |
| 2026-10-09 | #0 | 5GndoVh…CaXTP | 1.000 | 9,247,134 |
| 2026-10-08 | #0 | 5GndoVh…CaXTP | 1.000 | 9,239,960 |
| 2026-10-07 | #0 | 5GndoVh…CaXTP | 1.000 | 9,232,970 |
| 2026-10-06 | #0 | 5GndoVh…CaXTP | 1.000 | 9,225,790 |
| 2026-10-05 | #0 | 5GndoVh…CaXTP | 1.000 | 9,218,611 |
| 2026-10-04 | #0 | 5GndoVh…CaXTP | 1.000 | 9,211,426 |
| 2026-10-03 | #0 | 5GndoVh…CaXTP | 1.000 | 9,204,245 |
| 2026-10-02 | #0 | 5GndoVh…CaXTP | 1.000 | 9,197,070 |
| 2026-10-01 | #0 | 5GndoVh…CaXTP | 1.000 | 9,189,891 |
| 2026-09-30 | #0 | 5GndoVh…CaXTP | 1.000 | 9,182,712 |
| 2026-09-29 | #0 | 5GndoVh…CaXTP | 1.000 | 9,175,530 |
| 2026-09-28 | #0 | 5GndoVh…CaXTP | 1.000 | 9,168,351 |
| 2026-09-27 | #0 | 5GndoVh…CaXTP | 1.000 | 9,161,167 |
| 2026-09-26 | #0 | 5GndoVh…CaXTP | 1.000 | 9,153,980 |
| 2026-09-25 | #0 | 5GndoVh…CaXTP | 1.000 | 9,146,814 |
| 2026-09-24 | #0 | 5GndoVh…CaXTP | 1.000 | 9,139,631 |
| 2026-09-23 | #0 | 5GndoVh…CaXTP | 1.000 | 9,132,450 |
| 2026-09-22 | #0 | 5GndoVh…CaXTP | 1.000 | 9,125,281 |
| 2026-09-21 | #0 | 5GndoVh…CaXTP | 1.000 | 9,118,102 |
| 2026-09-20 | #0 | 5GndoVh…CaXTP | 1.000 | 9,110,926 |
| 2026-09-19 | #0 | 5GndoVh…CaXTP | 1.000 | 9,103,750 |
| 2026-09-18 | #0 | 5GndoVh…CaXTP | 1.000 | 9,096,572 |
| 2026-09-17 | #0 | 5GndoVh…CaXTP | 1.000 | 9,089,396 |
| 2026-09-16 | #0 | 5GndoVh…CaXTP | 1.000 | 9,082,410 |
| 2026-09-15 | #0 | 5GndoVh…CaXTP | 1.000 | 9,075,231 |
| 2026-09-14 | #0 | 5GndoVh…CaXTP | 1.000 | 9,068,052 |
| 2026-09-13 | #0 | 5GndoVh…CaXTP | 1.000 | 9,060,865 |
| 2026-09-12 | #0 | 5GndoVh…CaXTP | 1.000 | 9,053,680 |
| 2026-09-11 | #0 | 5GndoVh…CaXTP | 1.000 | 9,046,501 |
| 2026-09-10 | #0 | 5GndoVh…CaXTP | 1.000 | 9,039,320 |
| 2026-09-09 | #0 | 5GndoVh…CaXTP | 1.000 | 9,032,136 |
| 2026-09-08 | #0 | 5GndoVh…CaXTP | 1.000 | 9,024,952 |
| 2026-09-07 | #0 | 5GndoVh…CaXTP | 1.000 | 9,017,767 |
| 2026-09-06 | #0 | 5GndoVh…CaXTP | 1.000 | 9,010,580 |
| 2026-09-05 | #0 | 5GndoVh…CaXTP | 1.000 | 9,003,400 |
| 2026-09-04 | #0 | 5GndoVh…CaXTP | 1.000 | 8,996,362 |
| 2026-09-03 | #0 | 5GndoVh…CaXTP | 1.000 | 8,989,181 |
| 2026-09-02 | #0 | 5GndoVh…CaXTP | 1.000 | 8,981,995 |
| 2026-09-01 | #0 | 5GndoVh…CaXTP | 1.000 | 8,974,851 |
| 2026-08-31 | #0 | 5GndoVh…CaXTP | 1.000 | 8,967,666 |
| 2026-08-30 | #0 | 5GndoVh…CaXTP | 1.000 | 8,960,480 |
| 2026-08-29 | #0 | 5GndoVh…CaXTP | 1.000 | 8,953,296 |
| 2026-08-28 | #0 | 5GndoVh…CaXTP | 1.000 | 8,946,111 |
| 2026-08-27 | #0 | 5GndoVh…CaXTP | 1.000 | 8,938,946 |
| 2026-08-26 | #0 | 5GndoVh…CaXTP | 1.000 | 8,931,761 |
| 2026-08-25 | #0 | 5GndoVh…CaXTP | 1.000 | 8,924,580 |
| 2026-08-24 | #0 | 5GndoVh…CaXTP | 1.000 | 8,917,396 |
| 2026-08-23 | #0 | 5GndoVh…CaXTP | 1.000 | 8,910,209 |
| 2026-08-22 | #0 | 5GndoVh…CaXTP | 1.000 | 8,903,029 |
| 2026-08-21 | #0 | 5GndoVh…CaXTP | 1.000 | 8,895,849 |
| 2026-08-20 | #0 | 5GndoVh…CaXTP | 1.000 | 8,888,832 |
| 2026-08-19 | #0 | 5GndoVh…CaXTP | 1.000 | 8,881,646 |
| 2026-08-18 | #0 | 5GndoVh…CaXTP | 1.000 | 8,874,465 |
| 2026-08-17 | #0 | 5GndoVh…CaXTP | 1.000 | 8,867,286 |
| 2026-08-16 | #0 | 5GndoVh…CaXTP | 1.000 | 8,852,914 |
| 2026-08-15 | #0 | 5GndoVh…CaXTP | 1.000 | 8,845,726 |
| 2026-08-14 | #0 | 5GndoVh…CaXTP | 1.000 | 8,838,556 |
| 2026-08-13 | #0 | 5GndoVh…CaXTP | 1.000 | 8,831,372 |
Sampled one block per day from archived chain state — the block number is the verifiable anchor, the date is ±drift. Identity (hotkey + coldkey) is read at the sample block, so it names who actually won that day. Days the endpoint had already pruned are absent, never zero-filled.
The Emission map — what the scores converted into, live.
No emissions flow on chain right now — the race pays nothing until that changes.
Zero τ is flowing to this subnet right now (chain reads taoInPerBlock = 0) — the shares above are the score distribution that would convert if flow resumes.
what it costs to race here, live
Best-case frame: every key wins every epoch. Your real edge depends on the model you bring — check the scoreboard and winner history above, and the repo watch before committing.