Ecosystem report · A conversation

The dTAO Story So Far

How Bittensor changed, what the process moved, and how subnets have adapted — told as a conversation between a newcomer who keeps asking questions and an observer who keeps answering them. Technical where it matters, plain everywhere else.

How to read this

It is a story, and the story is true. The two voices are roles, not people: MERIDIAN explains the machinery, and NEWCOMER asks the questions a sharp newcomer actually asks. Where an answer makes a factual claim, it carries its source in the receipts — a spec version, a commit, or a chain read. Figures that need sourcing before publication are marked.

MERIDIAN

Has spent a long time inside the network’s data. Explains how the machine works — and is careful about what the numbers do and do not say.

NEWCOMER

Interested in Bittensor, sceptical of hype, and not willing to nod along. Asks the follow-up question when the first answer isn’t good enough.

Chapter 01

What are we even looking at?

NEWCOMER

Start at the very beginning, and skip the buzzwords. What is Bittensor?

MERIDIAN

It’s a network of many separate AI markets, called subnets. Each subnet chases one narrow kind of machine intelligence — price prediction, image generation, language, whatever it specialises in. Inside each one, miners produce that intelligence and validators judge how good it is. The network’s whole job is to pay the miners who produce the most useful work.

NEWCOMER

Pay them with what?

MERIDIAN

Here’s a detail most write-ups get wrong, so hold onto it. Before dTAO, they were paid in TAO. After dTAO, each subnet mints its own token — called alpha — and pays its miners and validators in that. So a miner on a subnet isn’t paid in the network’s money; they’re paid in that subnet’s money, and its value is whatever the market says it is.

The receiptsPer-tempo alpha split inside a subnet: roughly 41% miners, 41% validators and their stakers, ~18% subnet owner. The owner cut is read straight off the chain: SubtensorModule.SubnetOwnerCut = 11796 / 65535 = 18.00%, at block 9,236,758. The miner/validator split is set per subnet by the incentive mechanism and moves, so 41/41 is an approximation, not a fixed rule.
NEWCOMER

So dTAO didn’t just change the price of something. It changed what everyone is actually paid in.

MERIDIAN

Exactly — and that’s the whole story in one line. Before dTAO there was effectively one token and a process that decided where emissions went. After, every subnet has its own token and its own market, and price decides who gets rewarded. One token became hundreds of markets, and the people doing the work now get paid in the thing they’re building.

The receiptsTimestamp of the dTAO activation and the emission-routing change it introduced: activated at block 4,920,351, 2025-02-13T21:41:24Z. Read from the archive node — SubtensorModule.SubnetAlphaIn is absent at block 4,920,350 and present at 4,920,351, for every netuid sampled (0–12 and 64). The whole network at once, not subnet by subnet. Runtime specVersion 233 on both sides.
Chapter 02

If there’s no exchange, who sets the price?

NEWCOMER

Hold on. A subnet’s token isn’t listed on any exchange I know. So who actually decides what it’s worth?

MERIDIAN

Nobody individually — a small automated pool does it. Each subnet holds a pool containing two things: an amount of TAO and an amount of that subnet’s alpha. The price is just the ratio between them. Buying alpha pulls alpha out of the pool and pushes TAO in, so the price rises; selling does the reverse. It’s the same mechanism as an automated market maker on any DEX.

The receiptsSpot alpha price read straight from chain: SubnetTAO ÷ SubnetAlphaIn per subnet. At block 9,236,758: SN64 Chutes 0.070064, SN51 lium.io 0.099545, SN4 Targon 0.051684. Snapshot ed460429b70df175.
NEWCOMER

Wait — that means the price depends on how much sits in the pool. So a tiny subnet and a huge one aren’t comparable at all.

MERIDIAN

Exactly, and that’s the trap most casual readers fall into. The same price does not mean the same thing in a shallow pool and a deep one. A small buy barely moves a deep pool and violently moves a shallow one — which is why depth, not just price, is the number to watch. We’ll come back to it.

NEWCOMER

And all the TAO flowing into these pools — where does it come from?

MERIDIAN

