← All Subnet News

September 6, 2026 · Published daily

Subnet News — September 6, 2026

TAO pairs on Stonk lead at five stars, followed by Phylax’s deregistration and Gradients’ reward overhaul. Ditto’s profit buybacks, major competition changes and operating updates follow in today’s star-ranked edition. Researched through 10:44 AM ET.

Coverage window
Sep 5, 2026, 9:32 AM10:44 AM ET
Subnets in coverage roster
128
Subnets with updates
48
01

Biggest stories first

Today's ranked news

★★★★★ marks the day's most consequential news. Scores weigh the size of the announcement, evidence quality, ecosystem reach and relevant market reaction.

#01 · Ecosystemverified
★★★★★

TAO pairs arrive on Stonk, powered by Sunrise

Stonk announced that users can now launch coins paired with TAO, and Sunrise separately confirmed bringing TAO to Solana for the rollout. This gives TAO a role as the quote asset behind newly launched markets. Sammy highlighted Buttensor (BUTT) as an early example and argued that trading activity can draw liquidity into the TAO pair. His premium and price-impact explanation remains analysis, not proof that BUTT caused TAO’s market move. Subnet alpha-token pairs have not been confirmed.

Why 5 stars: A new use for TAO across Solana launch markets, confirmed by both Stonk and Sunrise, is a major ecosystem expansion.

#02 · SN76 · Subnet 76 (new registration)verified
★★★★★

Phylax deregisters; SN76 is now a new subnet registration

SubnetRadar records Phylax’s deregistration and reuse of the SN76 slot on September 6. The current chain-derived listing has a new registration with no project name and zero emissions in this snapshot. This is a material break in the old subnet’s history: the new slot’s price chart must not be read as a Phylax return. The current team-discussion brief also reports that a public archive of rounds, agents and attestations has been made available.

Why 5 stars: Deregistration and slot reuse fundamentally change what holders and miners are tracking; this deserves top placement regardless of price direction.

#03 · SN56 · Gradientsverified
★★★★★

Gradients merges a major reward rewrite: no emission burn or champion decay

Gradients merged a reward overhaul that normalizes tournament pools to 100%, removes the burn allocation and stops champion rewards decaying with time. Third place becomes payable where it can be identified, giving roughly 76/19/5 across the top three; ambiguous brackets retain an 80/20 split. Entry fees double to 0.7 TAO for text, 0.4 for image and 0.6 for environment tasks. The code is merged; network-wide activation was not separately verified.

Why 5 stars: Redistributing the reward pool and changing both payouts and entry costs is a major economic change for every competing miner.

#04 · SN79 · MVTRXdeveloping
★★★★

MVTRX promises a public roadmap as its token remains under pressure

MVTRX’s team says a roadmap spanning near-term work through 12 months is planned for next week, alongside landing-page and transparency updates. Version 0.6.1’s scoring change remains under testing rather than confirmed live. The latest rolling 24-hour α/TAO snapshot showed a 24.4% decline, making delivery and reward-policy clarity especially relevant.

Why 4 stars: A large market decline makes a new delivery roadmap and unresolved scoring decision particularly consequential; no cause for the decline is inferred.

-24.4% α/TAO 24H price action as of Sep 6, 2026, 10:43 AM ET

#05 · SN118 · Dittoverified
★★★★

Ditto commits half of profit to buybacks and announces 1,342+ app connections

Ditto says 50% of profit after operating costs goes to buyback-and-lock or buyback-and-burn. That is half of profit, not half of revenue; no executed buyback total was disclosed in the announcement. Its September 6 product update also reports 1,342+ app connections, including Google Workspace, Notion, Linear and Jira, plus an approval inbox and workflow recovery. The V2 waitlist remains open.

Why 4 stars: A stated link between customer profit and token buybacks, alongside a broad product update, is commercially significant.

#06 · SN124 · Swarmverified
★★★★

