Bittensor Daily News

Latest edition
#01 · Ecosystemverified
★★★★★

TAO Templar replay is available; Leadpoet remains November 5

The October29 Travis / TAO Templar conversation is now a public replay with chapters and guest links. Gavin’s Leadpoet livestream remains November5 at11AMET/8AMPT. The October28 members video is still the latest member upload; completed replays and upcoming streams are listed separately.

Why 3 stars: Original Shizzy coverage with dates and access status separated.

#02 · SN8 · Vantaverified
★★★★★

SN8 Vanta records a finalized 170.301197993-alpha burn

Successful AlphaBurned at block9392751, extrinsic11, event171 on October29 23:30UTC destroyed exactly170301197993 raw units. This meets the 100-alpha per-event minimum. The burning wallet differs from the current owner coldkey; all-wallet subnet burns and owner-only burns are different scopes. Execution does not by itself prove the source of offchain revenue.

Why 3 stars: Exact native-token transaction evidence, not an inferred revenue claim.

#03 · SN8 · Vantadeveloping
★★★★★

SN8 Vanta reports October TAO purchases

Arrash’s October29 original says Vanta Trading bought about $160,000 in TAO during October at purchase-time prices and discusses expanding funded-miner participation through Null Consensus. This is a team operating claim, not independently audited cash revenue, a new burn transaction or proof of customer retention. Earlier monthly burn aggregates remain in yesterday’s report rather than being counted twice.

Why 3 stars: A dated public operating claim with accounting scope explicit.

#04 · SN14 · Cacheonverified
★★★★★

SN14 Cacheon: finalized 4,614.416800000 alpha burn

Successful SubtensorModule.AlphaBurned at finalized block 9397215, extrinsic 12, event 169 on 2026-10-30T14:22:48+00:00. Exactly 4614416800000 raw units were burned, meeting the 100-alpha per-event minimum. Registration 4848444 and the historical project label were checked at the event block. This is an explicit transaction burn, not miner withholding, recycling or fees. Execution alone does not establish an offchain revenue source.

Why 3 stars: Verified successful transaction with exact native amount and historical registration.

#05 · SN16 · Unknownverified
★★★★★

SN16 EG registration ends; a new registration occupies the slot

Finalized lifecycle cleanup at block9392862 removed EG’s identity and registration; NetworkAdded at9392863 created a new registration with a new owner. Its allocation reset to the default vector is lifecycle cleanup, not an owner-set allocation transaction. Prior EG stories remain attached to their historical registration. The chain does not identify an offchain buyer or establish a negotiated sale price.

Why 3 stars: Finalized registration and state transitions, with buyer/price claims excluded.

#06 · SN18 · Zeusdeveloping
★★★★★

SN18 Zeus reports 25,000 forecast-archive downloads

The October 29 original reports 25,000 Hugging Face downloads and says forecasts have been hashed onchain since June 17. Downloads measure archive retrieval, not unique customers, revenue or forecast accuracy. The hashing and download aggregate were not independently reconstructed in this run.

Why 3 stars: A dated first-party usage claim with the metric’s scope explicit.

#07 · SN19 · blockmachinedeveloping
★★★★★

SN19 Blockmachine emphasizes performance-weighted traffic

The October 30 original says speed and reliability now determine node traffic and earnings in its incentive mechanism. This signals the operational goal beyond low list prices. Actual traffic allocation, latency improvements and customer retention were not independently measured.

Why 3 stars: A concrete mechanism announcement with measured outcomes left unverified.

#08 · SN22 · Desearchdeveloping
★★★★★

SN22 Desearch announces Company Search

The October 30 original introduces company lists from a plain-language brief, with country, required-signal and fit filters plus source-backed public contact and leadership records. The product homepage lists Company Search. The post’s exact documentation route returned 404 during review, so implementation details and paid usage were not tested. This adds a company-research route rather than evidence of new customers.

Why 3 stars: A concrete product capability with an explicit documentation access gap.

#09 · SN28 · SayGMdeveloping
★★★★★

SN28 SayGM expands its model catalog

October 29–30 team posts announce GPT-6.1 Terra and Kimi K3.1 Pro routes and quote launch discounts. Pricing, model identity, context limits and TEE assurances are provider claims and can change; they were not benchmarked or audited here. The useful development is another announced access route, not proof of identical quality or sustained lowest cost.

Why 3 stars: An attributed catalog update with price and verification limits.

#10 · SN49 · Nepher Roboticsdeveloping
★★★★★

SN49 Nepher opens Franka Tabletop RL Challenge Phase 1

The October 30 original says Phase 1 is live: miners develop policies teaching a Franka arm to grasp, carry, place, stack and pack objects on a cluttered table. This is a new robotics participation task, not evidence of a deployed factory customer or measured real-world success.