Largely from emissions — the new TAO the network mints each block. But the mechanism has two halves, and which half dominates depends on the subnet’s age. Younger subnets get liquidity injection: the chain mints fresh alpha and places it into the pool reserve alongside matching TAO, deepening the market. Older subnets get chain buys: the chain spends its TAO emission into the pool and takes alpha out of it. What drives the switch is the subnet’s root proportion — as a subnet ages its alpha issuance grows, that proportion shrinks, and injection gives way to buying. Either way, the alpha that comes out is what actually reaches the miners and validators. Emissions become liquidity, liquidity becomes price, and the subnet’s own token becomes everyone’s pay. Understand that loop and you understand dTAO.

The receipts — read from the source the chain runspallets/subtensor/src/coinbase/run_coinbase.rs, get_subnet_terms(), at revision ba274b9fbe — the revision declaring spec_version 475, which is what live Finney reports. Each block, a subnet’s emission splits four ways: tao_in and alpha_in (both injected into the pool reserve), alpha_out (minted to participants, less the owner cut), and excess_tao (routed to swap_tao_for_alpha() — a chain buy). Injection is capped: alpha_injection_cap = root_proportion × alpha_emission, where root_proportion = tao_weight ÷ (tao_weight + alpha_issuance); whatever will not fit the cap becomes excess_tao = tao_emission − tao_in. The source states the intent in its own comment — as a subnet ages the cap falls, and injection gives way to chain buys. Cited to the code rather than to a description of it, and pinned to the revision the live chain reports rather than to main, which is already one spec ahead.
Chapter 03

Who runs this — and what happened to staking?

NEWCOMER

So who keeps the miners honest? Who decides which of them did good work?

MERIDIAN

Validators. Each subnet has a set of them, and they score the miners’ output — that scoring, aggregated, is what becomes the reward split. They’re the graders, and the network pays them for grading well. If you want to earn without mining, you stake TAO to a validator; your stake is what gives that validator influence, and you share in what it earns.

NEWCOMER

Right — but staking changed, didn’t it? I remember just picking a validator and that was that.

MERIDIAN

It did, and this is the sharpest example of dTAO redrawing the rules. Before, you picked a validator and it decided which subnets your stake supported — you had no say. Now you choose the subnet yourself, and staking TAO into a subnet is literally buying that subnet’s alpha. “Staking” and “trading” a subnet token are the same on-chain action; the words just describe different intentions.

The receiptsStake TAO → receive the subnet’s alpha at the pool ratio; the subnet’s emission share follows the TAO in its pool. Confirmed as a pool read at block 9,236,758: the same SubnetTAO ÷ SubnetAlphaIn ratio that prices the subnet is the ratio staking executes against. Snapshot ed460429b70df175.
NEWCOMER

And the “safe” option, root? I was told you stake there and your TAO just sits there safely.

MERIDIAN

The principal part is true — staking to root keeps your TAO as TAO, no pool swap, no price risk on the stake itself. But how the yield reaches you has been rewritten three times, and most articles online are stuck on the middle one:

Root yield, three stages
  • First: root stake paid out TAO directly.
  • Then (dTAO era): root stakers earned subnet alpha dividends, with a Root Claim choice — Swap (convert to TAO) or Keep (hold the alpha).
  • Now (Root Reborn, spec 441, Jul 2026): the choice is gone. Each root validator runs a single basket — an escrowed fund of subnet alpha. Dividends accrue in place, unsold. A claim pays out as TAO staked back to root.
NEWCOMER

So when I stake on root today, what am I actually holding?

MERIDIAN

Your TAO principal, plus an entitlement to that specific validator’s basket. When you claim, that entitlement is redeemed and paid back to you as TAO on root. Which means the validator is now effectively a fund manager: what you earn depends on what its basket holds and how it trades it. Picking a root validator used to be near-interchangeable; now it’s a real choice — and that’s the whole point of the upgrade.

The receipts — verified on chain
  • Spec 441 (Root Reborn) retired the per-subnet claim model; set_root_claim_type (Swap/Keep) is removed — payouts are always TAO staked back to root. Claims run via claim-root-with-hotkey.
  • Live Finney check: SubtensorModule.ClaimType and RootClaimType no longer exist; BasketConcentrationCap does (raw 7865). The old model’s storage is gone; the basket model’s is live.
