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.
SN118 Ditto opens a business partner program
SN118 Ditto’s public partner page now offers consultants, agencies and service providers a share of a client’s setup fee and recurring monthly retainer. Partners can offer the service under their own brand; each client receives a scoped build, hosting and support. Shares, tiers and terms are individually agreed rather than a published universal commission rate. This turns yesterday’s forthcoming partner-program mention into an inspectable offer. It is a distribution channel, not evidence that new deals, profit or buybacks have already occurred.
A verified public commercial program with concrete referral and service mechanics, beyond yesterday’s first-client announcement.
SN118 Ditto announces a live campaign with SN93 Bitcast
SN118 Ditto’s October 9 post says its Stitch3 Creator Campaign with SN93 Bitcast is live, with creators producing posts about Ditto V2. That is a distribution campaign for a Bittensor product, separate from yesterday’s first-business-client announcement. The original Ditto statement was checked; independent campaign performance, spend and customer conversions were not established. The announcement does not turn views or creator posts into verified revenue.
A distinct cross-subnet distribution campaign, with commercial results and counterparty confirmation still limited.
SN120 Affine publishes finalized training evidence and selection accounting
SN120 Affine’s October 10 changes publish finalized training inputs, diagnostics, evaluation evidence and actual selection/exclusion accounting. Its signed history catalog links retained evidence from round 14 onward. The documentation separates this read-only evidence exporter from mining admission, reward rules and training itself, and distinguishes completed learning cycles from public mining cadence. The fresh run starts from Qwen2.5-Math-7B-Instruct; older runs remain historical records. This improves inspectability without proving a new state-of-the-art result or treating every accepted submission as a training example.
Primary training and evaluation records make the learning process more accountable, without promoting infrastructure evidence into a benchmark victory.
SN127 Astrid: payout schedule and competition pause outlined in brief
SN127 Astrid’s October 10 Discord summary relays a message posted on behalf of the team: MS5 payouts are intended to finish October 15, with MS6 and MS7 starting by October 20 and running four weeks under Astrid Score. Competitions would pause after MS7 while the archives and scoring are reviewed, including a proposed buy-and-hold hurdle. The original delegated speaker and live payout execution were not independently verified. Treat these as reported plans, not completed payments or a finalized new scoring rule.
Specific upcoming payout and evaluation changes merit monitoring, with delegated attribution and future execution made explicit.
SN3 Teutonic changes how evaluation handles document boundaries
SN3 Teutonic published document-masked evaluation and token-weighted scoring on October 9. The new policy isolates document fragments, resets positions and excludes predictions across document boundaries. It also supports additional whole-document sampling from roughly 2K to 8K tokens. Deployment instructions require coordinated validator and evaluator policy identities, so this is a source-level evaluation change rather than proof that every current score already uses it.
A substantive evaluation-method change with explicit deployment requirements.
SN9 Iota reports SDK training across 139 consumer GPUs
Macrocosmos shared fresh SN9 Iota SDK results on October 8, one week after its Exploit Summit announcement. The team reports a 16B model trained across 139 RTX 4090/5090 GPUs with 1.8× faster wall time than its legacy stack, plus 30% shorter butterfly all-reduce times. It also reports 878 tokens per second serving gpt-oss-120b to 32 users on A6000s. A separate distributed 7B GRPO experiment improved MATH-500 from 63.6% to 68.4%. These are different workloads and team-reported measurements, not a single universal speedup or independent benchmark.
Concrete post-conference training, inference and reinforcement-learning results, with hardware and baseline context retained.
SN14 Cacheon and SN46 Instant: Const highlights the inference race
Const’s October 9 post drew attention to an inference-speed comparison between SN14 Cacheon and SN46 Instant. The image reports 205.40 versus 162.61 tokens per second and lower first-reasoning latency for the shown SN14 Cacheon run. But the tests differ: SN14 Cacheon ran locally with GLM-5.3 NVFP4 on four B300s using SGLang; the SN46 Instant comparison used a GLM-5.3-Flash FP8 API run on two B300s with vLLM, according to the visible technical reply. Treat this as commentary on competitive optimization, not a controlled winner-takes-all benchmark. Separately, SN14 Cacheon reports its first customer, SN120 Affine, and a team-measured 40.9% throughput improvement for the optimized Qwen workload.
Relevant Const commentary plus a team-reported customer milestone, with unequal model, hardware and serving conditions made explicit.
SN15 ORO opens AssistantEval’s replayable assistant tests
SN15 ORO pointed to AssistantEval on October 8. The public benchmark contains 34 tasks in resettable synthetic services, grading what happened in service logs rather than accepting an assistant’s claim that it finished. Its displayed results also expose reliability: 31% of assistant-task results that passed once failed on another attempt. This is useful scrutiny of agents handling inbox, calendar and other multi-step work. The site explicitly presents evaluation results, not demonstrated training gains or a guarantee about real accounts.
A public, inspectable evaluation framework that measures outcomes and repeatability rather than just persuasive responses.
SN17 404 shows Sundrift, another game-jam build
SN17 404 shared Sundrift on October 9, a mountain-pass drift racer built using its game generator with procedural 3JS assets. The point is another concrete example of the creation tool in use, rather than a new subnet launch. Const’s October 7 reaction to the earlier Farseek game is retained as dated commentary in the source review, not relabeled as today’s product release.
A fresh product demonstration; its significance is practical use rather than a new platform or commercial milestone.
SN19 blockmachine announces live Arc RPC endpoints
SN19 blockmachine announced dedicated Arc mainnet RPC endpoints on October 8, with dollar-denominated pricing and payment in USDC. The team advertises pricing up to 60% below centralized alternatives, a comparison that depends on the actual endpoint plan and usage. The material development is support for another network through the subnet’s infrastructure product; no new customer total or revenue figure was disclosed.
A specific new service offering, with comparative pricing treated as a team claim.
SN22 Desearch announces a Raycast MCP Registry listing
SN22 Desearch says its search tools are now listed in Raycast’s MCP Registry, giving Raycast users another installation route for its search service. This October 9 announcement is separate from the October 6 Gemini CLI extension resurfacing in TAO Daily’s October 8 article. A registry listing reduces discovery and setup friction; it does not by itself demonstrate new paid usage.
A distinct new distribution listing, deduplicated from older Gemini CLI coverage.
SN25 UR records a deployment, with provider rollout still gated
SN25 UR’s primary launch document now records an October 8 deployment, contract calls and a validator activation block. It describes one launch validator and a weekly epoch configuration from epoch 1, effective at block 9,247,228. Operator enablement and reserved-slot upload still follow the epoch start. The record is more concrete than generic migration chatter, but it is the project’s deployment account: this edition did not independently replay every chain receipt or verify that all providers are operational and receiving rewards.
A primary deployment record with remaining rollout gates stated explicitly.
SN28 SayGM ships a CLI for model access and agent deployment
SN28 SayGM’s October 9 CLI announcement is backed by a public product page. It documents setup for Claude Code, Codex, Hermes and OpenClaw; terminal chat and shell-output prompts; and Hermes/OpenClaw deployment to Phala confidential VMs, SSH servers, EC2 or local Docker. The page specifies Node.js 22 or later and Windows, macOS and Linux support. This makes the gateway easier to use in existing coding and agent workflows. Documentation was checked; deployments and billing were not exercised.
A concrete new product surface with documented setup, deployment and automation capabilities.
SN30 Endure: Forge and TAO.com announce wrapped-alpha collateral collaboration
Forge announced on October 9 that it will build on TAO.com’s wstAlpha wrappers to bring alpha collateral to mainnet. Both TAO.com and SN30 Endure acknowledged the collaboration. The intended benefit is liquidity access without first selling the underlying alpha exposure. The language is explicitly forward-looking: these posts do not establish that borrowing markets are already open, disclose collateral parameters or independently verify the scope of any audit.
Both sides acknowledge a concrete infrastructure collaboration, while live lending and risk parameters remain unconfirmed.
SN46 Instant’s public dashboard gets a Const spotlight
Const linked InstantNetwork on October 8 evening Eastern. Its public dashboard identifies SN46 Instant and exposes miner throughput, request failures and scoring. The inspected October 9 16:16 UTC epoch snapshot showed six miners and 164.8 tokens per second as the mean of miner medians, with 7 failures among 1,237 routed requests. These are workload- and epoch-specific operational observations, not audited revenue or a guarantee about a user’s own prompts. The pointer gives readers a way to inspect the network instead of relying only on screenshots.
A directly inspectable operational dashboard and a relevant Const pointer, with metrics defined and timestamped.
SN49 Nepher demonstrates its robot policy on real hardware
SN49 Nepher’s October 9 demonstration shows an SO-ARM101 writing the team’s name and tracing its logo in simulation and on the physical arm. The team contrasts this with a July test where a circle that worked in simulation failed on hardware. This is a concrete sim-to-real progress demonstration for the shown task. It is not evidence of general-purpose manipulation, a broad benchmark win or readiness for every robot embodiment.
A visible real-hardware milestone with a specific task and an appropriate limit on generalization claims.
SN51 lium.io changes its missing-settlement fallback in code
SN51 lium.io merged a validator change so a missing settled window submits no new weights, retaining the weights already in force rather than sending a fallback burn vector. Inclusion reports are kept and retried instead of being lost if posting fails. This concerns a particular settlement failure path, not a blanket end to burns or a new revenue announcement. The merged implementation was reviewed; production adoption was not independently confirmed.
A meaningful settlement and reward-continuity fix, with the failure path clearly scoped.
SN54 Yanez announces a US sponsor-bank partnership
SN54 Yanez announced a partnership with an unnamed US-based banking-as-a-service sponsor bank on October 8. Yuma highlighted the distribution opportunity on October 9: sponsor banks provide regulated infrastructure behind consumer fintech products. That potentially puts financial-crime tools closer to institutional workflows, but neither post names the bank or discloses contract value, rollout scope or revenue. This is a team-announced commercial development, not proof that all fintech customers of the bank have adopted SN54 Yanez.
A potentially material institutional channel, with important commercial details and independent counterparty confirmation outstanding.
SN55 NIOME sets October 28 for phased GENOME migration
SN55 NIOME’s October 9 announcement sets October 28 as the migration opening date. The first batch is intended to move 5% of GENOME’s snapshot market capitalization into SN55 NIOME, with later batches continuing the process. The team describes escrow, delivery verification and burning the original tokens only after successful delivery, with refunds if a swap fails. The portal link is promised when migration opens; this is not a swap already available today or an independently tested guarantee. At the 17:22 UTC market snapshot, SN55 NIOME was up 19.47% over 24 hours in alpha/TAO terms; that does not prove the announcement caused the move.
A dated migration plan with specific batch and settlement mechanics, supported by the original announcement; execution remains future.
SN58 Attune opens Vector, an adaptive-robotics competition
Announced October 8 after the previous report’s cutoff, SN58 Attune is Robotensor’s competition for robots that adapt from demonstrations instead of needing a fresh model for every task. Its public site marks Vector live: submitted models face matched demonstrations, starting states and randomized simulation conditions. Horizon, combining human-video learning and world-action models, remains coming soon. New code rejects commitments made before a configured competition start block. This verifies the public competition launch and entry framework; it does not establish that miner rewards are already flowing.
A substantive new robotics competition with a public product, rules and matching implementation; reward activation remains separate.
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.
