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.
SN53 Engy confirms Antseed access and fixes request bodies leaking into miner logs
SN53 Engy confirmed on October 13 that it serves models through Antseed, whose new Gateway Console lets teams select models, manage access and track budgets. Separately, merged SN53 Engy miner code addresses an error path that could write a buyer’s request body into logs when malformed Unicode triggered an encoding failure. The patch sanitizes logged errors and handles that input. Distribution is useful, but the privacy correction is equally material: protected hardware alone does not prevent application logs from exposing prompts. The code fix is verified; deployment across every miner and deletion of previously written logs are not.
Both sides acknowledge a distribution channel, and public code documents a concrete prompt-logging privacy failure and repair.
SN61 RedTeam 4.10.10 adjusts challenge incentives and submission limits
SN61 RedTeam’s October 13 changelog for 4.10.10 names incentive-weight and maximum-unique-commit changes for its bex_tracer_v1 and ada_detection_v3 challenges. It also simplifies container resource/security options. These are verified release-code changes affecting competition configuration; they do not establish that every validator upgraded or resolve each unanswered scoring-server complaint in the channel.
Challenge incentive and unique-submission limits directly affect miner participation.
SN71 Leadpoet preserves results while making unfinished judging recoverable
SN71 Leadpoet merged judge-continuation and retry-safety changes on October 13, with the stated constraint that existing October 13 results must not change. Its dashboard also distinguishes scored rounds from pending final results. The point is preventing interrupted provider calls or incomplete judging from looking like a final outcome. These are verified implementation changes; they do not independently establish that every stalled round is resolved or announce another investment round.
Recoverable judging and clearer finality address fairness and reliability in an active competition.
SN74 Gittensor’s merged policy recycles the miner pool while its repository registry is empty
SN74 Gittensor’s October 12 merge sets the open-source pool share to 100%, leaving the compute pool at zero. Its accompanying comment explains that with an empty repository registry the miner emissions recycle to UID 0. This is a material change from the previously documented 70/30 open-source/compute split, and more consequential for miners than simply announcing another interface improvement. The configuration is verified in public code; the exact subsequent finalized weight and payment totals were not independently reconstructed.
A verified reward-allocation change can remove the compute pool and redirect the full miner allocation under the documented empty-registry condition.
SN75 Hippius launches encrypted screen recording in Drive
SN75 Hippius’ October 13 product post and published guide confirm screen recording in its web console and desktop app for Mac, Windows and Linux. Users can capture a screen, microphone and system audio in up to 4K; the team says files are encrypted on the device before going to Drive. The practical change is turning decentralized storage into an everyday capture-and-share workflow. These are documented product capabilities, not an independent security audit or a guarantee that everything shown on a recording is safe to share.
A released, documented user feature gives the storage product a concrete new everyday workflow.
SN80 OpenRoboto announces four Solana Accelerate appearances
SN80 OpenRoboto says it will present at Solana Accelerate in Shanghai on October 16, Hangzhou on October 18, Shenzhen on October 20 and Beijing on October 22. Its announced topic is an incentive computer for robotics data collection and models. The schedule is a distribution and developer-outreach opportunity; a planned talk or reference to partnership progress does not establish a newly executed commercial contract. These are upcoming appearances, not events already completed.
A dated official schedule creates specific upcoming opportunities to hear the team’s robotics progress.
SN81 Reliquary separates benchmark tickets from telecom training
SN81 Reliquary’s new telecom-solo v2 split explicitly holds out the 134 tickets used for the upstream telecom benchmark. The commit explains that the prior split placed 114 of those benchmark tickets in training. The tasks and grading stay the same while the split changes, making the distinction between training and benchmark evaluation clearer. This is a reproducibility and leakage-control improvement, not a newly demonstrated model score or a guarantee that every possible form of contamination is eliminated.
A concrete benchmark-overlap correction makes future evaluation easier to interpret.
SN89 InfiniteQuant schedules a larger Markets share for October 14
SN89 InfiniteQuant’s October 13 code and documentation schedule a new split from October 14 at 00:00 UTC: Markets receives 20% of the total miner allocation, with low-frequency and high-frequency tracks at 30% each and the separate referrer mechanism’s 20% unchanged. Markets therefore doubles from its prior 10%, taking five percentage points from each frequency track. The change is paired with vault accounting that protects open bets’ maximum payouts. This is a dated future rule, not proof it has activated already or that outstanding claims have all been paid.
A specific scheduled reward reallocation and payout-reserve rule matter directly to participants.
SN91 Cascade offers Ephemeris forecasting through MCP
SN91 Cascade’s October 13 announcement makes Ephemeris time-series inference available to agents through an MCP connection and OAuth sign-in, naming compatible agent clients in its post. This follows earlier forecasting benchmarks but adds a different kind of progress: a route for an agent to actually call the service inside its workflow. The announcement does not prove that every client or dataset will work without setup, and it does not establish a fresh accuracy record.
A new agent-facing access path makes existing forecasting capabilities easier to integrate.
SN93 Bitcast reports repeat-customer revenue and renews its buyback deadline
SN93 Bitcast’s October 13 post says more than 60% of revenue comes from returning customers. Repeat business is a useful signal for a subnet selling creator distribution: it suggests buyers come back rather than every campaign requiring a new customer. The percentage is the team’s own disclosure, without a reporting-period breakdown or independently audited customer ledger in the post. It should not be converted into a new total revenue figure or a guaranteed future buyback. Separately, CEO Tom B says the remaining $78,000 of the previously announced $93,000 buyback commitment will be purchased over the next seven days. That is a renewed execution plan, not another completed $78,000 burn; no new execution transactions were verified here.
A new customer-retention disclosure adds commercial context beyond campaign counts.
SN96 Verathos digest reports scoring disruption and ongoing correction
The October 13 SN96 Verathos channel digest attributes intermittent connectivity and legacy scoring problems to a Hetzner Finland outage. It says scoring corrections and monitoring are ongoing and the Decide testnet was unaffected. This is a developing service incident, not an independently reconstructed missed-emission total or a blanket all-clear. The October 15 Decide transition is still a separate planned event; a testnet being unaffected does not establish successful production migration.
An attributed operational disruption can affect miners now and needs follow-up rather than an assumed recovery.
SN105 Beam changes PRISM duel scoring and reports sell-allowance fields
SN105 Beam’s public code changes PRISM duel stakes and failed-recovery treatment, followed by a correction that draws close speed duels and only zeros clear deficits. Its October 13 digest says the scoring update went live October 12 and describes new safe-to-sell and next-penalty-free fields in the allowance API. The code changes are verifiable; current fleet activation and the API response were not independently exercised. This updates incentive behavior without declaring all earlier security and task-volume concerns resolved.
Specific reliability-oriented scoring changes affect competition outcomes and miner selling decisions.
SN109 Finsight digest reports a handover; the recorded chain owner is unchanged
SN109 Finsight’s October 13 digest attributes a completed transfer of responsibilities and revoked access to the former team, with the original project intending to return on a newly registered subnet when ready. Direct finalized node comparisons from block 9268161 to 9275607 show no change to SN109’s owner key or registration height. Those observations can coexist: an operational or account handover does not necessarily require a new chain key. Buyer identity, sale price and a separately decoded new on-chain transfer remain unverified. The reported handover advances the earlier sale discussion but is not described as a new registration.
A reported business handover updates an open sale story, with direct chain state preventing an unsupported execution claim.
SN114 SOMA reports a context-compression gain with a controlled methodology
SN114 SOMA’s October 13 thread claims 30% more effective compute from its context compressor, measured with the task, model, provider, environment and generation settings held constant. Its published methodology compares reference and transformed context, uses weighted token costs, checks quality first and distinguishes invalid runs from results. That is a more useful basis than comparing unrelated runs, but the headline remains the team’s claim; it is not an independent replication or a general 30% hardware-speed increase on every workload.
A specific efficiency claim comes with a published method and meaningful controls, while generalization remains limited.
SN117 Everyframe adds image, audio and reference-aware worker contracts
SN117 Everyframe’s v0.4.0 miner code adds H3 reference handling and Studio image/audio contracts, following flexible video workers in v0.3.9. The documentation requires a compatible worker update, credentials, fresh attestation, available capacity and explicit offers; updating the CLI alone does not update a running worker. Existing offers do not automatically authorize the new jobs. This expands what miners can serve, but the registry is not a promise that every model is enabled or that all app traffic routes through miners.
Published worker support expands the task catalogue with explicit operational and pricing gates.
SN118 Ditto completes its first business-client onboarding
SN118 Ditto’s October 12 post says the onboarding call with its first business client is complete and the custom build is starting. This advances the October 9 client announcement from agreement toward delivery; it is not a second customer or a completed three-month build. The team’s channel digest separately reports a 0.05 TAO submission fee and a forthcoming reranker competition. Those operational details remain attributed to the digest until their original configuration and activation are independently checked.
A confirmed delivery-stage milestone updates an existing customer story without double-counting the client.
SN120 Affine records two MiMo updates and exposes answer-format sensitivity
SN120 Affine’s October 13 public research records two completed MiMo updates, while its matched evaluation shows why a headline score needs context. The official first-update result moves from 18/32 to 19/32; applying the same narrow answer-format diagnostic to both checkpoints gives 22/32 for each. The team explicitly does not claim convergence or sustained learning improvement. Prospective parser and runtime corrections remain separate from the frozen advertised worker archive. The useful advance is auditable training evidence and a documented grading sensitivity, not proof of a breakthrough from one small evaluation.
Public matched evidence distinguishes actual training progress from fragile grading-dependent performance claims.
SN126 Attelier requests additional MiniMax licensing permission
SN126 Attelier’s October 13 post says it has requested MiniMax’s permission to offer optimized H3 in markets outside the current license’s coverage. The team wants to reduce generation time and cost while bringing the work to its API. This is a useful disclosure of a release dependency: a permission request is not approval, and the post does not establish availability in those markets or a completed quality-preserving speed benchmark.
An explicit licensing dependency helps distinguish an intended expansion from an available product.
taostats launches its refreshed toolkit and a $9 Power plan
taostats’ October 13 launch brings a refreshed explorer, upgraded app and wallet, rebuilt API and a Power subscription together across devices. Its October 12 pricing post lists $9 per month for features including 24 months of tax data, grouped accounts, batch transfers and more API access. This is broader than yesterday’s API migration story: it changes the tools and access tiers available to everyday Bittensor users. The existing migration deadline remains a separate developer obligation; subscribing does not remove the need to update old endpoint integrations.
A live ecosystem-wide product refresh and new access tier affect wallets, research and developer workflows.
Subtensor merges Release 478 with staking-accounting repairs
Subtensor merged Release 478 on October 13. The changes include bounded restoration of missing staking-hotkey associations and stake-exit charging sized to the caller’s actual hotkey list in EVM and contract paths. These are concrete staking-accounting and execution-cost repairs rather than a generic version bump. The merge is verified in the protocol repository; a separate finalized-node runtime query in this pass still reports spec 477, so Release 478 is not presented as activated.
Protocol staking consistency and contract-execution charging affect infrastructure users; activation remains a separate fact.
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.
