Bittensor Weekly — September 4th, 2026

Apex collapsed competition launch from 8 weeks to 2 hours.

"We have shrunk the launch time from a competition from ~8 weeks to about 2 hours."

fox dropped that in the channel this week. The Olympics pipeline and the Robotics Humanoid pipeline both went from months to an afternoon. The team has a stage gate at end of month to see how low they can push it. Trials opening soon for anyone tech-savvy who wants in.

When the platform for launching competitions moves this fast, the bottleneck shifts from infrastructure to ideas. That's the right bottleneck to have.

Bitsec's head-to-head win against Anthropic's Fable 5 got the mainstream treatment this week. John Yu appeared on Jason Calacanis's This Week in Startups to walk through how a decentralized subnet of competing security miners found more vulnerabilities in a paid client engagement than one of the most capable closed-source models.

The test itself ran in June — Fable 5 had to be jailbroken to run the scan at all, and Bitsec still found more. But the podcast put the result in front of an audience that doesn't follow crypto or Bittensor. That's the kind of exposure the network needs more of.

"Minotaur is still here, but from this point forward, we are no longer operating on Subnet 112."

τ-slice put it plainly after the coldkey swap completed and ownership transferred. 24 hours notice before market sales. An introduced buyer. The swap started Monday, finished by Tuesday. Everything documented.

The DeFi intent execution tech stays with the team. They're exploring a return on a new subnet, or bringing it directly to platforms and wallets.

Subnet transfers are rare. A clean one with transparent communication is rarer. Minotaur showed how it's done.

Building hard: SN1 (competition pipeline from months to hours), SN5 (V4 overhaul coming September, harder problems), SN31 (all three repos mainnet-ready, four mining tiers), SN45 (V3 Article Intelligence in internal testing, "shake up the mining" update incoming), SN79 (0.6.0 exchange agent framework live, scoring rewrite ready to flip), SN90 (BTLABS landed 11 nodes — 7x H200, 4x H100, enterprise confidential compute from day one), SN105 (Room data-transfer live across the Beam network), SN109 (v0.1 committed, MVP in 1-2 weeks), SN122 (week 4 of beta, testnet registered, shipping visible milestones).

Shipping live changes: SN2 (v14.14.0 — security patches, validator IP rotation tolerance), SN44 (Car Wash element replaced with vehicle detection, live annotation), SN60 (beat Fable 5 in head-to-head), SN67 (fast-mode tasks rolling, novelty check tightened to two comparisons), SN68 (better molecule evaluation with atom pair fingerprints), SN107 (scoring config endpoint published, GVCF bug found and patched), SN111 (4-batch evaluation guarantee for newcomers, transparent Q&A all week), SN120 (post-crown audit CLEAN — 1248 of 1248 challenger thoughts were unique reasoning), SN124 (V5.1.5.3 — interception scoring change, not hover), SN126 (telemetry-based evaluation, no manipulation possible).

Transparency standouts: SN6 (baseline forecaster in scoring alongside prediction markets), SN33 (explained scoring mechanism in detail — random 6-miner sampling, EMA), SN110 (public debate on what makes a subnet decentralized), SN100 (team acknowledged the work of subnet ownership, community responded with encouragement), SN118 (v11 screening policy broke, rolled back to v10, fixed one agent at a time in the open).

Dormant or stalled: SN112 exited. SN59 moving to miner burn. SN70 flagged by community for low liquidity. Most other subnets are silent. Building, not talking.

The Cortex (SN100) channel this week had a miner who'd missed announcements and felt left out. The team posted the link again. No defensiveness, no "read the docs." Then Side eye Corgi said the line about not being born a good subnet owner — you become one.

The channel didn't pile on the miner or dismiss the frustration. They chose encouragement.

This is the version of Bittensor that doesn't make the news. A builder, a miner, a moment of friction, and a community that answered with patience instead of cynicism. It happens somewhere on this network every week.

Subscribe for next week's edition: newsletter.bittensor.quest

Shaping the next issue: tell me what to keep, what to cut, and what you want more of — mailto:[email protected]