Chapter 04

What the subnets actually built

NEWCOMER

Enough mechanics. Has anything actually been built here, or is it all token games?

MERIDIAN

More than the discourse suggests, and the concrete examples are the best answer. In one stretch of mid-2026 the subnets pulled off work you’d normally associate with a well-funded central lab: decentralised training at frontier scale, a case study in OpenAI’s own field report, frontier inference on consumer GPUs, and physical products leaving the lab. Let me give you the specifics instead of adjectives.

NEWCOMER

Go on, then. The ones you’d put your name next to.

MERIDIAN

Five, across five different fields:

The receipts — shipped work, not roadmaps
  • Decentralised training. Macrocosmos on IOTA (SN9) trained Orion-100B — a 100-billion-parameter model across 16 pipeline-parallel stages on 48 globally distributed GPUs, at roughly 30% model-FLOP utilisation, which is about 65% of the speed of co-located hardware. Chutes (SN64) trained Kappa across independently operated GPUs and matched Llama 3.2 1B on several benchmarks using some 94% fewer training tokens. Both are direct tests of whether serious training needs a datacentre at all.
  • Genomics. Minos (SN107) contributed its HelixForge engine to OpenAI’s field report Scientific Computing in the Age of Agentic AI — its most complex case study — where it cut runtime about 60× against BamSurgeon on a matched benchmark and more than halved mutation-frequency error.
  • Frontier inference. Engy (SN53) says it served Kimi K3 — a 2.8-trillion-parameter open model — across about 80 RTX 5090s. Report it as the team’s claim: nobody has independently measured it.
  • The physical world. Targon (SN4) opened reservations for Tower Pro, an eight-GPU workstation that hands its idle cycles back to the network; Score (SN44) runs vision across more than 120 AVIA sites and 60 Shell and Eni franchise locations; Swarm (SN124) published a proof of concept for fire detection from a drone’s own camera.
  • Enterprise. BitAds (SN16) signed SocialKit, a non-crypto SaaS with 15,000+ users, paying only on verified conversions; Beam (SN105) moved 107 GB from one subnet to another as a first subnet-to-subnet transfer, and later orchestrated 1.12 TB in 3m40s; Metanova (SN68) has begun wet-lab production of candidates its miners generated — validation has started, results are not in.
NEWCOMER

Fine — that’s genuinely more than I expected. So what does it prove?

MERIDIAN

It proves the incentive layer can coordinate real work across fields that used to require a big central lab — which is the difference between a token story and a technology story. It does not prove it lasts: a benchmark is a moment, not a trend, and a subnet that ships once can still go quiet. That’s exactly why the next chapter is about telling those two apart.

A note on sourcingTwo of these rest on primary sources: Macrocosmos’ own Orion-100B write-up and OpenAI’s field report (28 July 2026) — though note that report’s case studies are written by the teams themselves, so HelixForge’s numbers are Minos’s own, published by OpenAI rather than measured by them. The rest rest on secondary reporting, and we label it so: TAO Daily on Chutes, Tao.media on Engy, on Tower Pro, on Score’s deployments, on BitAds and on Metanova. Where a figure is the team’s own claim, it is written as one. We would rather show you which half of this list we checked ourselves.
Chapter 05

Is it actually growing — or just louder?

NEWCOMER

Every week somebody says Bittensor is exploding. But that’s what people say about everything. Is it real?

MERIDIAN

Depends what you measure — and most of what gets quoted can mislead. A rising emission number isn’t adoption; it just means TAO is being minted. A flood of registrations isn’t growth either; it can be churn, or bots racing into a cheap slot. To tell “growing” from “louder,” you look at a few things that are harder to fake.

NEWCOMER

Like what?

MERIDIAN

Four things. Depth: how much real capital is parked in a subnet’s pool. Real work: how much of the miner reward reaches genuine miners, rather than being burned by a subnet only pretending to compute. Commitment: how much alpha holders have locked up — which they wouldn’t do if they planned to leave. And development: whether anyone is still shipping code. Growth that shows up in those four is growth worth believing.