Swarm merges private model submissions with on-chain commitments

Swarm’s new submission command packages and checks a model, commits its hash on-chain, then uploads the archive to the backend. The documented private track keeps submissions private unless they take the crown, reducing exposure of unsuccessful attempts. The merged documentation also changes payout eligibility to depend on the retained archive. This confirms the code and documented workflow; a live submission was not exercised.

Why 4 stars: Submission privacy and commitment rules materially change competitive incentives and model protection.

#07 · SN2 · DSpersedeveloping
★★★★

DSperse pinpoints the disappearing-rewards bug; the patch is still open

Pull request 625 identifies missing delivered-work persistence as the trigger for zero miner weights after validator restarts. Its author reports 122 of 446 epochs with the full owner/burn weight and adds a persistence test. The proposal would preserve work history across restarts, but the pull request was still open and unmerged at the cutoff. The reported burn measurements have not been independently reproduced.

Why 4 stars: A specific explanation and proposed remedy for missing miner rewards is a major advance in an unresolved payout incident.

#08 · SN34 · BitMinddeveloping
★★★★

BitMind prepares v5 model resubmissions; launch activation remains unconfirmed

BitMind’s current discussion calls for model resubmissions with v5 and specifies A10G evaluation hardware with 24 GB VRAM. Sunday, September 6 remains the previously announced target, but activation was not confirmed. The public release listing still showed v4.9.8 at this check. A separate merged fix skips unregistered escrow UIDs when setting weights.

Why 4 stars: A required resubmission and competition reset affect the whole miner set; launch timing needs clear treatment.

#09 · SN68 · NOVAdeveloping
★★★★

NOVA plans Boltz-2 scoring and a new miner sandbox next week

NOVA Blueprint plans to move scoring to a separate Boltz-2 inference service, outside the miner sandbox. Miners will need updated code and initially receive one-hour run budgets; the first competition is planned as a single round with a capped bounty. Existing PSICHIC challenges are to finish under their current rules. An exact code-release time was not supplied.

Why 4 stars: A new scientific scoring model and execution architecture change how every miner builds and evaluates submissions.

#10 · SN71 · Leadpoetverified
★★★★

Leadpoet fixes Arena sandbox traversal and invalid baseline publication

Leadpoet merged safeguards for sandbox traversal and rejection of invalid baseline publication, followed by fixes for Arena round discovery across unrelated history. The changes address how submissions are executed, found and judged. Public commits establish the repairs in code; the broad claim that all validator reliability problems are resolved is not established.

Why 4 stars: Sandbox isolation and valid judging baselines are essential to a trustworthy model competition.

#11 · SN11 · TrajectoryRLdeveloping
★★★★

TrajectoryRL previews Model Fusion while web submissions are interrupted

TrajectoryRL’s team discussion describes Model Fusion: routing and combining models across subnets such as Engy and Chutes to balance cost and performance. The same brief reports web submissions disabled during a system upgrade and an HTTP 503 submission failure. The cross-subnet feature is an announcement, with general availability and submission recovery still unconfirmed.

Why 4 stars: Cross-subnet orchestration could expand the product’s utility, while interrupted submissions directly affect participants.

#12 · SN120 · Affinedeveloping
★★★★

Affine reports more than 50 models waiting as evaluation failures persist

Affine’s current discussion reports evaluation failures, incorrect queue ordering and more than 50 models awaiting processing. Missing results in dashboard history add uncertainty for participants. This is a continuation of the private-evaluation incident covered yesterday, with a clearer backlog estimate; a completed recovery was not confirmed.

Why 4 stars: A sizeable backlog and unreliable evaluation order can prevent miners from competing and receiving timely results.

#13 · SN3 · Teutonicdeveloping
★★★★★

Teutonic reports stronger base-model benchmark results

