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.
SN109 Finsight sale reported; buyer reveal and completed transfer remain pending
SubnetRadar’s October 11 Discord digest reports that SN109 Finsight has been sold to a known community member who has launched multiple subnets. It says the buyer requested a delayed reveal and will announce after claiming the subnet. The original private-channel messages were not independently read, and no sale price or buyer identity is verified here. Treat this as a reported agreement with transfer confirmation pending, not proof that a new operator has already taken control. Separate conviction-lock activity in the chain-event feed does not establish the sale.
A potential ownership change is material, but secondary reporting and unconfirmed transfer limit confidence.
SN117 EveryFrame adds direct Vivix W1 access for miners
SN117 EveryFrame’s October 11 miner update adds a direct Vivix W1 provider and everycli API-key support. This expands the supported video-generation route and credential setup for operators using the published miner. It is a concrete integration change, not evidence of new customer revenue, universally available provider capacity or improved benchmark performance.
A working provider integration broadens miner options with clear limits on what the release establishes.
SN120 Affine separates epoch openings from hourly reward processing
SN120 Affine’s October 11 documentation says that from epoch 136, opening a mining epoch no longer waits for a fresh hourly reward assessment. When fresh processing fails, the reward writer retains the last valid assessment and maps rewards to current registrations; this is not an owner-only or burn fallback. Audits and reward penalties remain separate, and the change does not itself alter miner quotas or the training optimizer. The same day’s fixed-endpoint results show 78 to 84 correct answers on one 128-task diagnostic cohort and 91 to 92 on another. Both paired uncertainty intervals include zero, and these cohorts were already exposed: this is not independent proof of improvement over the upstream base model.
A concrete continuity change and inspectable evaluation results matter, with uncertainty and baseline limitations preserved.
Taoswap adds desktop-native limit orders for subnet trading
Taoswap’s October 11 announcement introduces desktop-native limit buys and sells: users set a price and amount, with an option to keep orders out of the public order book. The team credits TAO.com for the underlying technology, previously launched in its mobile app and browser extension. This is a new desktop trading feature beyond the interface rebuild covered earlier this week. A limit price does not guarantee that an order will fill.
A directly announced trading feature gives subnet users more control over execution without requiring a new token or inferred partnership.
SN13 Data Universe fixes validation of fresh Reddit posts
SN13 Data Universe merged a validator-side fix after yesterday’s cutoff to stop rejecting fresh Reddit posts against an archive snapshot that does not yet contain them. That addresses a specific false-failure path in data validation. The merged release is verified; it does not show that every validator has adopted the fix or require treating a new miner release as the remedy.
A concrete reliability fix affecting valid data submissions and their scoring.
SN44 Score: challenge pipeline outage reported
SubnetRadar’s October 10 Discord brief reports that SN44 Score’s data pipeline stopped creating challenges, including Worksite PPE tasks. The brief attributes an expected return at the next tempo to the team and notes one annotation block was removed. The underlying private conversation and subsequent recovery were not independently verified. This is an operational incident watch, not a confirmed current outage duration or an all-clear; unrelated miner allegations are not repeated as facts.
Potentially material disruption to miner evaluation, explicitly retained as secondary-source developing coverage.
SN48 Quantum Compute publishes its 2.0 mining overhaul
SN48 Quantum Compute published its 2.0 release on October 10. The new miner documentation describes receiving quantum-circuit jobs, submitting them through a provider adapter, uploading results and answering subsequent status queries. This creates a path for provider-backed quantum execution rather than treating a repository release as proof that every miner owns quantum hardware. Crucially, the miner README still says “COMING SOON.” The implementation is published; open participation and paid mining activation are not established by that commit.
A substantial implementation and execution-model change, with the explicit upcoming-miner label preserved.
SN51 lium.io reports $1.4 million in monthly GPU rental spend
SN51 lium.io’s October 10 month-in-review reports GPU rental spend up 45%, active users up 16%, rentals up 106% and first-time renters up 32%. It also reports 15% more providers and 32% fewer rental failures. Opentensor highlights $1.4 million of GPU rental spend over 30 days. That is marketplace spend reported by the team and amplified by Opentensor, not profit, independently audited revenue or a guaranteed token-holder return. This is fresh operating data rather than a repeat of the previously covered buyback announcement.
Specific usage and reliability metrics indicate commercial activity, with spend distinguished from profit and audited revenue.
SN60 Bitsec names TWIF as a continuous-security client
SN60 Bitsec announced on October 9 that TWIF has signed up for Sentios Continuous Coverage of its codebase. The direct connection here is a named client for a Bittensor security service, not unrelated token-market coverage. The team’s announcement is verified, but contract value, actual service activity and independent confirmation from the named client were not established during this check. Coverage does not endorse the client or guarantee that its code is safe.
A named customer claim for the subnet’s security product, with terms and independent counterparty evidence outstanding.
SN61 RedTeam: browser failures reportedly affect Ada-3 scoring
SN61 RedTeam’s October 10 dated brief describes Multilogin failures affecting Ada-3 submissions since October 8. A participant reports two of four runs missing; the brief attributes acknowledgment of a browser problem and a planned restart to a team member. It also says there was no rescore mechanism for affected submissions. These are secondary summaries, not an independently replayed scoring failure. Recovery and any compensation remain unconfirmed.
A scoring-reliability issue with direct participant consequences, without presenting a planned restart as a completed fix.
SN62 Ridges merges validator evaluation load balancing
SN62 Ridges merged validator scheduling and load-balancing work on October 10, with matching endpoints, queries and database changes. This concerns distributing evaluation work rather than a new model or another change to yesterday’s upload pricing. The implementation is in the repository; production adoption and measured queue-time improvements were not independently tested.
A relevant evaluation-capacity change, qualified as merged implementation rather than proven live performance.
SN71 Leadpoet tightens arena publication evidence
SN71 Leadpoet’s October 10 arena changes bind incomplete-publication judge witnesses to the current round. This reduces ambiguity about which round’s evidence is used when a publication remains incomplete. The wider development window includes scoring and claim safeguards, but commit volume alone is not a business milestone. These are verified reliability changes rather than a new customer, investment or independently measured model improvement.
Concrete safeguards for competition evidence and reward-related decisions.
SN74 Gittensor expands rental visibility and fixes SparkInfer builds
SN74 Gittensor’s rental tooling adds per-box market status, pinned hotkeys and busy-state visibility. Separately, SparkInfer’s 0.6.33 documentation adds Swift-Qwen3.8-27B support; the following 0.6.34 fix restores linking when NVFP4 is disabled, including affected Windows binaries. These are distinct operational improvements to renting compute and running inference. Published benchmark comparisons depend on the tested model, hardware and workload and are not a blanket speed advantage.
Useful rental and inference compatibility improvements backed by exact changes, without overstating benchmark scope.
SN75 Hippius: eight-day confidential-VM test reports 99.84% successful checks
TAO Daily’s October 10 report describes Marcus “Mogmachine” Graichen’s September 30–October 9 evaluation of four SN75 Hippius confidential-VM servers in France and the Netherlands. It reports 4,292 of 4,299 scheduled checks succeeding, with seven network-related failures and automatic recovery. That 99.84% figure describes the sampled checks, not the probability that a workload is secure or an independent guarantee against every attack. The article describes the service as beta. The original raw test report was not independently reproduced, so this remains attributed developing coverage rather than a newly verified universal security claim.
Specific external testing adds evidence about reliability, with sample size, beta status and verification limits retained.
SN81 Reliquary adds a general and tool-use training corpus
SN81 Reliquary’s October 10 environment release adds 113,355 prompts across 127,766 rows, with a pinned dataset and integration as a stage-A corpus source. The environment includes instruction-following, structured-output, clarification and function-call grading, while some conversational categories remain ungraded. The practical change is broader, inspectable training material and evaluation rules. This is published corpus infrastructure, not evidence that a newly trained model has already beaten external benchmarks.
A sizable pinned training corpus and matching integration expand what the subnet can train and evaluate.
SN89 InfiniteQuant changes market windows and reward accounting
SN89 InfiniteQuant’s October 10 source changes add daily and weekly Bitcoin Up/Down windows anchored at 5 PM New York, carry retained losses forward per entity before paying above a high-water mark, and size shorter markets using the preceding three hours of sealed ticks. Another change arms the V4 oracle record for markets starting at or after 17:00 UTC. These are substantive competition and accounting rules in published code, not independent confirmation of deployed enforcement or a promise of trading performance.
Specific changes to reward accounting and market construction matter to participants; deployment remains a separate check.
SN100 Cortex schedules HyperTrain mining for October 12
SN100 Cortex’s October 10 thread dates the HyperTrain challenge for Monday, October 12, with 70% of emissions allocated to collaborative AI training and mining intended to open the same day. The first project is OpenDecision, described as a Jev alternative, with model training from scratch and architecture experiments. Web, desktop and mobile access to open models is a later ambition. This is a specific upcoming challenge and allocation announcement, not mining already open today or an independently verified on-chain reward change.
A dated new training challenge and substantial planned allocation, with activation kept separate from announcement.
SN104 TAOstatus announces mainnet validation across two mechanisms
SN104 TAOstatus’s October 9 announcement says its validator is live on mainnet for LLM-key contribution and AI security audits. The first mechanism relays and evaluates contributed API keys; the second benchmarks autonomous agents before offering vulnerability reports for applications or repositories. The matching source change sets the default burn percentage from 95% to 100% during bootstrapping. An environment override remains possible, so a code default is not proof that every live emission was burned. The mainnet announcement advances yesterday’s unconfirmed launch target; independent full chain replay and customer adoption remain outside this check.
An original mainnet announcement supported by matching bootstrapping code; actual emission configuration and service uptake are separately qualified.
SN105 Beam adds room webhooks for agents and external applications
SN105 Beam announced room webhooks on October 10, giving external applications and agents a documented HTTP entry point into room workflows. Its documentation describes webhook members, requests and responses rather than requiring every integration to use the same agent framework. A separate demonstration shows Hermes and OpenClaw working with shared visual context. These are concrete integration surfaces beyond yesterday’s Hermes announcement; the demo does not independently establish enterprise customer adoption or universal interoperability.
A documented developer feature that makes the subnet service easier to integrate across applications and agent frameworks.
SN108 ChipForge fixes winner resets while burn concerns remain open
SN108 ChipForge published two October 10 validator fixes: reset a local winner when the server’s baseline epoch changes, and use the server’s exact score-to-beat while limiting restored-winner payments to unpaid hours before its reward end. Separately, SubnetRadar’s dated Discord brief attributes a 100% emission burn and validation overhaul to a team member following an exploited winner. The code changes are directly verified; the incident account and live burn percentage were not independently reconstructed from chain data. There is no verified all-clear or firm restoration date. At the 23:17 UTC alpha/TAO snapshot, the subnet was up 22.17% over 24 hours and 160.73% over seven days; those moves do not establish a cause or resolution.
Material validator fixes plus an unresolved reward incident deserve attention; code verification and secondary incident reporting remain clearly separated.
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.