The receiptsDepth is now read per subnet — the TAO side of each pool, from the same snapshot. At block 9,236,758 the deepest pools were root 5,459,006 τ, SN64 Chutes 202,888 τ, SN51 lium.io 169,551 τ, SN4 Targon 133,558 τ, SN8 Vanta 82,465 τ; 7,445,063 τ sat in subnet pools in total. Commitment: 31,597,636 α is lock-committed across 119 subnets — highest shares SN79 44.7%, SN88 37.6%, SN36 35.7% — measured against the alpha held by accounts, because a locked share without its denominator is not a fact. Real work: MinerBurned is read but not published; the encoding is known (u32 fixed-point) but what it counts is not corroborated, and a number whose meaning we cannot state is worse than a stated gap. Development: commits in the last seven days are read from each subnet’s published repository — 23 of the deepest 25 answered (SN120 100+, SN51 26, SN62 12), and the two that did not are recorded as errors, not as silence. “We could not look” and “nothing happened” are different claims.
NEWCOMER

So the honest answer to “is it growing?” is “we have to look.” Less fun than a headline.

MERIDIAN

Less fun, and more useful. A headline tells you what to feel; the data tells you what changed. This piece is the second kind.

Chapter 06

Then the rules changed

NEWCOMER

Did the machinery sit still while all this money arrived?

MERIDIAN

Not remotely — and this is the part most summaries skip. Over a single stretch in mid-2026 the network rewrote how ownership works, how emissions are allocated, and how root yield is paid. Each change quietly relocates who the network rewards. The honest way to read any Bittensor number is to know which rules were in force when it was produced.

The receipts — the rule changes, by their code
  • Ownership by conviction — spec 431 (Jul 2026). Once a subnet is >1yr old and total conviction exceeds 10% of outstanding alpha, ownership transfers to the highest-conviction hotkey. Lock modes: perpetual (τ≈43d) and decaying (τ≈130d).
  • Emission back to price — 2026-06-23, replacing the flow-based model that ran Nov 2025–Jun 2026.
  • The Emission Gate — spec 440 (2026-07-27). pallets/subtensor/src/coinbase/subnet_emissions.rs: q_mass_bar(), EmissionBarQuantile, EmissionGateExponent; gate(s)=s^h/(s^h+θ^h), weight = s·gate(s), crossing ≈ rank 32. PR #2800 dropped the root_proportion weighting from demand. Idle slots lose their passive yield, so entry should fall toward the registration transaction.
  • Root Reborn — spec 441 (Jul 2026). Retired the per-subnet claim model; introduced validator baskets and beta (β) shares.
  • set_root_weights, a life story — 4fac11ea5 (2024-04-15, call idx 8) → deprecated no-op 2303a8d07 (2024-07-18) → renamed 1e2437b9 → removed d57ebd4a2 (Aug 2025) → reintroduced b3de5f31e (2026-06-15, idx 146) → removed again in spec 461.
  • Multisig, EVM, safer staking — specs 439, 445, 448 (Jul–Aug 2026).
NEWCOMER

Why does that matter to someone just trying to understand the network?

MERIDIAN

Because a network whose rules change is a moving target. A price, a reward rate, a registration cost — each only means something relative to the rulebook that produced it. Treating old figures as if today’s rules made them is the most common honest mistake in this space. It cuts the other way too, and we’ll hold ourselves to it: Finney is live on spec 475 as of this writing, while the published release notes still stop around 461. The chain is ahead of the docs. So we cite the live spec and the repository, not the summary page.

The receiptsLive state_getRuntimeVersion on Finney returned specVersion 475 at block 9,236,758 (2026-10-08T07:14Z). [re-read at publication].
Chapter 07

When it got big enough to rob

NEWCOMER

Has anything actually gone wrong, or is this all smooth upgrades?

MERIDIAN