Why 3 stars: A specific live competition; routine participation updates remain three stars.

#11 · SN58 · Attunedeveloping
★★★★★

SN58 Attune raises generalization tests with Level 3

Robotensor’s October 29 original says Level 3 changes object models and categories, sizes and colors while varying scene conditions. Its clip explicitly labels Level 3 live. The team reports Level 2 ended at 92.5% after 125 duels; these are its simulation-competition results, not independently measured physical-robot adoption. The harder task aims to distinguish generalization from memorizing one object.

Why 3 stars: A concrete competition update with team-reported metrics bounded.

#12 · SN59 · Unknownverified
★★★★★

SN59 owner share rises to 31.9696% in a finalized allocation

At finalized block 9391035 on October 29 17:46:48 UTC, owner allocation changed 30.1% to 31.9696%, validators 36.9% to 35.0304%, miners stayed 33%; TAO and recycle slots remained zero. Extrinsic 18/event197 executed successfully. Exact five-slot vectors and registration8938771 are retained in permanent evidence. Root baseline is paid first and capped by validator allocation; displayed yield history can lag. This is not a transaction burn.

Why 3 stars: A verified allocation event with exact before/after values and registration.

#13 · SN62 · Ridgesverified
★★★★★

SN62 Ridges: finalized 182.481106887 alpha burn

Successful SubtensorModule.AlphaBurned at finalized block 9397157, extrinsic 39, event 245 on 2026-10-30T14:11:12+00:00. Exactly 182481106887 raw units were burned, meeting the 100-alpha per-event minimum. Registration 4474225 and the historical project label were checked at the event block. This is an explicit transaction burn, not miner withholding, recycling or fees. Execution alone does not establish an offchain revenue source.

Why 3 stars: Verified successful transaction with exact native amount and historical registration.

#14 · SN65 · True Performance Networkdeveloping
★★★★★

SN65 TPN introduces quantized-model validation

October 30 TPN announces a workbench tool comparing a quantized model with its parent using next-token agreement, KL divergence and perplexity. The public workbench describes validation tied to exact weights and a quote-before-run workflow. This can help developers assess a compression tradeoff; no paid job was run and the reported measures are not a universal proof of equal downstream quality.

Why 3 stars: A usable developer-tool announcement; independent execution and output verification remain untested.

#15 · SN91 · cascadeverified
★★★★★

SN91 Cascade merges per-round eligibility code

GitHub PRs 382 and 383 merged October 29. Trainer code replaces lifetime hotkey submission exclusion with per-settlement-round eligibility; documentation separates CPU generation from the GPU training clock and requires 32-channel generators. The PR explicitly says the rule applies on trainer restart. A merge and a scheduled launch target do not verify production activation; larger GPU layouts remain planned.

Why 3 stars: Verified code and documentation changes, not a claimed live activation.

#16 · SN92 · REAXdeveloping
★★★★★

SN92 REAX schedules demand-linked inference and competition rewards

The official FAQ, updated October 29, marks the new policy approved from the first weight set after the October 30 14:30 UTC engine slot. Inference is planned to move from 50% to 40% of miner emissions. Competition champions retain full payment for three days, followed during a pause by decay to day seven and keep-alive treatment. Unused allocations are intended to be burned. These are miner-emission policy plans, not a verified eTAO-vector change or qualifying transaction burn; execution at the scheduled boundary was not established by this review.

Why 3 stars: Material miner rules with effective-time and denominator separated from chain execution.

#17 · SN105 · Beamdeveloping
★★★★★

SN105 Beam reports Hugging Face and Zapier connectors

Beam’s public product site lists Hugging Face among its connectors; byteleap’s October 30 original also reports the Hugging Face and Zapier integrations live. This offers routes for moving datasets and model weights into existing workflows. No authenticated transfer or Zapier partner-directory verification was performed. Platform-wide Hugging Face catalog sizes are not Beam customer counts, and this is one integration story rather than separate repeated launches.

Why 3 stars: Concrete integration announcements with testing and partner-verification limits.

#18 · SN118 · Dittodeveloping
★★★★★

SN118 Ditto announces agent navigation and Router work

The October 30 original describes an agent-only sidebar, a single launcher for apps/code/tools and simpler app connections. An October 29 team follow-up also discusses Router MCP injection and remote control for Claude Code. This is a product and workflow update; no installed client or customer deployment was independently exercised.

Why 3 stars: Specific first-party product changes without inferred adoption.

Smaller developments and early plans. Verification labels distinguish confirmed information from developing claims.

#19 · SN1 · Apexdeveloping
★★★★★

SN1 Apex: Apex reports screener and live-data fixes

The public dated brief reports corrected handling of rejected submissions and live competition data. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#20 · SN33 · ReadyAIdeveloping
★★★★★

