Bittensor Daily News
Latest editionSN11 TrajectoryRL merges a default-on miner-share burn mode
The November 8 merge of PR347 adds BURN_ALL, enabled by default in version 0.7.8, and routes weight ticks through the existing burn helper instead of the seated winner. The intended denominator is 100% of the miner share, not all subnet emissions; the team describes owner and validator shares as unaffected. Setting BURN_ALL=0 restores the normal path. This is verified merged code and a stated direction for validators. Production rollout, the live RecycleOrBurn setting and actual emission withholding were not independently verified. It is not an executed transaction burn or a new five-slot eTAO allocation event.
Around Bittensor
1 more storiesSN127 Zils requires every customer question family to pass before model delivery
PR218, merged November 8 at 03:34 UTC, replaces pooled acceptance with per-question-family accuracy and baseline Brier-improvement gates. A strong decision family can no longer hide a weak one; failed families are named. Migration retains per-decision no-regression, while single-decision and legacy unscored rows preserve prior behavior. Separately, November 7 PR217 updates miner terms for mainnet SN127: only opted-in open-tier training splits go to assigned miners for z3-mini; data and trained adapters must be deleted within seven days and cannot be served or redistributed by miners. Outside admission remains closed pending rehearsal. The reward rubric is unchanged by PR218, and no new customer delivery or miner earnings were verified. Later on November 8, PR219 fixes a separate reward gate: when a fine-tune’s admission blend contains a pruned, ungraded member, scoring can use the best remaining gradable base instead of excluding that fine-tune indefinitely. A rebuilt blend that fails evaluation still blocks it. The merge does not establish deployment or repayment of previously excluded miners.
Quick briefs & watchlist
6 updatesSmaller developments and early plans. Verification labels distinguish confirmed information from developing claims.
SN8 Vanta records four qualifying alpha burns on November 8
Four successful direct burn_alpha calls on November 8 each individually exceed the 100-alpha threshold: 125 alpha at 06:39:00 UTC, 166.666666666 alpha at 09:45:36 UTC, 187.5 alpha at 16:18:24 UTC and 199.847267161 alpha at 17:19:00 UTC. The later executions are finalized blocks 9,462,584 (extrinsic 27, event 266) and 9,462,886 (extrinsic 8, event 180). Each signed request matches its event amount. All four come from a wallet different from Vanta’s registered owner, so they count toward all-wallet subnet burns, not owner-wallet burns. Vanta’s registration 1,477,264 is unchanged. The earlier two events remain in the archive without recounting; purchase, buyback or revenue funding is not inferred.
SN17 404-GEN changes Pod authentication and bounds final-save rendering
November 7–8 source changes replace cached Pod bearer grants with allocation-bound signed-hotkey authentication and fixed round deadlines. The documented SDK is 0.2.19; matching gateway and Pod images are required, and existing grant-dependent Pods need replacement. Follow-ups deduplicate reconnects, separate read-only ownership lookup from lifecycle mutations, and retain the last completed ownership result during a delayed poll while still fencing explicit ownership loss. A November 8 13:03 UTC commit gives final-save rendering batches 150 seconds, retains 30-second previews and returns HTTP504 render_timeout for retry rather than validation rejection. Documentation requires witness client 0.2.19 and renderer client 0.1.5 or compatible later versions. No production artifacts were built or deployed by that commit; code does not prove the separately reported gateway incident has recovered.
SN71 Leadpoet consolidates Arena evidence, routing and restart safeguards
November 7–8 merges tighten listed-parent public-company evidence, preserve sanitized private upstream evidence separately from worker-visible content, and retain blank provider plaintext without awarding thinking credit. Prospective admission can explicitly bind an approved Kimi alternate; older markerless clients retain Sol and the ordinary DeepSeek primary remains unchanged. Incomplete guarded restarts invoke rollback, retries reuse verified evidence, and ampersand company LinkedIn slugs are normalized while encoded namespaces, separators and double-encoding remain rejected. Frozen scoring outcomes are preserved. Live schema, image and gateway release gates remain; no production migration, repaired round, training readiness or customer adoption is independently established. Later November 8 merges preserve older scorers’ company-input grammar, cache hashes and accepted-result replay after the LinkedIn URL expansion. Operators must pair the corrected gateway with its scorer image and keep existing rounds pinned. A separate fix keeps bounded capture warnings visible after chain-library logging setup. Deployment remains unverified. Further November 8 merges add finite, owner-approved recovery after a proven provider rate limit or an expired execution. A recovered provider attempt may receive one separately verified scorer correction on a different runtime. Execution recovery can cross an operational phase only within the same frozen grading floor, preserving accepted work, billing and quota limits. These changes install recovery authority in code; reopening rounds and granting attempts remain separate operator actions. No production recovery or migration is verified.
SN76 Ormas records a 1,283.866996239 alpha owner-multisig burn
At 04:51:36 UTC November 8 (23:51:36 Eastern November 7), finalized block 9,459,150, extrinsic 11, event 190 records 1,283.866996239 alpha burned by the registered-owner multisig. The inner burn_alpha request, event amount, independently encoded call hash, MultisigExecuted Ok and outer success match. Ormas’s registration 9,003,844 is unchanged. This event was already added to the permanent Burns archive and is carried into the morning edition without recounting it. Purchase or revenue funding is not established.
SN81 Reliquary fixes order-audit exposure and drand warm-up
November 8 PR471 values the work a charged failure can actually forfeit within its own settlement period, including the prompt/output price ratio. New generation orders default to a 30-minute hold instead of 72 minutes. Charged-failure and short-completion limits remain, and the existing corpus-validator rule is unchanged. PR470 moves drand initialization before auditing each order to avoid fallback over-auditing. These merged implementation fixes do not independently establish rollout, measured customer savings or the economic guarantees described by the team.
SN112 THOR completes a finalized owner coldkey change
At 21:53:48 UTC November 7, finalized block 9,457,061, extrinsic 12, event 198 records a successful ColdkeySwapped. The owner changes from 5HDswRwsoc9xfzpQRD7PfEGESUmHhdFm9dNH8Y65K59vJEAm to 5FLYvgSLABgFkgK3m1KQJNm1wEHUimp1xRxePsedRG6N2yQC. THOR’s name and registration block 5,633,022 are unchanged, so this is an owner-key change within the same subnet registration. Before/after storage and extrinsic success were independently checked. No sale agreement, buyer identity, price or pilot launch is established by this transaction.
Stars indicate editorial priority, not investment quality. Routine competition updates receive at most three stars. Shizzy videos receive three; substantive non-video Shizzy coverage receives at least four. Scheduled events remain plans.
Sources & coverage notes
Audit trail
Coverage notes
TrajectoryRL merges a default-on miner-share burn mode; Zils tightens customer-model delivery gates. Plus 404-GEN deployment requirements, Leadpoet and Reliquary operator fixes, THOR’s finalized owner change and qualifying Vanta and Ormas burns. Code changes, operational plans and executed transactions are kept distinct.
Coverage: Nov 7, 2026, 3:58 PM – Nov 8, 2026, 4:12 PM ET
Searched
- All128active slots reconciled with finalized owners/identities, full market snapshot and sector classifications.124configured repository rows queried over seven days; access failures retained.
- All46loaded November8subnet briefs opened natively and summarized; required Const/Tensia/owner discovery reviewed against overnight receipts and the preceding edition.
- Finalized eTAO/burn extension9461092–9462213, all128owner holdings at9462213, full daily lifecycle extension and retained prior qualifying burn evidence.
- Both signed-in YouTube Videos and Live inventories checked. Latest public/member/replays unchanged; Carbon cancellation retained.
Public-data gaps
- Grok discovery, top-five discussion and final omission checks are BLOCKED:100% weekly use, $0 extra credits; native reset November 9 at 5:14 PM. No new queries or exhaustive X coverage claimed.
- The seven-day repository sweep reached54HTTP200,40HTTP403,14HTTP429,4HTTP404 and12unconfigured rows. Pagination and selected original-channel/media gaps remain; prior primary-verified monitor evidence supplements this pass.
- Authenticated TaoStats /v1 access is unavailable because no API key is configured. Moments/activity refresh returned HTTP504; no empty-event conclusion is inferred.
- Discord brief summaries are discovery only. Unresolved original-message verification includes gateway/validator incidents, planned competition changes and Lium October metrics. Private security reviews and member allegations are not published as findings. Saved interview media was not completely listened to or transcribed.
Browse all 92 editions
Conference news · September 30, 2026
Exploit Conference Catch Up · Day 1
The teams, the ideas and the practical takeaways from Exploit Summit’s first day in Montreal. From Gamma and phone-based AI to robotics, science and the business of running a subnet.
Conference news · October 1, 2026
Exploit Conference Catch Up · Day 2
Catch up on Exploit Summit’s second day: Carbon’s Pitchtensor win, SN107 Minos’ research app, agent controls, robotics data, inference partnerships and the decisions behind building a subnet business.