Skip to main content

Sturdy Subnet

Sturdy Subnet — 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).

Sturdy Subnet — a Bittensor subnet (SN10) that Sturdy uses for competition between allocation strategies; 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 (SN10) where miners propose allocation strategies and validators incentivize strategies based on yield (per the project’s description).
  • Who it’s for: the Sturdy protocol and its aggregators/users (as an “engine” for choosing allocations).
  • Why onchain/token: onchain is used as a competition/incentive mechanism (miners/validators) within the Bittensor subnet; the role of a separate project token is not established.
  • What you can actually touch (Tier‑1): a public dashboard/analytics at sturdysubnet.org (see links_*).

How it works (very briefly)

  1. The user does: uses Sturdy (or an aggregator) to place/manage a deposit in “silos” (the exact UX steps are not established per Tier‑1).
  2. The system does: requests from the subnet a set of allocation strategies among whitelisted silos.
  3. The user gets: an allocation/strategy selected based on the results of the competition and incentives.
  4. Where the blockchain is: Bittensor Subnet 10 — competition and incentives for strategies (miners/validators).
  5. Token role (if any): not established (no Tier‑1 description of the token utility was found).

Quick links: AI thesis fit

Project passport

Field Value
Project name Sturdy Subnet
Also known as (aliases) Sturdy SN10
Logo (logo) ../assets/465_sturdy-subnet_logo.svg
Token symbol (ticker) —
Category AI/Other | DeFi | Infra
Primary chain (chain) Bittensor
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) —
Token contract —
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit yes
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) allocation strategy competition
Use‑case (use_case) allocation selection for silos
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 0 / 2
Last verified 2026-02-11

General project overview

Sturdy Subnet is a Bittensor subnet (SN10) that Sturdy uses to provide aggregators with allocations among whitelisted silos. Per the project’s documentation, miners provide allocation strategies, and validators incentivize strategies based on yield.

Features/modules

  • Bittensor Subnet 10: competition of allocation strategies (miners) and incentivization of strategies based on yield (validators).
  • Integration with the Sturdy protocol/aggregators (integration details are not established per Tier‑1).

Typical scenarios

  • Aggregator: receives recommendations/allocations → applies them to whitelisted silos.
  • Miner: publishes an allocation strategy → competes with other strategies.
  • Validator: evaluates the results → distributes incentives (per the subnet rules).

Getting started (wallet/network)

  • What you need: instructions for mining/validating are in links_* (Discord/Docs).
  • Network/chain: Bittensor; Subnet 10 (see Explorer).
  • Fees: not established (Tier‑1).

Architecture/tech (non‑AI)

  • Components: Sturdy + Bittensor Subnet 10 (miners/validators) for allocation strategies.
  • Participant roles: miners (strategies), validators (incentives/evaluation), aggregators (consumer of the result).
  • Where logic runs: evaluation/competition of strategies — in the Bittensor subnet mechanics; integration with “silos” — outside this document (not established per Tier‑1).
  • Dependencies: not established (Tier‑1).

Token/economics (expanded, no forecasts)

  • Token utility: not established (Tier‑1).
  • Protocol necessity drivers: —.
  • Who pays fees: —.
  • Where fees go: —.
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: not established (Tier‑1).
  • How protocol parameters change: not established (Tier‑1).
  • Where decisions are discussed/made: GitHub/Discord (links — in links_*).
  • Keys/multisig: not established (Tier‑1).

Security and incidents

  • Audits: yes (see Audit report(s) in links_*).
  • Bug bounty: yes (see Bug bounty in links_*).
  • Incidents: not established per Tier‑1.
  • Threat model: the risk of dependence on offchain evaluation of strategies/data; there is no Tier‑1 data that onchain is critical for the product.

Project status and timeline

  • Current status: active; network: mainnet.
  • Key releases/milestones: not established per Tier‑1.
  • Roadmap: not established per Tier‑1.

Ecosystem/integrations

  • Integrations: the Bittensor ecosystem; integration with Sturdy/aggregators (details are not established per Tier‑1).
  • Partners: not established (Tier‑1).
  • Where it’s actually used: not established (Tier‑1).

AI component of the project

  • What is real AI here? The project uses a Bittensor subnet as a decentralized “layer” for competition between allocation strategies; specific ML models/metrics are not described on the subnet page.
  • What is truly onchain? Competition and incentives in Bittensor Subnet 10 (miners/validators).
  • Why is a token needed? Not established (Tier‑1).
  • Red flags (based on the information found): specific AI metrics/architecture for the strategies are not described; the role of the project token requires separate Tier‑1 confirmation.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 1
Onchain necessity medium 2
Token necessity low 0
Evidence Tier‑1 present (AI/OC), none for the token 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): What exactly the AI component does (model/algorithm) — not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.sturdy.finance/overview/sturdy-subnet
  • Why sufficient / why not (one line): The documentation describes “allocation strategies”, but without AI details.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a public dashboard/analytics showing the metrics of the subnet/aggregators (the project’s demo surface).
  • Evidence: Tier‑1 — https://www.sturdysubnet.org/dashboard
  • Why sufficient / why not (one line): This is a reproducible “surface” for observing the operation of the subnet and aggregators; it does not disclose AI metrics/models (AI_3 remains 0).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not established per Tier‑1.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There are no Tier‑1 quality metrics for strategies/signals.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): The architecture/model versions for the subnet are not described on the subnet page.
  • Evidence: Tier‑1 — https://docs.sturdy.finance/overview/sturdy-subnet
  • Why sufficient / why not (one line): There is a description of the purpose and roles, but no technical details of the AI part.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Bittensor
  • Addresses/identifiers: Subnet 10
  • Evidence: Tier‑1 — https://docs.sturdy.finance/overview/sturdy-subnet ; Tier‑2 — https://taostats.io/subnets/10/chart
  • Why sufficient / why not (one line): Tier‑1 specifies that this is a Bittensor subnet (SN10).
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the competition/incentive mechanism for strategies in the subnet (miners/validators).
  • Evidence: Tier‑1 — https://docs.sturdy.finance/overview/sturdy-subnet
  • Why sufficient / why not (one line): Tier‑1 describes that validators incentivize the strategies with the best yield.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not proven that without the Bittensor mechanics the Sturdy product breaks down; this is not described in Tier‑1.
  • Evidence: Tier‑1 — https://docs.sturdy.finance/overview/sturdy-subnet
  • Why sufficient / why not (one line): There is no Tier‑1 statement about onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The presence/absence of a separate subnet token is not established in Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 statement “no token”.
  • Conflict note (if any): —

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 token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of TK_1.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): Token mechanics of incentives/collateral/penalties for the project token are not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of TK_2.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via the token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of TK_3.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established (no Tier‑1 description of the token utility).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without Tier‑1 on token mechanics, replaceability cannot be strictly asserted.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.sturdy.finance/overview/sturdy-subnet Description of Sturdy Subnet (SN10): allocation strategies (miners) and incentivization of the best strategies (validators).
Tier‑1 https://www.sturdysubnet.org/dashboard Public dashboard/analytics (what you can “touch” and observe).
Tier‑2 https://taostats.io/subnets/10/chart Subnet 10 on Bittensor (explorer/metrics).
Tier‑1 https://docs.sturdy.finance/overview/security-and-audits The existence of a section about security/audits (as a source of links).
Tier‑1 https://immunefi.com/bounty/sturdy/ Bug bounty (a Tier‑1 link from links_*).
Tier‑1 — No Tier‑1 source for claim “the project token is needed for payment/incentives/governance” was found.

No comments to display

Back to top