Bittensor Toolkit →Find the right tool for your question.

BITTENSOR · THE NEWS ARCHIVE

Find the story.

Search 88 dated editions without scrolling through them one by one.

Reset filters

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.

2,373 matching stories

2026-10-07 edition →Ecosystemdeveloping4 / 5 stars

Subtensor’s pool-lending proposal changes its reserve design; the PR remains open

Subtensor PR3211 has been revised to move otherwise unreachable reserve floors into funded lending vaults while preserving the pool’s opening-price behavior and local price sensitivity. The latest design defers the previously discussed 1% minimum for the 500 TAO calibration; that earlier figure should not be presented as settled policy. The proposal describes 25% loan-to-value, weekly collateral collection, interest equivalent to 100% nominal annual interest on opening collateral value, and an aggregate asset cap. Avoiding price-triggered liquidation does not remove collateral-exhaustion or credit risk. This remains an open pull request, not an activated mainnet lending service, and the branch does not independently establish a runtime upgrade.

A substantial core lending proposal has changed in ways that affect pool mechanics and borrower risk, making the revised design and unactivated status material.

2026-10-07 edition →Ecosystemverified3 / 5 stars

Taoswap announces a rebuilt subnet trading and portfolio interface

Taoswap says its rebuilt interface brings subnet discovery, swaps, portfolio views and validator allocation into one experience. The public site was available at this check. The announcement is directly relevant to using TAO and subnet alpha, rather than unrelated crypto-platform activity. No swap was submitted during research, and a redesigned interface is not an independent smart-contract audit, verified improvement in execution price or evidence of newly generated trading revenue.

Taoswap announces a concrete user-facing Bittensor product refresh, with availability and transaction verification distinguished.

2026-10-07 edition →Ecosystemdeveloping3 / 5 stars

Yuma reports September subnet-fund performance in dollars

Yuma reports its composite gaining 26.9% in USD during September, compared with 30.9% for TAO, and 52.5% during the third quarter compared with 48% for TAO. Its large-cap product reports 29.0% for September and 64.6% for the quarter. The monthly and quarterly comparisons tell different stories and should not be blended into an unqualified outperformance claim. These are manager-reported fund measurements, not returns earned by every subnet holder, an independently reproduced portfolio history or a guarantee of future performance.

A major Bittensor fund manager supplies a new dated performance report with a clear USD benchmark and mixed comparison periods.

2026-10-07 edition →Ecosystemdeveloping3 / 5 stars

TAO.com reports $3 million in cumulative swap volume

TAO.com reports reaching $3 million in cumulative swap volume through its dTAO-to-USDC route. That is a usage milestone for an interface connecting subnet exposure and stablecoin liquidity. It is not $3 million in daily revenue, a single fresh TAO purchase or independently audited net demand; volume can include activity in both directions. The figure is attributed to the project rather than inferred from token price.

TAO.com reports a material product-usage milestone directly involving Bittensor swaps, with cumulative volume distinguished from revenue and net buying.

2026-10-07 edition →Ecosystemverified2 / 5 stars

Today with Shizzy: SN91 Cascade at 11 AM Eastern, plus the latest members update

Today’s SN91 Cascade conversation with Chris Hames and Chris Zacharia is scheduled for October 7 at 11 AM Eastern / 8 AM Pacific. It covers forecasting models, synthetic data, real-world evaluation and the products built around SN91 Cascade. The schedule is an upcoming broadcast, not a claim that it is already live. The October 6 members news video is now listed at 5:29 through YouTube membership access, and yesterday’s Subnet Summer/Medulla Labs validator conversation is available as a 49:17 public replay. The public market episode remains the default player.

The verified schedule and refreshed library make today’s Bittensor coverage easier to follow without presenting promotional content as a major launch.

2026-10-06 edition →SN8 · Vantaverified3 / 5 stars

SN8 Vanta adds limit orders outside regular equity hours

SN8 Vanta’s latest code supports equity limit orders during pre-market, 04:00–09:30 Eastern, and after-hours, 16:00–20:00 Eastern. Regular equity trading remains 09:30–16:00; the wider windows are not unrestricted overnight market-order trading. The update adds trade and quote handling for those sessions, and separate code permits corrections to an entity’s account size without resetting its history. These are substantive trading-infrastructure changes, not a performance or revenue claim. The merged implementation and published market-hour rules were checked; full production adoption was not independently demonstrated.

SN8 Vanta extends its documented equity trading sessions with bounded order rules and improved account handling.

2026-10-06 edition →SN10 · Paretonverified3 / 5 stars

SN10 Pareton adds evaluation under simultaneous demand

SN10 Pareton’s new benchmark code evaluates completion time across input tiers under simultaneous requests, with failed requests reducing eligible scores. The published breakdown includes tier weights, absolute times, failures and deductions so miners can reconstruct the arithmetic. This tests how a tuned inference system handles competing work rather than judging only isolated requests. It is a verified implementation change, not a newly demonstrated customer speedup. Separately, the Opentensor conversation with SN10 Pareton is scheduled for Thursday, October 8; it has not happened yet.