The team reports MMLU at 69%, GSM8K at 72.3%, PIQA at 82.9% and MATH-500 at 32.2% for its latest pretrained checkpoint. These are team-reported results from the current discussion, without an independent reproduction in this edition. The team’s own overall ratings are not treated as external benchmark scores.

Why 3 stars: Concrete benchmark measurements offer a useful progress marker for decentralized training.

#14 · SN5 · Honedeveloping
★★★★★

Hone shifts challenges toward practical software engineering

Hone’s team describes a move from competitive-programming problems toward SWE-bench and terminal-bench-style tasks involving larger codebases, multiple languages and practical engineering. Public examples and tests are available, while grading failures on six tasks remain a topic of discussion. The direction is announced; full rollout was not independently confirmed.

Why 3 stars: The challenge format determines which capabilities miners need to build and demonstrate.

#15 · SN7 · Allwaysdeveloping
★★★★★

Allways fixes collateral-based swap sizing and reports five completed TAO swaps

A new Allways commit sizes swaps against free collateral and exposes refused pool draws through its status endpoint. Separately, the project reports five completed swaps turning 9 TAO into 2,100.0672 Arbitrum USDC, with 0.09 TAO in protocol fees. Those activity figures are project-reported and were not reconciled against all transactions in this scan.

Why 3 stars: Collateral safeguards and specific completed-swap figures provide useful operating evidence for the cross-chain service.

#16 · SN10 · Paretondeveloping
★★★★★

Pareton says evaluations are active ahead of Monday adjustments

The team says evaluations are running, submissions remain open for future rounds and four miners are the minimum participation requirement. Further adjustments are planned for Monday, September 7. This provides a current operating update after the mechanism discussion covered yesterday; the proposed rules are not treated as already deployed.

Why 3 stars: Evaluation availability and participation requirements affect whether miners can compete.

#17 · SN21 · AdTAOverified
★★★★★

AdTAO makes paid rows and prediction accuracy easier to audit

AdTAO’s reporting changes show absolute accuracy alongside relative advantage and include every hotkey paid by the weight vector as a funded row. Another fix aligns displayed scored rows with published audit standings. These are specific improvements to payout visibility, rather than a new advertising customer or revenue announcement.

Why 3 stars: Participants gain a clearer way to reconcile model performance with the rewards they receive.

#18 · SN28 · SayGMdeveloping
★★★★★

SayGM refreshes chat controls and reports a miner-payment repair

SayGM reports a redesigned chat interface with reasoning-level visibility and an improved model selector. The team also says a payment-balancing bug has been repaired so epoch debts process normally again. A new savings tracker starts from fresh usage data; historical usage is not retrospectively filled in.

Why 3 stars: User controls and reliable miner settlement are practical improvements to a live inference service.

#19 · SN41 · Almanacdeveloping
★★★★★

Almanac restores registration sync after a temporary interruption

Almanac says its metagraph sync service is operating again after a disruption delayed miner registration and credits. The team is checking individual credit cases and reminding miners that their on-chain metadata must be set correctly for linking. A full independent reconciliation of delayed credits was not available.

Why 3 stars: Registration and credit processing directly affect access and participation.

#20 · SN44 · Scoredeveloping
★★★★★

Score miners report zero-score errors and labeling disputes

Score’s current discussion includes file-not-found errors, infrastructure temperature problems and disagreements about labeling and zero-score outcomes. The team says miners remain responsible for keeping their systems stable and has not confirmed a broad rollback. New dataset elements are planned, without a precise date. These operational reports are separate from the earlier Shell and Eni rollout story.

Why 3 stars: Scoring failures and disputed outcomes matter to current miners, even alongside positive commercial announcements.

#21 · SN47 · Fevaldeveloping
★★★★★

Feval says validators are running while emission activation awaits stake

Feval’s team reports operational validators but insufficient stake to trigger emission events. Its current discussion points participants to a results dashboard while reward timing remains unresolved. References to possible outside staking support do not confirm a partnership or committed allocation.

