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.
SN62 Ridges reports recovery after maintenance-related evaluation pause
The October 25 team-attributed digest says evaluations paused during a short outage for a security update and scheduled maintenance, and that service subsequently returned. It does not establish a security breach, loss of funds or repair of every affected job. The item closes the operational loop while keeping the scope of the recovery claim explicit.
Service availability matters to participants; the evidence supports an attributed maintenance/recovery report, not a breach claim.
SN70’s prior identity is cleared; a new unnamed registration follows
Finalization of block 9,364,302 on October 26 at 00:40:12 UTC removes the former Consted 2.0 identity and clears its registration/owner storage. Block 9,364,303, twelve seconds later, records NetworkAdded for SN70 with a new registration height and a different owner. The new registration has no on-chain project name at our finalized cutoff, so its current label is Unknown. Its allocation is the default 18% owner / 41% validators / 41% miners. The earlier 33% / 33% / 34% vector was reset during lifecycle cleanup, not by a newly observed owner allocation transaction. This does not establish a subnet sale, purchase price or continuity with the old project. Historical Consted coverage stays labelled with its recorded identity.
Verified slot reuse changes which owner and project the current subnet data describes; a new name or sale is not inferred.
SN71 Leadpoet reward-rule dispute continues as arena fixes land
The October 25 digest reports a miner dispute over when stricter improvement thresholds were applied, and says the team declined retrospective changes. We have not independently verified the claimed lost reward. Separately, public code allows miner execution alongside baseline judging and adds recovery for stopped scoring jobs with bound provider failures. The commits establish implementation changes, not resolution of the disputed payout or proof that all live rounds have recovered.
Miner-facing reliability fixes and an unresolved rule dispute deserve a concise update without treating allegations as settled facts.
SN76 Ormas raises its validator emission allocation to 49%
A successful finalized transaction at block 9,361,535 on October 25 at 15:26:48 UTC changes the alpha split from 18% owner / 41% validators / 41% miners to 18% / 49% / 33%. The burn and recycle slots remain zero. This reallocates eight percentage points from miners to the validator bucket; it is not a transaction burn. Root receives its live baseline first, capped by the validator allocation, and alpha validators share the remainder. Individual returns still depend on stake, performance and take; historical yield can lag the change.
A chain-verified allocation change directly affects the reward buckets without guaranteeing an individual yield.
SN78 Umi keeps C5 rewards active while C6 evaluation continues
The October 25 team-attributed digest reports 32 of 103 C6 models fully evaluated and a provisional completion target around 15:00 UTC. C5 remains the active reward cohort until final scoring and weight activation. New public code also schedules resident models against physical GPU capacity and preserves progress on longer cases. A target finish time is not evidence that C6 weights are active.
The active reward cohort is the useful distinction for miners; progress figures remain team-reported.
SN81 Reliquary removes its default minimum incentive-share cutoff
A new primary commit removes the default rule that reduced a hotkey’s task share below 2% to zero. The protocol default is now zero, allowing smaller verified contributions to receive a share; an individual task can still declare its own floor. Related code fixes optimizer setup so sharded training parameters, rather than transient unsharded buffers, receive updates. These are verified repository changes; we have not independently confirmed rollout on every running worker or validator.
The default payout rule directly affects smaller GPU contributors, and the training fix addresses whether model weights are actually updated.
SN91 Cascade user describes research integration and one live deployment
On October 25, @Tensor_Flow_ said its engineering stack uses Cascade’s synthetic time-series generator alongside the Alphacast forecasting feed, describing research-stage work and one live deployment. This is a direct user statement about use, rather than another model-size announcement. The user did not disclose a customer, revenue or independently measured production performance, so none is inferred. Bitstarter separately highlighted the statement.
A named public user describes actual integration, while commercial scale and effectiveness remain unverified.
SN118 Ditto tightens resubmission review; a new track remains in testing
The October 25 v0.387.0 release adds review of same-hotkey submissions against their earlier lineage; v0.387.1 preserves the managed Gamma guard across configuration converges. Separately, the team-attributed digest describes a new competition track running in shadow mode, awaiting scoring verification. Published code is distinct from reward activation: the additional track is not reported as live.
Concrete release changes affect submission checks, while the planned track still has an activation gate.
Grayscale files amended TAO ETF application; NYSE Arca trading remains conditional
Grayscale Bittensor Trust filed Amendment No. 2 to its S-1 on October 23, reviewed here as a late-found filing. The preliminary prospectus describes an intended NYSE Arca listing under GTAO and a planned rename to Grayscale Bittensor ETF. It explicitly says trading cannot begin until applicable listing requirements are met, and the registration statement must become effective. The trust’s existing OTCQX quotation is different from that proposed exchange listing. This is progress in the application process, not confirmation of ETF approval, a launch date or new inflows.
A primary regulatory filing materially advances the documented route to exchange-traded TAO exposure, with approval and trading conditions still outstanding.
Crucible announces desktop-feature parity on mobile and wider iOS access
In an October 23 announcement found during the overlap review, Crucible says its iOS and Android apps now include Smart Account, Rewards Allocator, Token Discovery, Token Details and Address Book, matching its Chrome feature set. It also names Argentina, Japan and Brazil in the iOS expansion. These are the developer’s release claims; we did not independently install each regional build or audit wallet permissions.
The announced mobile capabilities and regional availability are useful changes for TAO wallet users, while security and installation claims are not independently tested.
Latest Shizzy members update is available; next interviews remain scheduled
The 14:54 members-only October 24 news and TAO price-action video is now the site’s latest members entry. The public default remains a completed episode. YouTube still lists SN54 Yanez for October 27 at 12:30 PM ET, SN71 Leadpoet for October 28 at 11:00 AM ET, and TAO Templar for October 29 at 1:00 PM ET. They remain upcoming livestreams, not completed videos.
Current access labels and verified stream times help viewers find the right episode without implying an upcoming show has already aired.
SN6 Numinous reports lagging legacy validator queries
The October 24 digest says a team member confirmed that an old OpenRouter validator is lagging and advised deactivating its associated keys. It also says the current submission round is open. A separate member report that few forecasts were judged is not a verified network-wide outage. This is an operator follow-up to yesterday’s DKG release coverage; a complete recovery has not been independently confirmed.
A specific unresolved service issue, attributed to the team digest rather than inflated into a launch.
SN8 Vanta records two separate qualifying alpha burns
On October 24, successful transactions at blocks 9,353,782 and 9,354,416 emitted SN8 AlphaBurned events for 166.666666666 and 340.896934076 alpha respectively. Each event independently exceeds the 100-token minimum; smaller transactions were not added together to qualify. No matching buyback markers were established for these two events. Their block hashes, UTC times and event indices are retained in the Burns archive. A burn does not establish a price effect or business revenue.
Two new qualifying transactions, verified separately and kept distinct from prior coverage.
SN14 Cacheon records a new 1,933.73-alpha burn
A successful transaction at block 9,348,391 on October 23 emitted a SN14 AlphaBurned event for 1,933.73 native alpha. This is a new individual burn above the 100-token reporting threshold, separate from yesterday’s 2,870.53-alpha item. No matching buyback marker was established for this event, so we do not infer the acquisition source, revenue or a buyback program. Automatic miner-emission withholding and ordinary transaction fees remain outside the Burns archive.
An individually verified non-miner burn with transaction evidence, not a supply-counter inference.
SN22 Desearch merges page extraction V2; miners face an October 26 cutover
The October 23 merge introduces extraction V2 with page-type classification and separate main-text/full-text handling, supported by extraction-version tests. The October 24 team-attributed digest says validators accept V1 and V2 until October 26 at 11:00 UTC, then require V2. It also reports the miner-emission burn allocation falling from 50% to 30%: a 20-percentage-point shift, not a verified 20% increase in a miner’s realized earnings. The code is directly inspectable; the live acceptance deadline and allocation description retain digest attribution. Cleaner structured web text is the product change; the allocation is not a transaction burn.
A substantive extraction capability backed by code, with the separate operating deadline and allocation claims qualified.
SN28 SayGM miners told to redeploy v0.5.11 before October 26
The public gm-miner repository has a v0.5.11 release. The October 24 digest attributes a mandatory redeployment deadline of October 26 at 11:30 UTC to the team, after which older versions stop receiving traffic. It describes removal of affected eMudhra certificate roots, retries for dropped Azure verification connections, and gmcli deadline/worker notifications. Operators should use the project’s release and instructions rather than an unverified community image. Release availability is confirmed; the service cutover and root-removal details are team-reported through the digest, not an independent security audit.
A time-sensitive miner upgrade and trust-store maintenance requirement with source limits explicit.
SN34 BitMind’s Yugos migration stalls evaluations; submissions temporarily paused
The October 24 digest attributes stalled evaluation runs to a database refactor during SN34 BitMind’s migration to Yugos. It says the team paused new submissions, intended to finish existing runs and migrate the database before reopening. We inspected the Yugos product site: it advertises one model name and an API that routes among model providers, with per-request model/cost visibility. That confirms the current product description, not the number of active customers or a resolution of the submission problem. No verified reopening time was found. The older deepfake-detection description is being replaced in our sector guide while the canonical subnet label remains SN34 BitMind.
A material operating interruption and product-direction correction, without claiming the incident is resolved.
SN54 Yanez joins Shizzy on October 27
YouTube lists “Can You Prove You’re Human? Yanez Bittensor Subnet 54 with Jose Caldera” for October 27 at 12:30 PM Eastern / 9:30 AM Pacific. The watch-page start timestamp was checked directly. This is an upcoming interview, not a completed discussion or a new product launch. The video library and next-stream promotion now point to the scheduled episode.
A verified upcoming original Shizzy interview; video coverage uses the three-star rule.
SN62 Ridges reports a temporary evaluation pause
Following yesterday’s slow-validation notice, the October 24 digest attributes a temporary evaluation pause and an expectation of resuming soon to the team. The public repository also merges disk-management and gated Docker-start changes. Those commits do not by themselves prove that evaluation service has resumed, or establish the pause’s cause. We found no independently verified reopening time at the research cutoff.
A useful incident follow-up that keeps the repair code and actual service recovery distinct.
SN66 Conjectures adds 16 historical open problems to its task pool
An October 23 public merge adds 16 full historical open problems and updates the task catalog and admission records. These are new problem statements for the network to work on, not 16 newly solved conjectures. The distinction matters after yesterday’s coverage of an older Lean verification record. The release makes the new targets inspectable, but no claim is made that every statement is solvable or that miners have already produced proofs.
A verifiable problem-pool expansion; competition supply does not by itself earn a research-breakthrough rating.
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.
