BITTENSOR · THE NEWS ARCHIVE
Search 85 dated editions without scrolling through them one by one.
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.
The November 1 public brief attributes to the team a CLI option for viewing scores of a miner’s completed URNetwork submissions. That can help participants inspect finished evaluations. The underlying Discord message and CLI flow were not independently tested; suggestions for more difficult tasks are discussion, not an announced new competition.
A small participation-tool improvement with source and execution limits.
The November 1 public brief attributes a stale-price execution complaint and planned hedging/arbitrage controls to channel participants and the team. It says the team was reviewing the report and did not confirm arbitrage. A separate digest gives a different flagged-account amount, so no loss total is published here. The underlying data and Discord originals were not verified, and no deployed fix or effect on another subnet is established. This remains a market-integrity lead requiring follow-up.
A potentially material operational concern warrants qualified coverage while contradictory secondary details remain unresolved.
A successful direct burn_alpha call on November 1 at 20:50:12 UTC destroyed 223.333333333 SN8 alpha (223,333,333,333 base units). Finalized block 9,413,552, extrinsic 11, event 314 and the unchanged Vanta registration confirm the transaction. This is an explicit alpha burn, separate from miner-emission withholding, fees or recycling. No buyback marker or revenue source is established by this call, so it does not verify revenue, TAO burned or a price effect.
A qualifying supply-reduction transaction has exact finalized evidence, but this individual burn does not establish adoption or business performance.
In its November 1 announcement, Desearch says its public network statistics stream updates once a second and can replay missed snapshots from the preceding 20 minutes using Last-Event-ID. The attached diagram illustrates a dropped connection followed by replay and resume. That is useful for dashboard recovery; reconnect behavior was not independently tested, and these statistics are distinct from the separate AI-search streaming endpoint.
A concrete developer reliability feature with a clear recovery window and testing boundary.
Finalized block 9409822 (2026-11-01T08:24:12+00:00) records a successful SubnetOwnerHotkeySet at extrinsic 6, event 188. The stored hotkey changed from 5ELpkVn84ubfA7cYtz8YxL3NKYBSvMEZNGzkibkmsDe6YVcL to 5ELAvsvXL9kU9CMzkFcRiqFjw3QGVgA7MrvEfcHsicv5WvWX. The owner coldkey and registration height 2538424 were unchanged immediately before and after. This is an operational hotkey change, not a verified subnet sale or owner-coldkey transfer.
An exact finalized operational change with ownership implications bounded by before/after state.
Carry-forward safety watch: October 31 public coverage and an accessible screenshot attribute compromised wallets, unspecified losses and a product-announcement setback to a Perturb team message. The screenshot does not independently establish the speaker’s role, exact original date, attack cause, affected addresses or recovery. No new primary mitigation was found on the official X account. This is the same developing incident, not a new hack or an independently reconstructed chain exploit.
Unresolved safety information is retained without turning a screenshot into execution evidence.
The dated public brief says the challenge API distributes tasks while validators perform validation and grading. It also attributes a planned reduction in conversation-task share to the move toward a Skill Store. This clarifies the stated architecture; no new Skill Store launch or deployed workload change is established.
Useful mechanism clarification, distinct from a completed product launch.
The November 1 brief says provider errors are retried, failed questions score zero without stopping a run, and the submission quota is three ZIPs per hotkey per 24 hours. It also says oversized calls are admitted despite per-question cost caps. These are attributed operational clarifications from the brief, not an independently tested security or cost guarantee.
Practical submission rules for miners with direct-source access still limited.
The dated brief attributes removal of three faulty ground-truth blocks to the team: Petrol Station 9402900, PPE 9400500 and Beverage 9402000. This matters to evaluation fairness. Moving Vehicle detection to Profile 2 is only being considered for early next week, rather than already applied. Original channel messages and resulting scores were not independently checked.
Specific evaluation corrections and a separate, still-unapproved plan.
The dated brief attributes a denial of shutdown to the team and says a client-progress update and another buyback tranche are expected. These are team statements and plans; no new client revenue or buyback transaction is independently verified here.
A relevant status clarification without treating promised commercial progress as delivered.
The November 1 brief says an earlier-proof chat-log bonus is live through ZIP uploads in the submissions menu. It also says a Caltech Mathathon arrangement was cancelled after event-structure changes and that an Imperial College London hackathon is planned for November 22–26. The original messages and counterpart event confirmation remain unverified; do not treat a planned event as a completed partnership outcome.
A participation change and cancellation deserve clear coverage, with external confirmation outstanding.
In an October 31 reply about untrusted rollout verification, Const describes a cheap initial commitment followed by a more expensive asynchronous spot check and penalties for cheating. This adds explanation to the already-covered distributed-RL report, not a measured overhead number or independently demonstrated security guarantee.
Relevant new explanatory commentary, separated from benchmark evidence.
Late-found October 31 merged PRs 392 and 393 add rental caps, failed-boot handling, shutdown cleanup and progress/deadline guards. These address the risk of machines continuing to cost miners when useful training is not progressing. The PRs describe code that still needs rollout: worker safeguards require rebuilt images, and a measured-time gate is off by default. No deployment or reduction in actual bills was independently observed.
Meaningful operator cost controls whose merged-code and deployment states remain separate.
Dated follow-up to the October 29 announcement and October 30 policy: the current official FAQ labels inference’s starting allocation 40%, Engine 20% and Generalist 30%, all measured within the miner portion of emissions. It says Generalist paused at October 30 16:30 UTC and Engine paused after its Friday slot, with no next crowning scheduled. Unpaid rewards are described as withheld/burned emissions, not qualifying explicit transaction burns. Further demand-linked adjustments remain plans; neither a fresh eTAO change nor lower realized selling pressure is established by commentary.
Actionable miner documentation clarifies denominators, dates and the difference between stated operation and finalized event evidence.
In its November 1 benchmark announcement, Beam reports transferring 1 TB in 2 minutes 42 seconds, describing a 20% speed improvement and 2.5 times as many security and integrity checks compared with the previous month. The attached graphic repeats those figures, and a team reply supplies audit ID 7ef65624-e81e-501d-9547-f051e4078a26. Faster large-file movement matters for distributing models and datasets, but the public audit and miner endpoints returned access errors during this review. The run, test conditions and comparison therefore remain team-reported rather than independently reproduced.
A specific infrastructure-performance claim with an audit reference, while independent access and reproducibility remain unresolved.
The November 1 brief says the team has not finalized the IM1/IM2 allocation, with roughly 10% discussed as an initial share that could later change. It describes IM2 mainnet as forthcoming and intended to operate autonomously with an agent. Neither a mainnet launch nor an executed allocation change is verified.
A useful roadmap qualification rather than a launch claim.
The dated brief describes medium effort, no Agent SDK system prompt, and compressor handling for subagent and side calls in the planned Claude Code and Haiku benchmark round. Cache-write accounting is still described as likely, and the backend was not expected in SOMA-benchmark before November 3. These are proposed settings and timing, not measured new performance results.
Specific benchmark preparation with uncertain settings and release timing retained.
Late-found October 30 announcement: Control Room beta invites practice on physics-AI challenges. The inspected mining documentation identifies testnet 567, unpaid participation and no carry-over of records to mainnet. It lists 32GB RAM and four CPUs, with GPU optional. The post’s next-day testnet-weights plan is not proof of execution, and mainnet activation was not verified. The full 81-second demonstration remains a media-review gap.
Useful participation information with testnet and unpaid status central.
The October 31 announcement adds Pika H3 Flex to the public video selector. The inspected catalog offered 5–15-second generation, picture and sound, and displayed 29 credits at five seconds during review. This is a visible catalog entry, not a completed paid render, quality benchmark or customer count. It is distinct from the earlier eleven-tool Director announcement. The full 27-second demonstration and its audio were not reviewed.
A specific available model choice, with pricing time and untested execution made explicit.
A successful finalized transaction on November 1 at 17:41:48 UTC changed Ditto's alpha-emission split from approximately 18% owner / 41% validators / 41% miners to 18% / 49% / 33%. Block 9,412,610, extrinsic 17, and exact storage immediately before and after confirm execution under the same subnet registration and owner. The validator bucket gains eight percentage points while the miner bucket loses eight; Root is paid its live baseline first, capped by the validator allocation. This is a redistribution of subnet alpha emissions, not an increase in Ditto's network emission share or a transaction burn. Individual staking returns depend on stake, performance and take, and historical yield windows can lag.
A verified payout-allocation change that directly affects miners and validators; it does not establish product adoption or a guaranteed yield.
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.