AI-assisted summary, reviewed by NullTX editors.

According to recent reports, paying a Bittensor subnet with gamma burns its alpha token. Here is how gamma gets minted, how the lower-price rule works and why the credit can never be converted back.Pay a Bittensor subnet for an AI answer with gamma, and your payment vanishes. The alpha token behind it gets burned, the credit gets spent, and nobody can redeem either one.

Using a subnet's service today usually means creating an account, adding funds and collecting an API key, and every additional subnet repeats the routine. Opentensor announced gamma to cut that friction. With gamma, a Bittensor wallet handles both access and payment across any subnet that adopts the standard.The mechanics are laid out in the gamma guide in the subtensor docs. Gamma is a credit a subnet can accept as payment, valued in US dollars. A customer gets it by burning that subnet's alpha token, and each dollar of burned alpha value mints one gamma, so a burn valued at $100 creates 100 gamma.Each balance stays tied to the subnet where it was created. Gamma minted for subnet 51 can't pay for a service on any other subnet. Root switches the system on network-wide, and each subnet owner or lease beneficiary then enables it for their own subnet.

According to recent reports, customers have two ways in. They can pay with TAO, and the protocol buys the subnet’s alpha and burns it in a single transaction. Or they can pay with alpha they already hold on that subnet, and the protocol burns it directly to create gamma.

Setup takes four steps. The customer creates a fresh hotkey that will act as an API key, associates it with their coldkey, looks up the service they want and mints. The docs give the command: btcli gamma mint --netuid 51 --hotkey API_KEY --amount-tao 10 --service-hotkey SERVICE_HOTKEY. The TAO route follows the same pool and flow accounting as stake-burn and creates no stake position. Owners who hold stake can burn it with mint-gamma-with-stake, and --amount-alpha all burns the whole position.

The gamma lands in a deposit. Each deposit belongs to the minting coldkey and is keyed by the API-key hotkey, which signs the customer's requests. A hotkey holds at most one deposit per subnet, and a coldkey holds at most 64 per subnet. The docs warn against reusing a staking hotkey or a coldkey, because requests signed with the key get paid from the deposit.A few guardrails apply. A mint must reach at least 0.1 gamma. By default, the SDK quotes the mint first and fails it if the result lands more than 5% below the quote. The mint also needs a TAO/USD price no older than 300 blocks, about an hour.

Gamma’s valuation rule decides how much credit a burn buys. The protocol values the burned alpha in TAO, then converts that figure to dollars through an on-chain TAO/USD price feed. The TAO value equals alpha multiplied by the lower of two prices, the gamma price and the spot price, which the docs write as alpha × min(gamma price, spot price).

Every subnet keeps a gamma price. When a subnet registers, the price starts at the median alpha price across subnets. After that it moves asymmetrically. If spot falls, the gamma price falls to match at once. If spot rises, the gamma price climbs slowly toward it, closing a small slice of the gap each block, so the gap halves every 600 blocks, roughly two hours. However high spot jumps, the gamma price can at most double every 600 blocks.An example indicates the effect. Say a user burns 100 alpha when spot sits at 0.05 TAO but the gamma price lags at 0.04. The mint uses 0.04, which gives 4 TAO of value, and at $400 per TAO that mints 1,600 gamma. Had the gamma price caught up, the same burn would mint 2,000, so the lag costs the burner 400 gamma. A short-lived pump buys no extra credit. The figures are illustrative, but the rule comes straight from the docs.The TAO/USD feed gets similar damping. A root-controlled oracle supplies the price, and the accepted price falls to a lower feed immediately but rises at most 66 parts per million per block, about 2% an hour. The docs admit the oracle is trusted: its accepted price can climb up to roughly 61% a day until root replaces or removes it.One more detail matters. The docs say alpha is valued at these prices, not at what selling it would return, so a burn that is large relative to the pool is worth more than a sale would be. A substantial burner gets credit for full value instead of a slipped sale price.Once minted, gamma holds its dollar value whether TAO or alpha prices rise or fall. Service providers still set their own prices.