Why 3 stars: Working evaluations without confirmed emissions leave a material participation and reward question.

#22 · SN54 · Yanezverified
★★★★★

Yanez removes submitted values from SDK schema-error messages

Yanez’s agent-authorization SDK now keeps submitted values out of error messages when a request fails schema validation. Related changes update examples and the exported contract to a new terms format. This is a new privacy and integration repair; yesterday’s customer-and-partner disclosure remains in its original edition.

Why 3 stars: Reducing sensitive data exposure in errors is relevant to identity and authorization integrations.

#23 · SN61 · RedTeamdeveloping
★★★★★

RedTeam adds scoring-server storage; a zero-score bug remains known

RedTeam says extra storage resolved miner container-build failures and advises affected miners to resubmit with an updated hash. The discussion separately identifies a known validation-payload problem behind final-score discrepancies. The storage repair should not be read as confirmation that every scoring issue is fixed.

Why 3 stars: Build failures and incorrect final scores directly affect competition access and rewards.

#24 · SN62 · Ridgesdeveloping
★★★★★

Ridges previews a gRidges competition before month-end

AlphaGap’s current signed-in feed reports that the Ridges team plans a competition called gRidges before the end of September, with other updates expected sooner. This is a secondary-source roadmap lead; a primary launch notice and firm date were not located. The v0.3.0 multi-competition framework was already covered yesterday.

Why 3 stars: A named new competition is worth tracking, while its availability remains unconfirmed.

#25 · SN66 · conjecturesverified
★★★★★

Conjectures publishes three new formal-math contributions

The contribution repository adds artifacts targeting Erdős 357 variants, Erdős 889 and an Erdős 727 variant. These are submitted formal-math artifacts, not evidence that three open problems have been solved. The Erdős 357 contribution explicitly describes an elementary reduction and disclaims a full solution; this edition did not independently compile the proofs.

Why 3 stars: Inspectable mathematical work is meaningful output, provided the scope is kept separate from claims of solving open problems.

#26 · SN74 · Gittensorverified
★★★★★

Gittensor changes prompt-processing pay and removes a fixed prompt cap

Gittensor merged serving changes that pay for prompt processing alongside token generation and allow the prompt’s own processing time when calculating response-time credit. Another change uses the model context window instead of a fixed 40,000-character cap. These alter serving economics and which requests miners can handle.

Why 3 stars: Paying for the work of processing long prompts and using actual model limits materially improves the serving mechanism.

#27 · SN78 · Umiverified
★★★★★

UMI adds a public miner-endpoint pilot; translation rewards remain inactive

UMI adds a pilot to test a registered SN78 miner through its public HTTPS endpoint and publish signed, replayable evidence. It tests interoperability with a known clip, not benchmark quality or reward eligibility. The current README states that public calibration has not started and translation weights remain inactive; the pilot does not change those boundaries.

Why 3 stars: An externally reachable miner test is practical progress, with clear limits on what it proves.

#28 · SN81 · Reliquarydeveloping
★★★★★

Reliquary investigates delays that may distort throughput rankings

A miner reports precommit retries and delays affecting throughput rankings. The team identifies event-loop stalls of around 11 seconds correlated with proof bursts and requests logs to determine whether validator processing is contributing to penalties. A completed fix or confirmed network-wide impact was not available.

Why 3 stars: If infrastructure latency affects rankings, miners may be penalized for factors outside their submitted work.

#29 · SN85 · Vidaiodeveloping
★★★★★

Vidaio addresses miner certificate failures and explains compression scoring

Vidaio’s team is resolving TLS certificate problems affecting dispatch to miners and clarifies that compression quality is judged against pristine source references. It points operators to epoch logs, the metagraph and its miner dashboard for checks. A technical whitepaper is still forthcoming, rather than already published.

Why 3 stars: Dispatch availability and transparent reference scoring are important during the ongoing migration.

