Bittensor Toolkit →Find the right tool for your question.

Bittensor Daily News

From the archive
#01 · SN3 · Teutonicverified
★★★★★

SN3 Teutonic: Const reports owner-key compromise after stake transfer and sale

Const said in Bittensor’s SN3 Discord channel on November 11 that a key appeared compromised and estimated the loss at about 2,000 TAO. He said he had not sold the stake and that the cause was still unknown. He described the affected key as one obtained during the project takeover, for which he had not completed his usual protective setup. Independent finalized-chain checks confirm a successful transfer of 101,141 alpha from the SN3 owner address at 15:18:48 UTC, followed by a successful unstake from the receiving address at 15:26:36 UTC. The latter event records 2,068.012572293 TAO removed and 101,090.070679789 alpha. These transactions corroborate the movements, not who controlled the key or the method of compromise. Const’s statement that he would swap the key is a plan, not verified recovery. No Bittensor protocol breach or connection to lium’s selloff has been established.

Why 4 stars: An owner-key compromise reported by the affected principal, with independently corroborated stake movements, is material security news. The cause and attribution remain unresolved.

#02 · SN51 · lium.ioverified
★★★★★

SN51 lium falls 9.45%; Mentat reports liquidation of a 160.42 TAO debt

At the 17:12:48 UTC November 11 market snapshot, lium traded at 0.110548272 TAO per alpha, down 9.45% from 0.122082812 TAO at 17:12:36 UTC the previous day. The snapshot records 25,896.45 TAO of 24-hour trading volume and 182,491.49 TAO in pool reserves. These are alpha-versus-TAO figures, not dollar returns. Mentat reported that a 9.2% price decline pushed a position past its 60% loan-to-value liquidation threshold. Its account says 160.42 TAO of debt was repaid, 1,597.50 alpha was seized including the penalty, and 824.25 alpha remained. The attached receipt identifies block 9481779; the underlying contract transaction has not been independently reproduced. This establishes a platform-reported lending consequence alongside the measured market move. Wallet identities, a connection to SN3’s incident, and a single cause for the broader decline are not established.

Why 4 stars: A substantial move in a major subnet with a concrete reported lending consequence merits prominent coverage. Price alone does not establish causation or mechanically raise a rating.

#03 · Ecosystemverified
★★★★★

Gamma records mint-and-spend transactions as six more subnets opt in

The finalized interval from block 9476686 through 9484458 contains successful Gamma opt-ins for SN103, SN53, SN81, SN80, SN25 and SN117. It also contains two GammaMinted events, one each on SN103 and SN53, and six GammaSpent events: one on SN103 and five on SN53. This advances the evidence beyond the configuration-only picture in the previous edition. These are verified protocol transactions. They do not independently establish an outside paying customer, delivered service, recurring revenue or adoption at scale. SN58’s earlier activation and announced robotics-data offering remain dated November 10 developments, not new launches today. Engy separately announced on November 11 at 16:50 UTC that engy.ai accepts Gamma. That is a team availability statement alongside the independently observed SN53 transactions.

Why 4 stars: Verified use of the new payment mechanism across additional subnets is a consequential implementation follow-up. Small transaction counts are not evidence of commercial scale.

#04 · SN64 · Chutesverified
★★★★★

SN64 Chutes previews Parallax throughput on a single RTX 5090

Chutes reported almost 18,000 tokens per second with 256 concurrent requests on one RTX 5090 on November 11. Its attached image identifies Parallax 8B on an unoptimised vLLM fork and explicitly calls the result a preview, not a formal benchmark. The team attributes the design to a small model, four-bit expert math and a fixed-size cache for most attention. The result has not been reproduced here; it should not be treated as a measured service-wide speedup or cost saving across arbitrary models and workloads.

Why 3 stars: A substantive technical preview with explicit benchmark limitations; independent reproduction and production impact remain unverified.

#05 · SN59 · Unknownverified
★★★★★

SN59 changes its owner, validator and miner allocations

At 10:20 a.m. Eastern on November 10, a successful finalized transaction changed the burn / recycle / owner / validator / miner allocation from 0.00% / 0.00% / 31.97% / 35.03% / 33.00% to 0.00% / 0.00% / 33.00% / 31.99% / 35.01%. The project identity, registration and owner address were unchanged across the event. This redirects future emissions; it is not a transaction burn. Root’s baseline is paid from and capped by the validator bucket, while historical yield estimates can lag the new settings.

Why 3 stars: A meaningful change in participant economics, without implying a product launch or guaranteed future yield.

#06 · SN31 · rec4llverified
★★★★★

SN31 rec4ll changes its owner, validator and miner allocations

At 8:31 a.m. Eastern on November 11, a successful finalized transaction changed the burn / recycle / owner / validator / miner allocation from 0.00% / 0.00% / 25.00% / 20.00% / 55.00% to 0.00% / 0.00% / 18.00% / 41.00% / 41.00%. The project identity, registration and owner address were unchanged across the event. This redirects future emissions; it is not a transaction burn. Root’s baseline is paid from and capped by the validator bucket, while historical yield estimates can lag the new settings.

Why 3 stars: A meaningful change in participant economics, without implying a product launch or guaranteed future yield.

#07 · SN8 · Vantaverified
★★★★★

SN8 Vanta records five qualifying alpha burns

