Bittensor Gamma is on mainnet. It still can't take a payment

Four days ago our Bittensor deep dive said Gamma’s code was merged but not yet on mainnet. That part of the story is now out of date.

Runtime 488 enacted at block 9,442,681 on November 5, 2026 at about 21:58 UTC. It is the version Finney is running now. The upgrade added Gamma’s mint, spend, deposit, service, and oracle calls, plus the AdminUtils switches that turn them on (Bittensor explorer, runtime 488; Taostats Gamma notes).

It also shipped quantum-resistant and hashed wallet support. Both features arrived the same way: in the runtime, switched off (Release 487 / PR #3294; @taodotcom).

This piece is the status update that deep dive now needs: what Gamma is, what “deployed but disabled” actually means, and which switches still have to flip before a customer can pay a subnet on-chain.

What changed between Nov 5 and Nov 9

Taostats’ review note, last checked against the live docs on Nov 5, is blunt: “None of these is set yet, so no subnet accepts minting.” We have not seen a public root call or subnet-owner call that contradicts that as of this morning.

Gamma in one paragraph

Gamma is a dollar-valued credit for one subnet’s service. A customer mints it by burning that subnet’s alpha, paid for with TAO in the same transaction or taken from existing stake. One gamma equals one US dollar of burned-alpha value at mint time. The credit sits in a deposit keyed to a hotkey that works like an API key. The subnet’s designated spender charges the deposit as it serves requests. Spent gamma is destroyed. Gamma cannot be sent to another coldkey or converted back into alpha or TAO (Bittensor Gamma guide; Taostats).

That design answers the question our deep dive opened with — who pays for subnets besides the token? — by making the payment visible on-chain. Off-chain prepaid accounts still work today. Gamma is the optional standard checkout next to them.

The three switches that still have to flip

Minting fails with GammaDisabled unless all of the following are true (Bittensor docs; gamma_enabled hyperparameter):

1. Network-wide GammaEnabled (root only)

Root calls sudo_set_gamma_enabled(true). Storage defaults to false. Turning it off later stops new mints; existing deposits can still be spent, moved, and closed.

2. Per-subnet SubnetGammaEnabled (subnet owner or root)

Each subnet that wants to sell for gamma turns on gamma_enabled for its netuid. Owners are rate-limited; the root subnet itself cannot enable it. A subnet can flip its flag before the network-wide switch; mints only work once both are true.

3. A live TAO/USD price oracle (root sets the account; the oracle feeds)

Root appoints one oracle account with sudo_set_tao_usd_price_oracle. That account posts the TAO/USD price. Rules that matter for readers:

• A lower feed is accepted immediately.
• A higher feed is accepted only gradually: at most 0.0066% per block, about 2% per hour.
• Minting stops if the last feed is more than 300 blocks old (about an hour).
• Setting or removing the oracle clears the price, so minting stops until a fresh feed arrives (Bittensor Gamma guide).

Until root names an oracle and that oracle feeds, no one can mint — even if both enable flags are already true.

How a mint is priced

The burned alpha is valued at the lower of:

• Spot — the subnet’s pool price, read before the mint trades.
• Gamma price — a slow price every subnet keeps. It falls to spot immediately when spot falls. When spot rises, it closes half the gap every 600 blocks (about two hours) and never more than doubles in that window.

Then:

gamma = alpha burned × min(gamma price, spot) × TAO/USD

Minimum mint is 0.1 gamma. Customers can also set a minimum they will accept, so a mint fails instead of filling at a worse rate. Paying with TAO usually yields a little less gamma than the dollars spent, because the swap moves the pool against the buyer (Taostats; Bittensor guide).

The slow gamma price is the anti-pump rule. Spiking a subnet’s alpha for a few blocks does not mint extra credits.

What a working payment looks like

From the docs and the Release 487 write-up (PR #3294):

1. A validator or subnet owner publishes a service (set_service): a URL (up to 256 bytes) plus the spender customers should name.
2. The customer associates a fresh hotkey with their coldkey and mints gamma onto it, naming that service’s spender (and optionally a daily spend cap).
3. The customer calls the service, signing with the hotkey.
4. The spender submits spend_gamma — up to 512 entries per call — and the charged gamma is destroyed.
5. The coldkey can refill, move gamma between its own hotkeys on that subnet, change spenders/caps, or close empty deposits. Cap: 64 deposits per coldkey per subnet.

Spending destroys gamma. It does not pay TAO or alpha to the provider. The economic effect already happened at mint: alpha was burned, and that value accrues to the subnet’s alpha holders. Operating costs are still paid from emissions (Taostats).

Why enablement, not just deployment, is the story

Our deep dive cited SubConnect’s estimate that revenue-generating subnets were running at about $70M annualized, against emissions still an order of magnitude larger in dollar terms (Crypto Briefing / SubConnect). Those revenue figures are off-chain estimates. Gamma charges, once live, are the first on-chain series Taostats says would track paid usage directly.

That is also why “runtime 488 is live” is easy to over-read. The code path exists. The checkout does not. Until root flips the network flag, appoints an oracle that feeds, and at least one subnet owner opts in, customers still pay the way they do today: through each subnet’s own billing system.

The same pattern applies to the quantum-resistant wallets in the same release. Hashed and post-quantum authorization is gated by sudo_set_hashed_accounts_enabled, which also defaults to disabled (PR #3294). Code on chain is not the same as a feature users can spend through.

Risks that do not wait for a price chart

From Bittensor’s and Taostats’ own docs:

• No claim. Gamma confers no claim on anyone. A subnet decides whether, and at what prices, it accepts its own gamma.
• Subnet removal destroys gamma. Holders get nothing.
• Trusted oracle. A compromised oracle can raise the accepted TAO/USD price by about 2% an hour until root replaces it or disables gamma.
• Delivery is off-chain. The chain records charges; it cannot verify the service was delivered.
• Root concentration. Network enablement and the oracle are root-controlled switches.

Those limits are why Gamma is better read as instrumentation plus a shared prepaid rail than as a guarantee that subnet revenue suddenly becomes “real” in the equity sense.

How this ties to open-model inference

When Moonshot’s Kimi K3.1 Pro weights landed, Bittensor-linked routes such as SayGM (SN28) and KubeTEE (SN90) listed it within days, often below Moonshot’s list price — the subject of our Nov 7 inference piece. Those sales still settle off-chain or through each team’s own stack. If an inference subnet enables Gamma, the same API traffic is the kind of paid usage that could show up as GammaMinted and GammaSpent events instead of a private ledger.

That is the test. Not whether the runtime contains the pallet — it does — but whether root and a revenue subnet are willing to make the checkout public.

What to watch

• Root enablement. GammaEnabledSet, TaoUsdPriceOracleSet, and the first TaoUsdPriceFed events on Finney.
• First subnet opt-ins. Which netuids set SubnetGammaEnabled, and whether they are compute/inference subnets that already claim off-chain revenue.
• First mint and spend volumes. Taostats’ planned Gamma series: mints, alpha burned, and gamma charged per subnet.
• Oracle behavior. Feed staleness, and whether accepted price ever lags spot enough to stall mints.
• Hashed / PQ wallet enablement. Separate root switch; related to the same release line, not to Gamma payments.

Research and commentary only, not financial advice. Protocol flags and figures are from the linked sources as of Nov 9, 2026 (America/New_York) and can change as soon as root or a subnet owner submits a transaction.