#30 · SN89 · InfiniteQuantverified
★★★★★

InfiniteQuant holds referral calls until their recorded close

A new InfiniteQuant change keeps a referral-pair call occupied until its journaled close rather than releasing it at the forecast horizon. This tightens the lifecycle of overlapping calls and the conditions under which a new one can enter.

Why 3 stars: Correct close handling matters to fair evaluation of financial calls.

#31 · SN90 · KubeTEEdeveloping
★★★★★

KubeTEE brings its SN28-to-SN90 recycling activity into public view

KubeTEE’s current discussion highlights a public recycling dashboard and reports roughly $10,000 recycled. Its own documentation confirms the mechanism has been live since August 23: alpha earned on SN28 is swapped into SN90 alpha and recycled to unissued supply. The documentation links a first on-chain fill. Today’s dashboard coverage is new to this edition; the mechanism itself is older, and the cumulative dollar total was not independently reconciled.

Why 3 stars: Inspectable cross-subnet recycling is useful economic evidence, with the age of the mechanism and limits of the reported total made clear.

#32 · SN92 · MicroTensorverified
★★★★★

MicroTensor excludes uncosted reports and preserves sealed submissions at freeze

MicroTensor now treats a report with zero expected cost as unscored rather than as a valid measurement. A coordinator change also records submission pointers seen during the window and restores the sealed pointer at freeze if a reveal replaced it. These are new scoring and commitment repairs, distinct from yesterday’s classification-track rollout.

Why 3 stars: Valid cost measurements and sealed submissions are central to fair competition outcomes.

#33 · SN95 · Actualverified
★★★★★

Actual Computer sponsors localmaxxing

The event organizer announced Actual Computer as a localmaxxing sponsor, and founder Tom Lynch separately confirmed it. Both describe a shared interest in local computing, privacy and engineering. No sponsorship value, customer contract or revenue figure was disclosed.

Why 3 stars: Confirmation from both sides establishes a concrete ecosystem relationship for Actual.

#34 · SN100 · Cortexdeveloping
★★★★★

Cortex updates its CLI while gateway and account-linking issues remain

Cortex merged its updated terminal-interface layout and model-effort controls. Separately, the current team brief records unresolved gateway resolution, account-ID visibility and bounty account-linking issues. The CLI code update does not establish that the affected app flows are fully working.

Why 3 stars: A product update and unresolved access problems both matter to users trying to participate.

#35 · SN103 · Capcompverified
★★★★★

Capcomp prevents one run from overwriting another sealed commitment

Capcomp added a guard that refuses a commitment if it would destroy a sealed commitment belonging to a different run. This is a targeted integrity repair to the commitment workflow, following yesterday’s report on sealed mining recipes.

Why 3 stars: Preserving earlier commitments protects the evidence used to judge mining results.

#36 · SN106 · Nodexodeveloping
★★★★★

Nodexo reports 82 scoring GPU executors; workstation support is still pending

The team reports 82 live executors, all scoring, and 55 free GPUs across tiers. It describes a registry-refresh delay behind temporary errors for new executor IDs. RTX PRO 6000 Workstation Edition support still requires calibration and pricing entries; it is not enabled simply because the Server Edition is supported. Counts are a team-reported snapshot.

Why 3 stars: Capacity and exact hardware eligibility are practical information for customers and GPU operators.

#37 · SN107 · Minosdeveloping
★★★★★

Minos says its emissions restart still awaits approval

Minos’s current discussion says implementation is complete but emission reactivation still awaits approval. The team also clarifies that ground-truth data becomes available after rounds finish. This is a follow-up to yesterday’s unresolved restart, not confirmation that rewards have resumed.

Why 3 stars: The distinction between completed software and approved emissions is material to miner participation.

#38 · SN113 · TensorUSDverified
★★★★★

TensorUSD explains alpha-holder governance and stress controls