SN10 Pareton broadens evaluation toward realistic concurrency and auditable failure penalties, with customer outcomes and the upcoming talk distinguished.

2026-10-06 edition →SN17 · 404—GENverified3 / 5 stars

SN17 404 records its Round 51 winner and opens Round 52

SN17 404’s public competition records now identify computer-vision-ai-lab/jade-harrier-6 as the Round 51 winner and mark Round 52 open. The new schedule closes reveals at block 9229786, sets the generation deadline at block 9230986 and gives an October 7, 08:00 UTC next-stage estimate. The winner’s entry is scheduled to become effective at block 9229786; that future block should not be confused with a payment already made. This resolves the earlier pending Round 51 result at the repository level and opens the next cycle. Separately, its game-jam community prize remains a different competition, with voting through October 12.

SN17 404 has newly published competition results and a next-round state, with future effective blocks and the separate game jam distinguished.

2026-10-06 edition →SN22 · Desearchdeveloping3 / 5 stars

SN22 Desearch changes task timing as the team reports a lower burn

SN22 Desearch’s new task API code starts a miner’s clock when tasks are actually handed over and judges completion when the upload reaches the API, rather than penalizing the miner for later server processing. Repeated completion requests return the original answer, and verified page updates are published in numbered files for downstream indexing. Today’s team-attributed brief also reports faster queues and a burn reduction to 70%, with validators updating automatically. The timing and publishing changes are verified implementation; the new burn and production rollout remain a secondary team report. Reported queue backlogs were not independently shown to have cleared, so the repair is not presented as an all-clear.

SN22 Desearch addresses a concrete fairness and throughput problem, while the reported emission change and complete backlog recovery remain developing.

2026-10-06 edition →SN23 · Trishoolverified3 / 5 stars

SN23 Trishool reports its output guard climbing to 81.87% F1

SN23 Trishool’s October 5 update reports output-guard F1 improving from 73.9% in its initial version to 78.53%, then 81.87%. The team says successful miner attacks become training examples for the next version, making the subnet’s adversarial work feed directly into the guard’s development. It describes the latest score as less than one point from the leading result in its comparison. That is a measured progress report, not proof that the system blocks every attack or leads every security benchmark. The result and comparison were not independently reproduced. The post landed at 15:14 UTC, four minutes after yesterday’s cutoff, so it belongs in today’s window.

SN23 Trishool reports a concrete progression tied to miner-generated attacks, with evaluation scope and independent-reproduction limits retained.

2026-10-06 edition →SN25 · URdeveloping2 / 5 stars

SN25 UR’s feed records a large lock changing to perpetual

SubnetRadar’s October 5 feed records an existing 545.1-thousand-alpha SN25 UR lock switching from decaying to perpetual at 19:49:35 UTC. It attributes the change to hotkey 5CyQFy…1wxG using set_perpetual_lock. This is a change in lock commitment, not 545,100 alpha newly purchased or added. The linked event page failed to load its details in both the public fetch and browser check, so the exact block and full event parameters remain unverified. The feed report is included as developing because of its scale, with no locker motive or ownership-transfer claim.

SN25 UR has a potentially material commitment change, but unavailable event details require a developing label and no purchase inference.

2026-10-06 edition →SN26 · Perturbdeveloping2 / 5 stars

SN26 Perturb reportedly targets a November product launch

Today’s team-attributed brief says SN26 Perturb is moving into a product phase after five months of subnet development, with launch targeted for next month. The team reportedly plans to continue buybacks before revenue begins and use a substantial share of future revenue for alpha buybacks. This is a stated roadmap and proposed funding model, not an already launched product, a disclosed customer contract or existing product revenue. The original announcement and buyback transactions were not independently matched during this scan.

SN26 Perturb supplies a new product timetable and reported business plan, with future launch and revenue distinguished from completed outcomes.

2026-10-06 edition →SN30 · Endure Networkdeveloping2 / 5 stars

SN30 Endure targets today’s mainnet launch; activation is not confirmed

SN30 Endure’s October 5 announcement targets October 6 for its mainnet launch, describing competitive, outcome-scored risk intelligence. A signed-in latest-post check still found that announcement, rather than a completed launch notice. Today’s team-attributed channel brief says validators are not currently setting weights and that the miner burn is being reduced later this week. The launch remains developing at this edition’s cutoff. A scheduled date and an operating subnet slot do not establish active scoring or reward distribution.

SN30 Endure has a material launch target, but the separate weight-setting and burn status prevents premature launch confirmation.

2026-10-06 edition →SN33 · ReadyAIverified3 / 5 stars

SN33 ReadyAI verifies a 19.24 TAO buy-and-burn and reports $95,000 ARR pace

SN33 ReadyAI reports that its jobs API’s latest weekly pace annualizes to about $95,000 in recurring revenue, with a six-figure target for October. That is an annualized pace, not $95,000 received last week or audited booked revenue. The team also says September’s buyback was 45% larger than August’s. Its linked explorer record confirms a successful add_stake_burn into SN33 for 19.24 TAO at block 9221415, timestamped 04:05:36 UTC on October 6, with AlphaBurned and AddStakeBurn events. The transaction is inspectable evidence of the burn; it does not independently verify the revenue figure, its funding source or the month-to-month percentage.

