Ridges
Ridges — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).
Ridges — an AI/Agents | Infra project on Bittensor (subnet), token (symbol: —).
Disclaimer
Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.
TL;DR (for readers who are not into AI)
- What it is: a Bittensor subnet (SN62) that builds a “software engineer agents” platform — a model/agents that solve software development tasks as a set of subtasks, while miners compete on the quality of the solution.
- Who it’s for: operators of Bittensor miners/validators and teams that need an agent‑based approach to development tasks.
- Why onchain/token: the onchain part is the Bittensor subnet mechanics (participants/incentives/weights); in the Dynamic TAO model the subnet has a subnet‑specific “alpha” token and TAO reserves (see Evidence).
- What you can actually touch (Tier‑1): the public “Explore / Benchmark Agents” page with benchmarks and current queues (screener/validator).
How it works (very briefly)
- The user does: formulates a development task (for example, fixing a regression/adding tests) within the Ridges interface/process.
- The system does: breaks the work down into subtasks; miners execute/propose solutions; validators evaluate quality.
- The user gets: the highest‑quality solution/patch based on the evaluation results.
- Where the blockchain is: subnet netuid 62 on Bittensor — the onchain layer is used for incentives/weights/participation.
- Token role (if any): an external project token (ERC‑20 etc.) is not recorded per Tier‑1; at the same time, the subnet on Bittensor has a subnet‑specific “alpha” token (Dynamic TAO) and an onchain incentive economy.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Ridges |
| Also known as (aliases) | ridges.ai, SN62 |
| Logo (logo) | — |
| Token symbol (ticker) | — |
| Category | AI/Agents | Infra |
| Primary chain (chain) | Bittensor |
| Type | Appchain |
| Network status | mainnet |
| Consensus (consensus) | — |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | native |
| Token contract | Subnet netuid 62 (Bittensor) |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | subnet “alpha” token + TAO reserves/emissions (Dynamic TAO) |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | software engineer agents |
| Use‑case (use_case) | development task automation |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 3 / 3 / 1 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.ridges.ai/ |
| Docs | https://docs.ridges.ai |
| GitHub | https://github.com/ridgesai/ridges |
| Releases / Changelog | https://github.com/ridgesai/ridges/commits/main/ |
| Whitepaper | https://docs.ridges.ai/ |
| Roadmap | — |
| Security advisories | https://github.com/ridgesai/ridges/security |
| Explorer | https://taostats.io/subnets/62/chart |
| App / Demo | https://www.ridges.ai/explore |
| X | https://x.com/ridges_ai |
| Discord | — |
| Telegram | — |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/ridges-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/ridges-ai/ |
General project overview
In the docs, Ridges describes its goal: to build a platform where AI agents solve software development tasks end‑to‑end. The approach is to decompose an engineer’s work into discrete tasks and let Bittensor miners compete on these tasks; validators evaluate quality and distribute incentives.
Features/modules
- A “task pool” for agents and the mechanics of miner competition.
- Tools for developing/running a miner and a validator.
- A repository with the code and documentation on the components (platform, inference gateway, screeners/validators).
Typical scenarios
- Scenario 1: a miner solves a task (patch/test/fix) → submits the result → receives a score.
- Scenario 2: a validator evaluates miners’ results → updates weights/rewards within the subnet.
Getting started (wallet/network)
- What you need: follow the official docs (Miner Guide/Validator Guide).
- Network/chain: Bittensor subnet netuid 62.
- Fees: depend on participation in the Bittensor network and infrastructure costs.
Architecture/tech (non‑AI)
- Components: subnet miners/validators + offchain services/agents (LLM/tooling) + a repository with the platform code.
- Where logic runs: tasks are solved offchain (agents/miners); the Bittensor onchain layer records participation/weights and the incentive economy.
Token/economics (expanded, no forecasts)
- Economics: incentives/rewards and weights are implemented via the Bittensor subnet mechanics.
- Subnet token (Dynamic TAO): the subnet has a subnet‑specific “alpha” token and TAO reserves (see Evidence); an external project token (ERC‑20 etc.) is not recorded per Tier‑1.
Governance
- Not established per Tier‑1 as of the verification date.
Security and incidents
- Audits / bug bounty / incidents: not established per Tier‑1.
- Threat model: typical risks for a subnet (manipulation of quality evaluation, sybil behavior, vulnerabilities in the validator/evaluator) and risks of offchain agents (prompt injection, leaks of keys/secrets, supply chain).
Project status and timeline
- Current status: active; subnet on Bittensor mainnet.
- Roadmap: not recorded by Tier‑1 (
links_*has—).
Ecosystem/integrations
- Ecosystem: participation is observable via the subnet’s onchain metrics (taostats); other integrations/partners are not recorded per Tier‑1.
AI component of the project
- What is real AI here? Tier‑1 docs describe AI agents for solving development tasks and the pipeline “task → solution → evaluation”.
- What is truly onchain? subnet netuid 62 on the Bittensor network (the onchain part of the incentive mechanics).
- Why is a token needed? on Bittensor, subnet economics use TAO and the subnet‑specific “alpha” token (Dynamic TAO) for incentives/emission distribution.
- Red flags (based on the information found): without Tier‑1 confirmation of a “project token”, do not raise the token flags; the quality of the agents should be checked against reproducible metrics/task sets (if published).
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 3 |
| Onchain necessity | high | 3 |
| Token necessity | low | 1 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI is described as a product (agents for development tasks), not only an intent.
- Evidence: Tier‑1 — https://docs.ridges.ai/ ; https://github.com/ridgesai/ridges
- Why sufficient / why not (one line): the intent flag adds no signal when a description of how the system works is available.
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): AI agents solve software development tasks (patches/tests/fixes) and compete on quality.
- Evidence: Tier‑1 — https://docs.ridges.ai/
- Why sufficient / why not (one line): the Tier‑1 docs describe a concrete use‑case and the approach.
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): there is a public demo surface “Explore / Benchmark Agents” with benchmarks and queues (screener/validator).
- Evidence: Tier‑1 — https://www.ridges.ai/explore
- Why sufficient / why not (one line): this is the project’s public interface, where artifacts of the network/agents’ operation and benchmarks can be observed.
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): reproducible metrics/methodology for evaluating agent quality (benchmarks/datasets/procedures) per Tier‑1 are not normalized in this card.
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the repository contains code (api/validator/evaluator etc.) and docs on the components.
- Evidence: Tier‑1 — https://github.com/ridgesai/ridges ; https://docs.ridges.ai/
- Why sufficient / why not (one line): there are public technical artifacts and documentation on the components.
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Bittensor
- Addresses/identifiers: subnet netuid 62
- Evidence: Tier‑1 — https://taostats.io/subnets/62/chart
- Why sufficient / why not (one line): taostats records the existence of the subnet.
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: the onchain layer participates in the subnet’s incentive/weight mechanics.
- Evidence: Tier‑1 — https://taostats.io/subnets/62/chart
- Why sufficient / why not (one line): the subnet is part of the Bittensor onchain network.
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 1
- “Replace the blockchain” test: without onchain the trustless mechanics of distributing incentives/evaluation break down.
- Evidence: Tier‑1 — https://docs.learnbittensor.org/subnets/understanding-subnets ; https://taostats.io/subnets/62/chart
- Why sufficient / why not (one line): the subnet’s incentive network relies on onchain state.
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): on Bittensor the subnet has a subnet‑specific “alpha” token (Dynamic TAO); an external project token (ERC‑20 etc.) is not recorded per Tier‑1.
- Evidence: Tier‑1 — https://docs.learnbittensor.org/subnets/understanding-subnets
- Why sufficient / why not (one line): “no token” is incorrect for a subnet; at the same time, a separate external project token is not established.
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): payment for the service with the project token is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no Tier‑1 description of pay‑per‑call on the project token.
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): subnet economics distribute emissions/incentives and rely on the onchain mechanics of Bittensor (Dynamic TAO).
- Evidence: Tier‑1 — https://docs.learnbittensor.org/subnets/understanding-subnets ; https://taostats.io/subnets/62/chart
- Why sufficient / why not (one line): Tier‑1 docs describe incentives/emissions in subnets; taostats confirms the specific netuid.
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): the governance role of the project token is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): there is no Tier‑1 description of governance via the project token.
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): the replaceability of the token/subnet economics with an alternative model is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): for subnets, the role of the token/TAO is built into the Bittensor economy; a conclusion about replaceability requires separate analysis.
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.ridges.ai/ | Tier‑1 description of the vision/approach and instructions for participating in the project. |
| Tier‑1 | https://github.com/ridgesai/ridges | Public codebase of the platform (agents/validator/evaluator etc.). |
| Tier‑1 | https://www.ridges.ai/explore | Public demo surface: agent benchmarks and “live” queues of screeners/validators. |
| Tier‑1 | https://docs.learnbittensor.org/subnets/understanding-subnets | Tier‑1 description of Bittensor subnets: onchain consensus/emissions/incentives; subnet‑specific “alpha” tokens (Dynamic TAO). |
| Tier‑1 | https://taostats.io/subnets/62/chart | Onchain fact of the existence of subnet netuid 62. |
| Tier‑2 | https://www.coingecko.com/en/coins/ridges-ai | Reference profile and link navigation. |
| Tier‑2 | https://coinmarketcap.com/currencies/ridges-ai/ | Reference profile and link navigation. |
No comments to display
No comments to display