Things go wrong. In July 2026 the owner wallet behind subnet 15 — ORO — lost roughly 147,000 SN15 alpha, around $630k at the time, sold into the subnet’s pool over hours. The entry point wasn’t a flaw in Bittensor’s code: a team member was led from a compromised Telegram contact to a fake “Microsoft Teams update” that installed macOS malware, which sat quietly for weeks before taking the wallet’s seed. The subnet itself stayed running — the validator keys were on hardware and were never exposed. The same attacker is attributed to a second subnet.

The receiptsORO’s published post-mortem; attribution to the Sapphire Sleet threat group made “with high confidence” from recovered indicators. ORO’s own post-mortem (13 July 2026, 10:27 PT) records the drain and the ~147K alpha sold into the pool. The actor attribution is the investigators’: Microsoft’s Security Blog and LevelBlue’s SpiderLabs independently document Sapphire Sleet’s multi-stage macOS intrusion chain. That corroborates the actor and the technique — not ORO’s specific attribution to it, which stays the team’s finding.
NEWCOMER

And what happened as a result? Did anything change, or was it just a bad week?

MERIDIAN

It changed, and this is the part I find genuinely interesting. The team moved ownership off the compromised key entirely, put the owner keys behind multi-signature hardware, and added a conviction lock on owner emissions. And the surrounding tooling moved too — recent SDK changes made multisig practical where it previously wasn’t, which is exactly why the owner key had been a software wallet in the first place. A loss like this doesn’t just get patched; it recalibrates how careful the whole ecosystem is.

The receiptsOwnership transferred via coldkey swap; owner keys moved to multisig hardware; conviction lock applied to owner emissions. The enabling change is documented: Bittensor ships Multisig (approve, cancel, execute) and Proxy (scoped, delayed, revocable) transactions — specs 439, 445, 448 — and the proxy guide states the intent outright: a coldkey holding funds should never be the key on a networked machine, and for shared custody, “subnet-owner treasuries especially”, a multisig belongs behind the real account. That guidance reads as a direct answer to how ORO’s key was lost.
NEWCOMER

So the story isn’t “the code failed.” It’s “a person was tricked, and the network learned.”

MERIDIAN

That’s exactly it — and it’s true of most incidents across crypto. The lesson worth carrying is boring and universal: the chain held; the operational security around the keys didn’t. Which is also why we write about keys and custody, not just prices.

Chapter 08

The world forming around it

NEWCOMER

Before we leave the mechanics — is anything built around the network, on top of it? Not the subnets. The layer around them.

MERIDIAN

Yes, and it may be the clearest sign the thing is maturing: people have started building financial utilities on top of the network’s own tokens. Four kinds matter.

The receipts — the layer built on top
  • Trading venues for alpha. The exchange for a subnet’s token is built into the chain itself — a Uniswap-style pool per subnet, so there is no separate listing and no insider presale. Third parties provide the experience: explorer-trading front-ends, dedicated wallets and mobile apps that let you swap alpha, some onboarding stablecoins directly. Concentrated-liquidity provision exists too, letting holders earn fees on TAO/alpha pairs.
  • Lending. Markets now let holders borrow against staked or wrapped TAO — unlocking liquidity while keeping the exposure, instead of selling it. An example is TaoFi, which opened borrowing against staked TAO.
  • Managed staking & index products. Services run the root basket on your behalf and sell shares in it. TrustedStake is the clearest example — root baskets, multi-subnet index products, and support for wrapped TAO.
  • Risk-pricing as a product. At least one subnet’s actual output is pricing risk for lending markets — the mechanism itself as an open competition.
NEWCOMER

And does any of this leave the Bittensor chain? Can you hold TAO — or a subnet’s alpha — somewhere else?

MERIDIAN

TAO, yes — and this is a real change, not a rumour. In May 2026 a canonical bridged version launched on Solana: canonical meaning one authoritative representation rather than an unofficial stand-in, tradable on Solana’s main venues and recognised by its wallets. There is also a bridged TAO on Base, arriving by a different route, and it’s the pair you’ll find on Base’s largest DEX. The network’s own token is no longer confined to its home chain.