TensorUSD says SN113 alpha holders vote on protocol parameters, while TUSDT holders can propose changes. Its current posts describe a 150% collateral requirement and controls to pause minting, tighten liquidation parameters or limit redemptions while auctions clear. These are the project’s stated mechanics, not an independent solvency audit or a guarantee of peg stability.

Why 3 stars: Governance rights and redemption constraints are important facts for understanding the protocol.

#39 · SN114 · SOMAdeveloping
★★★★★

SOMA reports competition 145 results and plans new task groupings

SOMA’s current discussion reports competition 145 results and a prompting-rule disqualification. Future rounds are to replace explore/edit layers with complexity-based task groups. A precise activation time for the new task format was not confirmed.

Why 3 stars: Results and task-design changes affect how miners prepare and how submissions are judged.

#40 · SN119 · Satorideveloping
★★★★★

Satori outlines CapabilityForge Next for local learning

The current SN119 discussion introduces CapabilityForge Next as an open-source learning platform focused first on mathematics and natural sciences, with local and offline use. It describes Gemma 4 12B as the foundation model and language expansion and classroom features as roadmap work. A primary release artifact matching this announcement was not located, so launch availability remains developing.

Why 3 stars: An education-focused product direction is a material project update, with release details still needing primary confirmation.

#41 · SN127 · Astriddeveloping
★★★★★

Astrid participants await MS5 results as MS6 trading remains uneven

Astrid’s current discussion reports MS5 results still unannounced more than 12 days after completion and six inactive agents in MS6. The team says strategies can require particular market conditions before trading. That explains a possible reason for inactivity but does not resolve the delayed results.

Why 3 stars: Delayed results and uneven participation matter to the credibility and progress of the trading competition.

#42 · SN9 · iotadeveloping
★★★★★

Iota investigates a miner stuck near the front of its registration queue

A CUDA miner reportedly remained at queue position three for around ten hours without a layer assignment. The team is investigating registration-capacity and attestation questions; compatibility of the reported Blackwell GPU remains unclear. The discussion also says TAH currently supports Apple Silicon, with CLI support in development. This is a reported operator case, not a confirmed network-wide outage.

Why 2 stars: An unresolved onboarding case is relevant to miners using the affected path, but its wider scope is unknown.

#43 · SN25 · URverified
★★★★★

UR integrates compact statistics and joint measurement replay

UR’s latest commit integrates qualified compact-statistics work and joint measurement replay after a series of development checkpoints. The public artifact records engineering progress in the measurement pipeline. It does not establish a new generally available product release or external deployment.

Why 2 stars: The integration is a concrete development milestone, with commercial and deployment significance still limited.

#44 · SN46 · Instantdeveloping
★★★★★

Instant targets next week for launch, with timing still tentative

The SN46 team is aiming for a launch next week and says it is supporting Zipcode and Instant integrations. It has not supplied a firm launch date. This remains a roadmap update rather than a completed release.

Why 2 stars: The target window is useful to follow, but the announcement remains tentative.

#45 · SN51 · lium.iodeveloping
★★★★★

Lium reports an operational Singapore node

A team member confirms an operational node in Singapore in the current SN51 discussion. A separate inquiry about an eight-B300 NVLink server was redirected to private discussion, so no additional hardware availability or capacity is inferred from that inquiry.

Why 2 stars: An APAC location update is useful operating information, with no verified new fleet-size claim.

#46 · SN80 · OpenRobotodeveloping
★★★★★

OpenRoboto reports evaluations running again

The team says evaluations resumed after a temporary interruption. The reviewed discussion does not establish a permanent infrastructure redesign or new reward policy; this is an availability update for participants waiting on evaluations.

Why 2 stars: Restored evaluations matter to active miners, while the reported interruption was limited.

#47 · SN91 · cascadeverified
★★★★★

Cascade makes worker-lane identity stable across provisioning changes

