Dates and verification labels belong to the original edition. A past verified announcement can now be outdated. Historical project names are retained; an SN filter searches the slot across registrations. All keywords must match the story text or subnet label. Ratings describe editorial priority, not investment quality.
SN122 CookingTAO outlines further public-launch steps
The October 18 digest describes a sequence of code publication, compute-miner deployment work, public opening and a management-portal beta. These are proposed next steps; the digest also distinguishes published miner code from code actually earning. We do not call the public portal launched or convert earlier month-on-month growth projections into completed revenue.
An explicit staged roadmap is useful only when publication, access and earnings are kept separate.
SN125 Refinery adds durable validator deployment and restart documentation
The primary SN125 repository adds deployment guidance for an update supervisor that restarts at round boundaries, a persistent payment ledger and round checkpoints. Documentation separates monitored container updates from an immediate mid-round image swap. The code/docs are public, but a large upload does not itself verify a new live competition or customer revenue. Conflicting historical repository mappings to SN123 are not used to duplicate this story.
Recovery and accounting documentation address concrete operator risks without implying a production launch.
SN1 Apex launches an agent-built incentive competition
On October 16, SN1 Apex announced an incentivized competition built by agents from a prompt by Const. Its follow-up links a live NIST-Lite robotic assembly contest. The team says development took six hours without human coding; that is an attributed development claim, not a benchmark we reproduced. Const’s quote-post invites agents to mine it. The important change is a concrete competition to participate in, rather than another promise about agent-built economies.
An announced live incentive mechanism connects autonomous development to an actual competition; development-time claims remain attributed.
SN2 DSperse announces a DaniLabs handover agreement
Inference Labs announced October 16 that it has entered an agreement for Dan to take over SN2 as DaniLabs, focusing on fast, affordable inference. This is an announced agreement, not a chain-confirmed completed sale. Our finalized comparison from block 9,296,035 to 9,306,529 found no change to SN2’s owner or registration height, and its stored name remained DSperse. No sale price or executed buyer identity is inferred. Unverified accusations in channel discussion are excluded.
A change in project leadership and product direction is material, with agreement and execution explicitly separated.
SN4 Targon publishes its eTAO discussion with Const
SN4 Targon published Talking Targon Episode 01 with Const on October 17 UTC, covering emission controls, guardrails and compute economics. This is a newly released discussion, not proof eTAO is active on Finney. Our finalized runtime check at block 9,306,529 still returned spec 479; the newer eTAO changes are present in primary code. The revenue-dashboard milestone was covered yesterday and is not presented again as new revenue.
A new first-party protocol discussion is useful context, while release and activation remain separate.
SN7 Allways incident remains open while recovery code lands
The October 17 channel digest reports an October 14–16 miner-side failed-swap exploit, a halt for patching and planned reimbursements. These incident and reimbursement details remain secondary reporting; we did not inspect private original messages or confirm every refund. Primary code separately bounds event ingestion to prevent backlogs blocking votes and enriches swap/configuration event logs. Those repairs support an operating recovery story, but do not establish that service has resumed or that the exploit is fully resolved.
A reported exploit and halt affect participants directly; available recovery code is distinguished from a confirmed all-clear.
SN10 Pareton interview is scheduled for October 20
The channel Live tab now lists “Can Bittensor Make AI Faster and Cheaper? Inside Pareton SN10” for October 20 at 1:00 PM Eastern / 10:00 AM Pacific (17:00 UTC). The YouTube player confirms upcoming status, not a live broadcast. This listing was verified at 23:59 UTC, after the main news cutoff. The site reminder and library now point to the scheduled interview while retaining the latest public replay as the default player.
A verified upcoming interview is clearly dated and does not imply a completed product launch.
SN14 Cacheon evaluation pause remains a capacity issue to watch
The October 17 channel digest attributes the evaluation pause to GPU availability and cost, and reports a team expectation to resume the following morning. That is a forecast, not a verified restart. Public product-website work was also collected, but it does not prove the evaluation backlog has cleared. Private original messages and live evaluation telemetry were not independently inspected.
A reported evaluation interruption affects participants; a promised restart is not an all-clear.
SN15 ORO bounds validator file reads and sandbox disk use
Primary SN15 ORO changes cap reads of sandbox outputs/logs and bound per-evaluation disk use, with evaluation failure when budgets are exceeded. The stated purpose is to stop malformed output or excessive files from exhausting validator resources. This is verified implementation work, not a claim that a specific production exploit occurred or that every operator has deployed it.
Resource limits protect evaluation availability against a concrete failure mode.
SN16 Zero Hour is the finalized name; its robotics concept remains a demo
At finalized block 9,306,529, SN16’s stored name is Zero Hour, with a description about robot-task disruptions and recovery demonstrations for VLA training. The linked fast-thinker/kenju repository still calls the subnet proposed and its current implementation a local symbolic demo. That verifies the identity and concept, not a production mining launch or completed sale. The alpha/TAO snapshot showed +18.24% over 24 hours at 23:49 UTC; price is not proof that the concept is operating.
The name change is useful history, but the repository explicitly limits the implementation to a demo.
SN28 SayGM reports its second burn cycle, with a finalized burn receipt
SN28 SayGM reports $104,372 burned against $514,686 of miner emissions for September 16–October 15, or 20.3% coverage. We independently decoded a successful burn_alpha at block 9,296,823, extrinsic 11: AlphaBurned records 10,771.229342391 SN28 alpha. The burn is verified; the dollar valuation and cycle-wide offset calculation remain the project’s accounting. Its page says some burned alpha comes from customer payments, so the dollar total should not automatically be described as cash spent buying tokens.
A successful burn is independently confirmed on chain; valuation and emission coverage are separately attributed.
SN28 SayGM adds DeepSeek Flash with SN90 KubeTEE
SN28 SayGM announced DeepSeek-V4.1-Flash-1017 availability on October 17 and credits SN90 KubeTEE for day-zero onboarding. The primary miner repository allows the model and promotes gm-miner 0.5.2. The team advertises confidential delivery and pricing 10% below list. We verified the announcement and supporting code, but did not send a paid inference request, audit the security boundary or independently measure model performance.
A named model integration links two subnets to a customer-facing service; price and security claims are attributed.
SN44 Score gives an early look at its new Studio
The October 16 SN44 Score post shows a Studio preview in which a user corrects a visual interpretation through conversation. The caption calls it a first look and says more is coming, so this is a demonstration rather than a confirmed public release. We inspected the playing clip. Separately, the October 17 channel digest reports Fallen Person Detection restored and PPE active again; those operating updates remain secondary and are not treated as independently verified uptime. Recirculated September break-even claims originated October 1 and are not a new October 17 revenue milestone.
A real product demonstration and attributed operating recovery are useful; old financial claims are not repackaged as new.
SN49 Nepher Robotics reports a stronger third-phase run/jump result
SN49 Nepher Robotics announced completion of Humanoid Run Jump Phase 3 on October 16, reporting a winning score of 0.8245 versus 0.6750 and 0.7735 in the prior phases using the same Unitree G1 task. These are team-reported competition scores, not an independently replicated physical-robot result. The October 17 digest also clarifies submissions run October 5–18; participants should check the team’s current timeline before acting on a deadline.
A dated result on a consistent task offers a concrete progress signal while its measurement limits remain clear.
SN51 Lium strengthens GPU-node qualification and CLI availability
Primary SN51 Lium code now fails unrented nodes when sshd does not start in the platform’s filler container, rather than treating installed software as evidence of a usable connection. Another fix limits a portal deletion to the named node. The CLI exposes free GPU counts on partly rented nodes and can upload Docker build context. These are specific operator/customer reliability improvements, not evidence for promotional payout comparisons or a new revenue total.
Changes address whether advertised GPU capacity is usable and make remaining capacity visible.
SN56 Gradients pauses environment tournaments while retaining their emission settings
The primary change disables new environment tournament starts and skips leftover pending/active environment rows until the full sunset. Its documentation explicitly leaves the environment emission share and related weight endpoints in place for the week. Text and image tournaments retain their separate schedules. A pause in scheduling should therefore not be described as an immediate removal of that emission allocation.
An explicit operating pause changes miner expectations; emission treatment is separately documented.
SN60 Bitsec announces SN105 Beam as a continuous-coverage client
SN60 Bitsec announced October 16 that SN105 Beam is now covered by Sentios Continuous Coverage, pointing to an active-project listing and a GitHub badge. The original announcement is readable, but our attempted active-project page fetch failed and the public BeamCore README examined did not independently confirm the badge. This remains a team-announced client relationship pending stronger confirmation from the other side. No contract value, vulnerability finding or security guarantee is inferred.
A named subnet customer could demonstrate commercial utility, while incomplete two-sided confirmation remains explicit.
SN64 Chutes transcription issue is reported in the playground
The October 17 channel digest reports a team member observing gibberish or incomplete output from the audiodojo speech-to-transcription path in the playground. This is a specific reported model/path issue, not evidence that all SN64 inference is unavailable. We did not reproduce the request or verify a resolution; keep it on the operating watch list.
A narrowly described customer-facing failure merits follow-up without overstating a network-wide outage.
SN67 Harnyx adds separately citable visual and structured page retrieval
SN67 Harnyx announced October 16 that Expand Fetch is available to every miner as a page-fetching tool. Each request provides a page representation preserving tables/layout and separately citable hidden structured data as JSON. This matters for tracing research claims to what an agent actually retrieved. We verified the original announcement; improved answer quality is an intended benefit, not a benchmark we independently measured.
A specific retrieval integration improves the evidence available to competing research agents.
SN68 NOVA clarifies reproducibility requirements
The October 17 digest attributes a rule clarification to the team: pretrained coefficients without verifiable training methods/data are not allowed, while training a surrogate inside the sandbox budget is permitted. This is secondary reporting of a qualification rule, not a finding that any named miner cheated. Primary enforcement and updated formal rules remain follow-up items.
A specific reported submission constraint is useful to miners without turning discussion into an accusation.
Searches published headlines and summaries, not private bookmarks, unpublished leads or source-page contents. Duplicate headlines within an edition appear once; separate editions remain separate so follow-ups are preserved. Share the page URL to retain your filters.