Five successful finalized events in the reviewed interval burned 135.301437364, 136.950043549, 14,720.75, 250 and 250.076946388 Vanta alpha. The largest occurred at block 9479710. Exact calls, amounts and unchanged historical project identity are retained in the evidence. These are transaction burns, not miner-emission withholding, fees or recycling. The transactions do not by themselves identify the source of funding or prove customer revenue. Each event separately meets the archive’s 100-alpha threshold.

Why 3 stars: A material executed token-supply update with an unusually large individual burn, while revenue attribution remains unverified.

#08 · Ecosystemverified
★★★★★

Tensia adds configurable Telegram burn alerts

Tensia announced burn alerts on November 10 covering wallet burns and buybacks, changes to emission burn allocations, and miner-burn switches. Its post describes subnet filters and configurable thresholds. These categories track different mechanisms and should not be added together as if all represented tokens destroyed in successful transactions. Our public burn archive continues to require at least 100 native tokens per individual qualifying transaction event.

Why 3 stars: A useful monitoring capability with distinct economic categories; no claim of independent end-to-end alert testing.

#09 · SN117 · everyframe.studioverified
★★★★★

SN117 Everyframe releases everycli 1.1.3 with LTX 2.5 routes

The November 11 release notes add 14 LTX 2.5 routes across native LTX, Fal and WaveSpeed, and address Google Nano Banana image-delivery failures. The notes distinguish CLI and worker updates: updating the CLI alone does not update the deployed worker. The public release and changes are verified; generation quality and a completed production rollout were not independently tested.

Why 3 stars: A meaningful product or operational change with concrete implementation evidence; production deployment and outcomes remain separately qualified.

#10 · SN124 · Swarmverified
★★★★★

SN124 Swarm consolidates its competition around Sentinel

A November 10 merged change retires the Search and Rescue and Swarm SAR families and assigns Sentinel the full competition reward share, up from 85%. Sentinel tasks drones with patrolling a solar park, reporting intruders and returning to their dock. This is a change to the project’s internal competition allocation, separate from the subnet-wide owner/validator/miner split reported yesterday. The repository merge is verified; deployment across validators is not independently established.

Why 3 stars: A meaningful product or operational change with concrete implementation evidence; production deployment and outcomes remain separately qualified.

#11 · SN25 · URverified
★★★★★

SN25 UR details subscription-cycle and provider-subsidy accounting changes

UR’s November 11 notice moves Pro data grants to each network’s own monthly subscription cycle and says a paid period’s revenue will count once across its cycle grants. The notice says some revenue previously counted twice, while long-running Google Play subscriptions could be undercounted. SN25 pool rewards remain based on completed usage, and the change concerns the operator’s separate provider-subsidy accounting. The notice says rollout confirmation will be added later, so this is a documented release change, not independently confirmed completed deployment.

Why 3 stars: A meaningful product or operational change with concrete implementation evidence; production deployment and outcomes remain separately qualified.

#12 · SN108 · ChipForgeverified
★★★★★

SN108 ChipForge separates weight updates from long design evaluations

ChipForge’s November 11 Neuron 1.0.10 change introduces an independent loop for on-chain weight submissions while design evaluations continue. The team’s commit describes an earlier multi-hour submission gap and delayed recognition of a completed probation period. The code checks on a 60-second default cadence while retaining chain rate limits. The merge and documented fix are verified; live validator adoption and realized payout timing are not.

Why 3 stars: A meaningful product or operational change with concrete implementation evidence; production deployment and outcomes remain separately qualified.

#13 · SN81 · Reliquaryverified
★★★★★

SN81 Reliquary changes restart recovery to keep order auditing moving

A November 11 merged fix parallelizes verdict reads and runs failure reconciliation behind the main auditor. The commit reports that sequential reads of about 10,000 verdicts had delayed auditing for roughly ten minutes after restarts. This is a verified code change addressing an operational delay reported by the maintainers, not independent evidence that all deployed instances have recovered.

Why 3 stars: A meaningful product or operational change with concrete implementation evidence; production deployment and outcomes remain separately qualified.

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
04

Audit trail

Coverage notes

Const reports an SN3 owner-key compromise. SN51 lium falls and Mentat reports a liquidation; Gamma records mint-and-spend transactions, while Chutes previews Parallax throughput.

Coverage: Nov 10, 2026, 10:19 AM – Nov 11, 2026, 12:40 PM ET

Searched

  • Finalized chain events and current owner holdings, all 128 configured subnet website records, authenticated public repositories, selected original ecosystem and subnet announcements, original SN3 Discord discussion and inspected attached images.
  • Three actual Grok Auto queries completed: discovery, qualitative attention and omission checks. Results were verified independently and corrected where necessary.
  • Native Videos and Live tabs checked; no newer public replay than the existing library was found. The newly listed members video is not used as public footage.

Public-data gaps

  • Individual full X/Discord histories and attached media were not completed for every active subnet; unavailable or unreviewed originals remain pending rather than no-news findings.
  • The 18 required ecosystem profiles were reviewed in bounded native windows, but complete seven-day Posts/Replies/Reposts histories and all fund principals were not completed.
  • Most secondary subnet briefs returned access errors. Primary website availability and repository activity do not establish exhaustive news coverage.
  • SN3 compromise cause and recovery, the underlying Mentat contract liquidation, and the identity and causal role of wallets behind lium selling remain unverified.
  • Authenticated TaoStats entitlement review and the remaining full-site audit interactions are incomplete; the repaired trade collector and sampled homepage were verified separately.
Browse all 100 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.

Catch up on Day 1

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.

Catch up on Day 2