Ridges is Bittensor subnet 62 (SN62), a project in the Code Generation and Development Tools lane. One agent.py, one git diff, may the best one win.
An open competition to build the best AI software engineer. Miners submit a Python agent.py that has to read a real codebase, understand a task, and return a working git diff. Validators run those agents inside a sandbox against SWE-bench Verified and aider-polyglot, and the platform decides who gets paid.
It is an educational deep dive, not a recommendation to stake. For live price, pool depth, and performance, always open the live subnet page.
What is Ridges (SN62)?
Ridges is subnet 62. Miners build small Python programs that act as autonomous software engineers. Each program receives a problem (a real bug from a real repo, or a programming exercise from a curated benchmark) and must return a patch in the form of a git diff. Validators run those patches against the project's own tests inside a containerized sandbox, and the top-scoring agent on the platform leaderboard takes the subnet weight.
In plain English: It is a hiring funnel for AI coders, run as a continuous tournament. Every agent gets the same problem and the same toolbox, and the one whose patches actually make the tests pass wins.
Centralized reference points: Devin (Cognition), Cursor, Claude Code, GitHub Copilot Workspace, Aider
How miners and validators work
Like every Bittensor subnet, SN62 is a two-sided market: miners produce work, validators score it, and emissions follow those weights under the network’s dTAO economics.
- Miners write a Python file that exposes
agent_main(input) -> str, returning a git diff. They upload it through the Ridges CLI, which requires an OpenRouter runtime key for the agent's inference calls. - Validators register with the Ridges platform, run uploaded agents inside the project's Harbor sandbox framework against the active task set (currently SWE-bench Verified and aider-polyglot), report results back, and set on-chain weights from the platform's scoring endpoint.
Mechanism and design
A miner's deliverable is a single Python file. The contract is small: agent_main(input) -> str, where the string is a git diff. The CLI (ridges miner setup, ridges miner run-local, ridges upload) handles workspace setup, local dry runs, and the upload itself, which now requires both an OpenRouter runtime key and an OpenRouter management key for platform-side validation. Local testing supports OpenRouter, Targon, and Chutes as inference providers, plus a custom sandbox-proxy hook.
On the validator side, the runtime is a separate component. Each validator registers a session with the Ridges platform, takes assignments, downloads the relevant task archives, and runs the uploaded agent inside the project's Harbor sandbox: a Docker-based execution framework that boots the agent, lets it produce a patch, applies the patch with git apply, and then runs the verifier. Result rows go back to the platform, which computes scores and exposes them at /scoring/weights. The validator periodically pulls that mapping and writes weights on-chain. The current production task set spans SWE-bench Verified (the 500-task human-validated subset of SWE-bench) and aider-polyglot (multi-language programming exercises). The recent commits show the team tightening operations: a cost-based tie-breaker between near-tied agents, short-circuiting evaluations on agents that fail early, and a stricter exclusion of cancelled or reference runs from the public leaderboard.…
Why the project exists
- The problem it solves: Code-writing AI is easy to demo and hard to score. SWE-bench Verified and aider-polyglot give a real, reproducible signal, but running them at scale and against constantly changing agents takes serious infrastructure. Ridges turns that infrastructure into a live market.
- The opportunity: Coding agents are one of the few AI use cases where the buyers (engineers and engineering teams) already pay for shoddy versions of the product. A continuously evaluated open agent ladder has a real chance to surface something useful for that audience.
- The Bittensor advantage: Open weights, open agent code, and a winner-take-all incentive that pushes contributors to ship faster than any single closed team can iterate. The best agent is always public.
- Traction signals: 3,386 commits on main, 19 contributors on the public repo, last push 2026-05-27 (the day before this writeup). Multiple merges per day through May from the core team, including a new cost-based tie-breaker, short-circuit logic for failing agents, and a leaderboard cleanup that excludes cancelled runs.
What stakers should check before buying alpha
Subnet storytelling is cheap. On-chain and product checks are not. Use the same framework as our subnet metrics guide:
| Check | Why |
|---|---|
| Real product / docs / repo | Separates shipping teams from narrative-only slots |
| Pool depth (TAO) | Your exit door: thin pools amplify slippage |
| Net flows (7d / 30d) | Under flow-based emissions, capital votes with its feet |
| Emission share | Whether the market is funding this subnet right now |
| Ownership concentration | Large holders can move a small alpha market |
| Immunity / deregistration | Post-immunity weak slots can lose the race (see immunity guide) |
Pull the live numbers on Ridges · SN62 rather than trusting any static screenshot in a blog post.
Risk factors
- Sustained price decline: A 61% drawdown over ninety days is real. It reflects rotation out of the AI-coding-agent narrative and the lack of distributed reward at the protocol layer, even with active development.
- Winner-take-all and platform centralization: The Ridges platform is the source of truth for scoring, and the weights endpoint is a single dependency. That keeps quality high, but it means a platform outage or scoring bug has outsized impact compared to a more decentralized scoring scheme.
- Inference cost on miners: Required OpenRouter keys for both runtime and management mean a real-money cost to compete, on top of whatever the agent costs to run per task. This raises the barrier to entry for hobbyist miners.
- Centralized competition: Cognition, Cursor, GitHub, and Anthropic are well-capitalized and shipping fast on the same problem. The Ridges advantage has to be sustained open-source velocity, not a one-time benchmark win.
How this fits a TAO portfolio
Many holders keep a root vs subnet split: root for calmer TAO exposure, subnets like Ridges for thematic upside (and higher variance). If you use TaoScale, you can size SN62 from your wallet without handing over custody. See non-custodial staking.
- Live market: SN62 on TaoScale
- Browse and stake: /invest
- More subnet explainers: /blog/subnets
FAQ
What does Ridges do on Bittensor?
It is a hiring funnel for AI coders, run as a continuous tournament. Every agent gets the same problem and the same toolbox, and the one whose patches actually make the tests pass wins.
What is the SN62 alpha token?
When you stake TAO into subnet 62, you receive that subnet’s alpha. Its price versus TAO moves with the subnet’s pool (see what is dTAO).
How do I research Ridges before staking?
Read the mechanism above, open the official repo/docs when available, then verify pool depth, flows, and activity on SN62. Cross-check with the metrics checklist.
Is this financial advice?
No. TaoScale publishes educational explainers and live tools. Decisions to stake are yours alone.
Not financial advice. Educational overview of Ridges (SN62) compiled from public project materials and ecosystem documentation. Mechanisms and market structure change, so verify live data and official sources before acting.
