Bittensor Daily News
From the archiveRuntime 491 release fixes lock accounting and extends account controls
The official Subtensor repository published runtime 491 on November 16 at 17:16 UTC. The merged change describes a fix for conviction-lock accounting that could double-count locks and incorrectly cross an ownership threshold, including the SN24 incident described in the release material. The migration rebuilds aggregate lock records from canonical locks; it does not change the underlying locks, stake or token balances. The release also exposes existing Gamma emission controls through SDK and command-line workflows. This is tooling for an existing feature, not a new Gamma launch. Protected-account workflows use proxy controls and delayed execution, without an automatic execution scheduler. These changes affect protocol accounting and account operation, making them more consequential than a routine app update. This report verifies the published release and merged implementation. Network activation and a complete finalized-event reconciliation remain separate checks.
Correction · · Added Chutes announcement with verification limits.
Around Bittensor
7 more storiesTaostats announces swaps between Ethereum assets and TAO or subnet alpha
Taostats announced on November 17 at 09:00 UTC that its cross-chain swap interface is live. The team says users can swap USDC or ETH on Ethereum for TAO or subnet alpha, and swap back, within Taostats. The announcement presents a quote-and-sign workflow without a separate exchange account or bridge interface. That describes the user experience; it does not by itself establish that the underlying settlement uses no cross-chain infrastructure or introduces no additional risks. The practical change is another route into and out of Bittensor assets from Ethereum. We verified the official announcement and linked product route, not a completed wallet transaction, trading volume or customer adoption.
Chutes announces Alibaba Cloud collaboration and discounted model access
Chutes announced an Alibaba Cloud collaboration on November 17, offering GLM-5.3, DeepSeek V4.1 Flash and Qwen3.8 Max through its service. The team says existing API keys and credits work, with developers changing the model ID. Its attached promotion dates the offer November 16 to 23 and advertises 35% off GLM-5.3 and DeepSeek V4.1 Flash. The discount is not described as applying to every model. The public Chutes catalog separately lists GLM-5.3 and DeepSeek V4.1 Flash. That establishes visible listings, not an independently tested inference request or proof that these external models are trained or served by SN64 miners. For developers, the announced change is access through their existing Chutes workflow. The relationship and offer remain attributed to Chutes: the limited Alibaba Cloud timeline reviewed did not provide separate confirmation, and commercial terms, usage and revenue were not disclosed in the announcement.
Lium reports $50 million hardware footprint and $2.93 million in 30-day billings
Lium said on November 16 that its hosted hardware footprint had reached about $50 million, including 481 B300 GPUs and more than 25 GPU types. The statement describes hosted capacity, not hardware owned by the subnet or revenue earned. Its public dashboard, timestamped November 17 at 14:36:40 UTC, separately reported $2.93 million billed to renters, 1.21 million GPU-hours and 34,268 rentals over the previous 30 days, with 83% utilization for that period. These are operator-reported measurements, not independently audited profit. The dated capacity announcement and current usage dashboard together provide a clearer operational picture than token price alone. The earlier October 22 figure of 91% rented is not used as a current utilization number, and the historical 481-B300 count should not be confused with a later live inventory snapshot.
SayGM ledger reports third-cycle burn equal to 25.2% of miner emissions
SayGM’s official buyback ledger lists 22,915 alpha burned for its October 16 to November 16 cycle, against 91,045 alpha of miner emissions. On that same-token basis, the reported burn covers 25.2% of the cycle’s miner emissions. The ledger links a successful SN28 burn_alpha extrinsic at block 9,519,875, executed November 16 at 15:17:24 UTC. The displayed call parameter is a maximum-amount request, not an independently decoded actual burn amount. The 22,915-alpha figure remains attributed to the operator ledger pending native-event reconciliation. SayGM describes buying alpha on the market, also receiving some alpha through customer payments, then burning monthly. Its stated goal is full miner-emission coverage. The current ledger basis supersedes the older 19.3% figure circulating in secondary coverage; neither that percentage nor the associated dollar amount is carried into this report as a verified current measurement.
Recall releases secondary validator and fixes miner connection heartbeat
Recall published its first public secondary-validator release on November 16 at 19:26 UTC. It verifies signed weight bundles from the master and submits weights using the operator’s registered hotkey. The release says it needs no GPU, database, open port or Recall API credentials. Verifying a signed bundle should not be confused with independently rescoring the underlying work. A separate miner release on November 17 at 07:14 UTC addresses silently stalled API connections. It introduces HTTP/2 health pings, closes idle connections after 60 seconds and creates a fresh connection following a failed request, without requiring miner configuration changes. These are released operational tools and reliability changes. The release pages establish availability, not the number of operators that have upgraded.
REAX 1.3 appears in the models.dev DecisionModels directory
REAX announced its models.dev listing on November 16 at 11:04 UTC. The provider directory lists REAX 1.3 under DecisionModels, giving developers another place to discover the model and its published interface information. This is a distribution and discoverability update for an existing model, not evidence that REAX 1.3 launched today. The team connects the model to SN92 miner fine-tuning and DecisionModels serving. A directory entry does not establish a partnership, usage milestone or paying-customer count.
It’s AI appoints Oliver Williamson to lead growth and sales
It’s AI announced on November 16 at 18:03 UTC that Oliver Williamson is joining as Head of Growth to lead growth and sales. The same announcement was shared by the team in its SN32 Discord channel. The appointment adds a named commercial leader to the subnet’s AI-detection business. It does not establish new customers, revenue or a change in subnet ownership. References in the announcement to customers of Williamson’s previous employers are not presented as customers of It’s AI.
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
Runtime 491 addresses lock accounting and account controls. Taostats announces Ethereum-to-Bittensor swaps, Lium reports GPU capacity and usage, and SayGM posts its third monthly burn ledger. Also: Recall releases, REAX distribution and an It’s AI growth appointment. Update: Chutes announces an Alibaba Cloud collaboration and temporary model discounts.
Coverage: Nov 16, 2026, 12:08 PM – Nov 17, 2026, 10:35 AM ET
Searched
- Official runtime release and merged implementation; Taostats launch announcement; Lium statement and dashboard; SayGM ledger and linked execution.
- Recall releases, REAX original and provider directory, and It’s AI original announcement.
- AlphaGap feed and bounded TAO Daily, Tao Outsider and 1t1b discovery; signed-in Grok discovery, attention and omission queries.
- Bounded signed-in Discord reviews for SN3, SN24 and SN32.
- Chutes original November 17 announcement and full offer graphic, public model listings, and a bounded Alibaba Cloud timeline check.
Public-data gaps
- Initial edition: remaining outlet, required-account, fund/person, full-roster and Discord coverage is incomplete. Inclusion in the roster is not a claim that every channel was checked.
- eTAO and burns finalized-event review has not been extended beyond retained verified coverage. Runtime semantics and exact burn-event reconciliation remain outstanding.
- Gamma, owner holdings and registration continuity review remain incomplete; last-good data is preserved.
- Market-move investigations and the full chart recheck remain open. No price cause is inferred from a team announcement.
Browse all 102 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.