SN33 ReadyAI: ReadyAI plans a shift away from conversation tasks

The brief attributes a phased task transition over coming weeks to the team. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#21 · SN34 · Yugosdeveloping
★★★★★

SN34 Yugos: Yugos reports timeout repair and escrow refund

The brief describes an affected provider timeout edge case and a repair nearing completion. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#22 · SN44 · Scoredeveloping
★★★★★

SN44 Score: Score removes annotation-error blocks

The brief reports removal of five flawed challenge blocks and clarified scoring rules. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#23 · SN54 · Yanezdeveloping
★★★★★

SN54 Yanez: Yanez explains reward-cycle dashboards

The brief describes cycle rewards, dashboard timing and the next phase. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#24 · SN55 · NIOMEdeveloping
★★★★★

SN55 NIOME: NIOME reports token migration underway

The brief attributes a started migration to the team; holder-specific instructions were not independently validated. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#25 · SN71 · Leadpoetdeveloping
★★★★★

SN71 Leadpoet: Leadpoet reports scoring and research-record repairs

The brief reports corrected company-size evidence scoring and additional research records. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#26 · SN75 · Hippiusdeveloping
★★★★★

SN75 Hippius adds language options to its website

The October 30 original announces French, German, Spanish, Simplified Chinese, Brazilian Portuguese and Greek alongside English. This can lower the navigation barrier for users; a localized website is not proof of new adoption. Yesterday’s CDN firewall story remains in its original edition.

Why 2 stars: Useful access improvement, not a major infrastructure milestone.

#27 · SN78 · Umideveloping
★★★★★

SN78 Umi: Umi reports C7 challenge intake complete

The brief reports129 certified entries and125 timely uploads, with evaluation still underway. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#28 · SN80 · OpenRobotodeveloping
★★★★★

SN80 OpenRoboto schedules a peaq discussion

The October 30 original invites users to a discussion next Monday about robot-training data, machine identities and the machine economy, with a teaser for more information. This is a scheduled conversation, not confirmation of a new partnership execution. Unresolved allegations about another project are excluded pending identity and primary relationship verification.

Why 2 stars: A useful dated plan; teaser wording does not establish execution.

#29 · SN88 · Investingdeveloping
★★★★★

SN88 Investing: SN88 prepares MetaTrader mining

The brief describes planned mining mechanics through a graylist release; participation remains subject to primary instructions. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#30 · SN118 · Dittodeveloping
★★★★★

SN118 Ditto: Ditto reports agent screening and a grader investigation

The brief reports released screened agents and an unresolved grading issue. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#31 · SN120 · Affinedeveloping
★★★★★

SN120 Affine: Affine investigates stuck evaluations

The brief reports evaluations stuck over12hours and work on larger batches; resolution is not verified. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#32 · SN121 · sundae_bardeveloping
★★★★★

SN121 sundae_bar: Sundae Bar publishes an SBC33 brief

The brief says submissions are scheduled to open at noon EDT. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

#33 · SN124 · Swarmdeveloping
★★★★★

SN124 Swarm: Swarm reports a new challenge and evaluation backlog

The brief attributes a launched challenge and paid-submission queue to the team; scoring and throughput outcomes are unverified. This is an attributed public summary of Discord activity, not independent primary execution or customer verification. Follow original team instructions before acting.

Why 2 stars: Useful operator information with its secondary source and verification gap explicit.

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

Desearch adds company search; TPN introduces quant validation; Nepher opens a robotics challenge. Also: REAX incentive plans, Attune Level 3, Cascade code changes, Beam integrations, Ditto updates and finalized SN59/SN16/SN8 carry-forwards.

Coverage: Oct 29, 2026, 10:04 AM – Oct 30, 2026, 9:57 AM ET

Searched

  • 128 active project profiles and dated briefs; 136 repository paths; public X feed and direct original follow-ups
  • Signed-in Grok daily discovery/top-five; owner bookmarks, originals, quotes, replies/reposts; Const and Tensia accounts
  • Finalized lifecycle, allocation and burn event scans; 128 owner holdings; YouTube Videos and Live tabs

Public-data gaps

  • Discovery reviewed 128 project profiles and dated briefs plus 136 repository paths, with three repository access failures; private channels and every individual X reply were not exhaustively checked.
  • Secondary Discord briefs remain attributed developing reports. Selected attached images and video frames reviewed; full long-video viewing and independent benchmark/customer audits were not performed.
  • Final Grok omission query reached the signed-in usage limit. Discovery and qualitative top-five response succeeded; no successful final omission response is claimed.
  • TaoStats local server API key was unavailable; no fresh TaoStats cross-check or credit usage verification. Configured archive evidence and existing shared site cache remain primary.
Browse all 83 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