Industry observers note that to use a service, a person or an AI agent signs a request with a hotkey from their Bittensor wallet. The subnet owner, or another authorized account, deducts the required credits from that hotkey's gamma balance before delivering the service. Nothing transfers to anyone. The designated spender calls `spend-gamma` with up to 512 entries per call, each naming a hotkey, an amount and a 32-byte reference, and the spent gamma is destroyed on the spot.The reference doubles as a receipt. By convention it holds the service's own ID for the request being paid, returned with the response, so the customer can match each spend to a specific request. The chain repeats the reference in its events and reads it nowhere else, so an entry sent twice spends twice.Customers keep control throughout. The minting coldkey can set a daily spend cap that refills linearly over 7,200 blocks, about a day, and a cap of zero pauses the deposit. The coldkey can also change the spender, keep separate deposits for different apps and agents, and top up an existing deposit without switching hotkeys. Because the coldkey can pause or redirect at any moment, services spend ahead: they spend what they are about to serve, then serve what was spent. A spender can hand this right to a `GammaSpend` proxy, which can make no other call.Both minting and spending leave public records on-chain, so anyone can audit how much credit a subnet has created and how much customers have used.

The limits are strict. Gamma can't be transferred to another wallet, and it can't be converted back into alpha or TAO. It confers no claim on any party and can't be redeemed. Each subnet chooses whether, and at what prices, it accepts its own gamma.

The docs flag the sharpest risk directly: dissolving or pruning a subnet destroys all of its gamma, and holders receive nothing. A customer who prepaid a large deposit to a subnet that later shuts down loses it. Moving gamma between your own deposits is allowed, and a deposit opened under someone else's hotkey stays yours, since you can pull the gamma back at any time.A coldkey swap adds a few wrinkles. While one is confirmed, the coldkey's gamma calls are refused, though its spenders keep spending. After a subnet owner swaps coldkeys, deposits that name the old one keep it until the owner republishes its service.

Sources indicate that the docs answer the economic question in one sentence: spent gamma pays its spender nothing. The value of the burned alpha accrues to the subnet's alpha holders.

That makes gamma a direct demand mechanism for alpha. Creating gamma always burns the subnet's alpha, which removes those tokens from circulation for good. When customers pay with TAO, the protocol first buys alpha from the subnet's pool, so TAO-funded purchases add buying pressure before the burn. Every dollar of AI usage ties a purchase of service credits to a burn of alpha.

A service operator earns through the alpha it holds and the emissions its subnet receives, not through a payment from customers. The structure rewards subnets that attract real usage, since usage shrinks their alpha supply.Two questions remain open. Customers get dollar-denominated credit, but the burn that funds it follows alpha prices, so heavy usage during a price spike may feel expensive. Holders also carry the dissolution risk, which will push careful buyers toward established subnets. Which services accept gamma, and at what price, will show whether this becomes a real payments layer or a niche tool. The mechanism is clear, and adoption is the unknown.

Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services. Follow us on X @nulltxnews.

It has been revealed that finCEN's November 6 order cuts US financial institutions off from MEXC Global, barring any transmittal of funds to or from the exchange. The order spells out what is banned, what MEXC is accused of, and how the exchange has answered.MEXC notes user assets remain secure. The FinCEN order never suggested otherwise, and the gap between the exchange's reassurance….

ZetaChain's Governance Proposal 2 would halt its L1 around Dec 9, mint ZETA 1:1 on Solana and burn about 55M ZETA in monthly installments. Voting closes Nov 7.Headlines are calling it a 55 million ZETA burn. Read the proposal's own schedule, though, and nothing close to 55 million disappears on the day the chain halts. The figure is real, but it arrives in t….

eZAR opened its rand-pegged token to the public on November 2 with R303 million in circulation. Its reserve yield is the feature that puts the stablecoin label to the test.Most stablecoin launches promise a token that never moves. eZAR's disclosures say its holders can make money or lose it. The rand-pegged token went live to the public on November 2, and it….

Industry observers note that on-chain data shows the attacker behind the $6.3 billion Binance theft depositing about $4 million into three Binance deposit addresses. At the same time, Binance's first post-hack reserve snapshot shows its biggest assets covered with buffers as small as 2.7 ETH and $6 of USDT. Binance's full zero-knowledge proof of those figures is due by Tuesday.Some of t….

One email a week with our new explainers and the news behind them.

More explainers and analysis from NullTX.

→ Read original article