SN33 ReadyAI links a business progress report to a directly checked burn transaction, separating on-chain facts from reported revenue and comparisons.

2026-10-06 edition →SN38 · ChronoLLMverified3 / 5 stars

SN38 ChronoLLM merges Round 14’s model caching and batched evaluation

SN38 ChronoLLM’s Round 14 pull request, still open in yesterday’s report, merged at 16:55 UTC on October 5. The change keeps downloaded model weights in a persistent cache and batches model-versus-model generation according to available memory. Qualified models are prefetched, with availability checked before evaluation, reducing repeated downloads and avoidable stalls. The validator container pin also changes. This is a concrete step toward more efficient and repeatable evaluation, but a merge does not confirm every validator has upgraded or establish a measured production speedup. Today’s channel discussion still mentions logs being lost on redeployment and a plan to preserve them; that separate observability issue is not declared resolved.

SN38 ChronoLLM advances from a proposal to merged evaluation code, with rollout, measured performance and log persistence kept separate.

2026-10-06 edition →SN39 · deprecateddeveloping2 / 5 stars

SN39 is marked deprecated despite a large reported inflow

SN39’s current identity in our chain-derived market feed is “deprecated,” while some directories still call it Cathedral or Basilica. SubnetRadar records a 1,315.7 TAO inflow from wallet 5GuRL…iuaC at block 9219245, timestamped 20:51:41 UTC on October 5. At 14:28 UTC today, alpha/TAO was up 16.98% over 24 hours. Those observations warrant attention, but neither establishes a relaunch, new owner, customer milestone or the wallet’s motive. The associated public repository has no new commit in this window. Use the current slot identity and the specific recorded movement rather than treating price or stale branding as proof that a new project is live.

SN39’s outlier move and large recorded inflow make its conflicting identity material, without inventing a catalyst or ownership event.

2026-10-06 edition →SN44 · Scoredeveloping3 / 5 stars

SN44 Score reports September break-even and demonstrates general object detection

SN44 Score shared an October 5 interview reporting that September was its first break-even month and that buybacks had begun from its owner address. Those are reported business milestones; this scan did not verify financial accounts or match the buyback transactions. Its own new demo shows the General Object Detector counting overlapping apples inside Score Studio without custom training for that example. Separately, the founder describes SN44 Score models being used by Manako’s Rig for client vision workflows. The product demonstrations add concrete context to the commercial claim, but are not proof of an unnamed packhouse deployment. New world-model training remains a next step, and the petrol-station track issue is not independently closed.

SN44 Score combines a fresh reported break-even milestone with concrete product demonstrations, while financial verification, customer scope and ongoing incidents remain clear.

2026-10-06 edition →SN49 · Nepher Roboticsdeveloping2 / 5 stars

SN49 Nepher Robotics reportedly requires simulator upgrades

Today’s team-attributed brief instructs SN49 Nepher Robotics miners to upgrade to Isaac Sim 6.1 and Isaac Lab 3.0.0. Keeping simulation environments aligned matters when robot policies are compared under common conditions. The original upgrade notice and deployed validator requirements were not independently matched, so this is an operational instruction reported by the channel brief, not a newly opened competition or a new physical-robot deployment. Yesterday’s conviction lock remains a prior event.

SN49 Nepher Robotics has a miner-relevant compatibility instruction, with the source and deployment gaps clearly marked.

2026-10-06 edition →SN51 · lium.ioverified3 / 5 stars

SN51 lium.io removes collateral scoring while preserving existing reclaim paths

SN51 lium.io’s new code removes the collateral requirement from validator scoring and the miner deposit commands. Existing locked collateral can still be reclaimed through a local contract client, with checks intended to avoid losing track of transactions whose outcome is uncertain. Another change starts host probes at SSH connection and runs GPU power restoration alongside volume creation, reducing sequential setup work. This changes provider onboarding and maintenance rather than proving a faster completed rental. The implementation is verified; current wallet reclaims and chain-wide validator adoption were not independently reconstructed. A member-reported rented node outage remains a separate, unresolved report.

SN51 lium.io makes a significant provider requirement change and preserves recovery for previously locked funds, without assuming automatic refunds or measured rental gains.

2026-10-06 edition →SN53 · engydeveloping2 / 5 stars

SN53 engy is reported to process 4–5 billion Kimi K3 tokens daily

An October 6 post by Algod reports SN53 engy revenue growing 100% month over month and processing 4–5 billion Kimi K3 tokens daily through direct distribution. If sustained, direct usage would matter for an inference subnet’s business beyond its emissions. The post does not provide an independently audited revenue amount or public usage ledger, and those figures were not reproduced in this scan. Separately, SN107 Minos names SN53 engy as an intended provider for its second mechanism, while SN97 Albedo has merged code that uses it for evaluation. Those integrations are evidence of a broader role, but do not verify Algod’s numerical claims or mean every announced workload is already live.

SN53 engy has a material public usage and growth claim plus specific subnet integration context, with unverifiable business figures labelled as reported.

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.