NewsCryptoTrajectoryRL v0.7.8 Enables BURN ALL Emission by Default, Burning Bittensor SN11 Miner Pay

TrajectoryRL v0.7.8 Enables BURN ALL Emission by Default, Burning Bittensor SN11 Miner Pay

Author: LiveBitcoinNews·

Key Takeaways

  • •The v0.7.8 release makes BURN ALL the default, and the environment loader treats an unset BURN_ALL variable as enabled, locking the burn-on state with unit tests.
  • •Under the new default, every weight tick writes owner UID 74 at a weight of 1.0 and skips the winner branch, so SN11's burn configuration destroys the miner emission share on-chain.
  • •The burn only registers if validators collectively converge on the new image, because Yuma Consensus ignores a validator's self-weight, and Watchtower is expected to auto-update configured community validators.
  • •Based on the SN53 precedent, the authors report that fully burning the miner share pushes SN11's slice of overall TAO emission toward zero, including pool injection and chain buys, while validator dividends and the owner cut remain unaffected.
  • •Evaluation, scenario scoring, and winner-seating on the platform continue unchanged, and operators retain a single switch, BURN_ALL=0, to restore winner payouts.
TrajectoryRL v0.7.8 Enables BURN ALL Emission by Default, Burning Bittensor SN11 Miner Pay

TrajectoryRL shipped validator version 0.7.8 on November 8, 2026, turning its BURN ALL emission mode on by default in a merged pull request. On Bittensor Subnet 11 (SN11), every weight tick now directs 100% of miner weight to owner UID 74, bypassing the seated fusion-policy winner entirely. Because SN11 is configured to burn recycled miner emission, that miner share is destroyed on-chain rather than paid out.

Bittensor runs task-specific subnets, and the weights validators write on-chain are what determine how TAO, the network's native token, is emitted to miners.

The change landed in the public trajectoryRL repository as release tag v0.7.8, with the same commit bumping the validator version. Operators who want to restore normal winner weights have exactly one switch: setting BURN_ALL=0.

How BURN ALL Rewires Weight Ticks

Under SN11's normal incentive path, validators read the platform's canonical winner and call set_weights; the seated miner then collects the full miner cut. The subnet's incentive mechanism already burned weight to the owner UID when no seat existed. The new BURN_ALL flag extends that burn path to every tempo — the recurring window on which a subnet's weights are written to chain — including tempos where a winner remains seated.

In code, the default is explicit. The burn flag defaults to on, and the environment loader treats an unset BURN_ALL as "1". With the flag active, the weight tick assigns UID 74 a weight of 1.0 and skips the winner branch entirely. Unit tests in the same pull request lock the behavior in place: burn mode writes only owner UID 74, burn mode off writes the winner, and the default stays on.

The maintainers stress that the burn has to be collective. Yuma Consensus — Bittensor's consensus mechanism — ignores a validator's weight on itself, meaning UID 74's own row cannot carry the burn alone. Every validator running the new image must set the same weights for the burn to register. Once the image is published, Watchtower is expected to pull it automatically for community validators configured to auto-update.

Why a Chain Burn Matters for an AI Competition

TrajectoryRL operates as Bittensor Subnet 11. Miners submit fusion policies that route agent work across open-weight models on Engy, and validators score those packs in sandboxes. The product claim for Season 2 is that the seated policy becomes deployable auto-routing. The chain's role in this loop is narrow and economic: it is the weight-and-emission layer that determines whose alpha gets paid.

AI is the contested object here, not the burn itself. Fusion policies decide which models answer, in what order, and under a metered cost cap. Validators continue to evaluate scenarios and can still seat a winner on the platform. What v0.7.8 changes is the payout wire once that seat exists: winning the fusion race no longer, by default, collects the miner emission stream.

Trace a single tempo under the new default. The platform still names a seated winner. The validator daemon still ticks. Instead of writing that winner's UID to chain weights, however, it writes owner UID 74 at 100%. With SN11's recycle-or-burn mode set to Burn, that miner share is destroyed. The pull request also documents a side effect the team says it already observed on SN53 before launch: when the miner share is fully burned, SN11's slice of broader TAO emission falls toward zero, including pool injection and chain buys. Validator dividends and the owner cut, according to the authors, remain unaffected.

What Is Demonstrated, and What Is Not

What the primary source demonstrates is a software default and a stated subnet burn setting. The release, the config flag, the weight-loop branch, and the owner UID constant are all visible in the public tree. Claims such as "validators will converge," "Watchtower will finish the rollout," and any exact figure for the live TAO-share drop should be treated as operational outcomes. Those still depend on who upgrades and what the chain shows once the weights land.

The motive remains project framing. The pull request explains the coordination problem — self-weight masking — and cites the SN53 precedent. It does not by itself prove how long the burn stays on, whether eval-enabled validators keep spending on sandboxes while miner pay is dark, or when BURN_ALL=0 might return. Those are follow-on facts.

For readers tracking the intersection of AI and blockchain, the notable point is the split between ranking and reward. A subnet can keep scoring agent policies while its miner emission path points at a burn sink. Competition, evaluation, and product seating can continue as before; payment to the seated fusion winner cannot, under this default, until operators turn the flag off or the fleet diverges. The experiment sits alongside other decentralized-AI projects rewriting what a stake or a client is for, such as 0G's path from staked assets into AI compute credits.

The mental model is simple. TrajectoryRL BURN ALL emission is not a new scoring rule. It is a default weight policy that redirects the miner cut to owner UID 74 so the chain burns it. What to watch next: whether community validators actually converge on v0.7.8, whether SN11's TAO share compresses as claimed, and whether the seated Engy auto policy remains worth defending when the miner paycheck is intentionally empty.

Source: Live Bitcoin News