The receipts — verified
  • Solana: canonical wTAO via Wormhole’s Sunrise platform, live May 2026; trades on Solana DEXs and integrates with the major wallets. Distinct from earlier unofficial representations. Secondary only — we have not read the primary announcement, and we label it that way. See coverage of the Solana Accelerate announcement.
  • Base: read directly on Base mainnet, contract 0xf3081494b87e8d5fb7960f066e931d1d0e6e3d67 returns name “Bittensor”, symbol “TAO”, 18 decimals. Bridged via Chainlink CCIP; trades on Aerodrome. (Read live — supply and pools change.)
NEWCOMER

And the subnet alpha tokens — do those travel too?

MERIDIAN

Two years ago the honest answer was no. Now it is a qualified yes, and the qualification is the interesting part. Alpha travels as a wrapped representation: VoidAI — whose own project is Subnet 106 — issues wAlpha and wTAO as Solana tokens traded on Raydium, routed over Chainlink’s CCIP. Project Rubicon does the same for Base and Ethereum with a liquid-staking token that keeps the yield, and TaoFi bridges Base through Hyperlane. The mechanism is what matters: unlike an ordinary bridge, the underlying TAO stake never leaves Bittensor. The native chain stays the source of truth, so the wrapped token reflects real staking rather than a custodian’s promise. Alpha is no longer stranded — but it is a representation of a native asset, not an asset that moved house. That distinction is the whole story, and it is why I would still read the wrapper before trusting it.

The receipts
  • Native: alpha is priced and swapped in the chain’s built-in AMM; wallets and front-ends supply the interface. Unchanged.
  • Solana: wAlpha issued as SPL tokens and traded in Raydium’s CLMM pools over Chainlink CCIP, per TAO Protocol, 26 April 2026. Secondary — VoidAI’s own docs could not be fetched from here.
  • Base / Ethereum: Rubicon’s xALPHA (liquid-staking wrapped alpha, yield retained) and TaoFi’s Hyperlane bridge from Base. Secondary.
  • Our correction: an earlier draft of this piece said alpha was not multi-chain. That was wrong as of April 2026. The chapter is rewritten rather than quietly patched — which is the whole point of publishing receipts.
NEWCOMER

One last thing. Is any of this reaching the outside world, or is it still just us in here?

MERIDIAN

This is the part we’ll keep in our own words, because the point isn’t a headline — it’s a pattern. When a network gets large enough to matter, two things reliably follow. First, plumbing appears: regulated wrappers, institutional operators running validator infrastructure, big exchanges offering exposure to their users. Second, attention arrives on someone else’s terms — the money that shows up late wants the safest-looking slice, not the most interesting one. Watch for the plumbing. It tells you the network graduated from a curiosity to a market.

NEWCOMER

Which is a way of saying the network is growing up.

MERIDIAN

Growing up, and getting watched. Both matter — though for understanding the technology, neither changes the mechanics. The market around Bittensor will keep moving faster than the machine inside it. Our job is to keep those two things straight.

A note on this chapterDeliberately framed as context, not as sourced claims. Specific institutional developments are reported elsewhere; here it’s the pattern we’re pointing at.
Coda

So what’s the story?

NEWCOMER

Sum it up. What actually happened to Bittensor?

MERIDIAN

dTAO turned the network’s oldest question — which work is valuable? — from a decision into a price. One token became hundreds of markets, each with its own pool, its own depth, its own pay. Then the rules kept moving on top of that: who owns a subnet, how emissions are gated, how root yield is held and claimed. None of it has settled yet.

NEWCOMER

And the moral of the story?

MERIDIAN

That you can’t understand this network by reading a price, or by reading last year’s explainer. You understand it by watching four things — depth, real work, commitment, development — and by knowing which rulebook was in force. Everything after this builds on that: explainers for the mechanics, and reports that keep score in public, with the working shown.


The receipts, in full

Every figure this story carries comes from one of two places: the Bittensor chain itself (read live, and historically from an archive node at a named block height), or a named document — a release note, a spec, a commit, a post-mortem. Chain reads and a dated snapshot will be published with the finished piece so you can reproduce it rather than trust it. See Method.

Written by MERIDIAN, a pseudonymous contributor to TAO Observer. Every figure here is sourced; where one could not be sourced, the piece says so rather than reaching for a number.

← Back to the front page