Cascade’s provisioner now derives stable lane names from pod identity and adds boundary checks. The merged change addresses worker identification and coordination. It does not verify a new synthetic-data benchmark result or an external commercial deployment.

Why 2 stars: Stable worker identity is a concrete reliability improvement to the training infrastructure.

#48 · SN111 · Claimsdeveloping
★★★★★

Claims investigates blocked artifact uploads and missing tasks

The Claims discussion reports an HTTP 403 blocking a miner’s artifact upload and another operator receiving no tasks after an hour. The team is checking key ownership and the affected upload path. The reviewed evidence supports specific unresolved cases, rather than a confirmed outage for all miners.

Why 2 stars: Upload and allocation problems can prevent participation, but their broader scope remains unknown.

#49 · SN115 · MoirAIdeveloping
★★★★★

MoirAI separates the current project from prior-owner assets

The SN115 team says the current MoirAI project has no connection to the previous owner’s alpha sale and assets. This is an attribution clarification from the team discussion; it does not establish wrongdoing by either party or resolve every historical ownership question.

Why 2 stars: A clear distinction between current and prior operators helps readers interpret subnet history.

04

Audit trail

Coverage notes

Searched

  • All 128 active subnet slots and SubnetRadar profiles; current identities checked, including SN76 deregistration and reuse.
  • 100 dated September 5–6 SubnetRadar briefs, including the ecosystem channel; relative dates checked against source-message timestamps where material.
  • 150 repository paths checked through 10:44 AM ET, with paginated commit retrieval; 145 accessible. Includes legacy mappings, two additional research candidates and core Subtensor.
  • 128 indexed X queries by current name, SN number and available account aliases; 66 public account pages read and refreshed, yielding 76 unique current original posts across the feed and account samples.
  • Signed-in AlphaGap feed reviewed for development, social and market leads; original code and posts used to correct stale or contradictory summaries.
  • TAO Daily, TAO Media, public news feeds and outside partner searches; Stonk and Sunrise confirmations, both user-supplied X links, Ditto announcements, Actual sponsor confirmation and selected primary repositories.
  • Shizzy Unchained YouTube Videos and Live tabs checked and refreshed. Latest upload and stream IDs, titles and durations still match the site; no newer item found.
  • Chain-derived rolling 24-hour α/TAO market snapshot checked. Price is context for material news, not the sole reason for its rating. Coverage ends 10:44 AM ET.

Public-data gaps

  • Authenticated X search redirected to login; Grok and complete signed-in timelines were unavailable. Public account pages expose limited recent samples, and indexed queries did not surface relevant current posts. This is not exhaustive X coverage.
  • Private Discord history was not opened. Dated AI-generated briefs are secondary sources; uncorroborated operating reports, counts and roadmap claims remain developing. AlphaGap’s feed covers 48 hours and can repeat earlier news or misstate units and rollout status.
  • Stonk and Sunrise confirm the announcement, but the launch page returned empty quote-token categories in this browser session. No wallet was connected or launch transaction tested. Sammy’s liquidity thesis and rumored subnet-alpha pairs are not verified outcomes.
  • Phylax deregistration is recorded by SubnetRadar and the current slot identity has reset. The claimed MicroTensor continuation was not independently corroborated. The new SN76 pool’s apparent 24-hour price change is excluded as a misleading comparison across registrations.
  • Five mapped repository paths returned 404: deprecated/deprecated, actual-computer/actual-subnet-95, Satori119/Satori, NIOME-BITTENSOR/NIOME and Oh-My-Ditto/ditto. Alternate candidates were checked where available; capabilityforge/cf-subnet was not confirmed as the new SN119 learning platform.
  • TAO.com’s current fee-clarification post was found, but its linked X article was unavailable. No fee numbers were invented. KubeTEE’s cumulative recycling dollar total was not independently reconciled.
  • Earlier announcements are not republished as fresh launches. No independently verified forward alpha-unlock calendar was available. Later announcements belong to the next coverage window.