Skip to main content

Sportstensor

Sportstensor — 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).

Sportstensor — a project about a decentralized “predictive intelligence” network on Bittensor; Subnet 41, 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 network on Bittensor where independent developers publish predictive models for sports events, and the system evaluates them against real outcomes.
  • Who it’s for: developers/ML engineers (as participants), as well as consumers of predictions/signals (as clients).
  • Why onchain/token: onchain is used for the competition and the distribution of incentives (miners/validators) within the subnet; the role of a separate project token is not established.
  • What you can actually touch (Tier‑1): the dashboard/leaderboard at dashboard.sportstensor.com (see links_*).

How it works (very briefly)

  1. The user does: joins as a miner/participant and submits predictions/signals (or uses the results as a client).
  2. The system does: scores the predictions against real outcomes and calculates the participants’ contribution.
  3. The user gets: results/reputation/incentives (for participants) or access to signals (for clients — details not established).
  4. Where the blockchain is: the Bittensor subnet — competition, recording of results and incentives.
  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 Sportstensor
Also known as (aliases) Sportstensor SN41
Logo (logo) ../assets/469_sportstensor_logo.png
Token symbol (ticker) —
Category AI/Other | 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 —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) ML models for sports forecasting
Use‑case (use_case) sports event outcome predictions
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 2 / 0 / 2
Last verified 2026-02-11

General project overview

Sportstensor describes itself as a decentralized network for “predictive intelligence” in sports predictions. Per the documentation, independent AI/ML developers deploy models that compete by submitting predictions; the predictions are then scored against real outcomes, and incentives are directed to the most successful participants.

Features/modules

  • A mechanism for the competition of models/signals based on a Bittensor subnet.
  • A white paper describing the incentive mechanism for prediction markets (scoring/rewarding miners).
  • Mining instructions (a guide in the documentation and the repository).

Typical scenarios

  • Miner: submits predictions → receives a score/rewards based on the results.
  • Validator: evaluates predictions against outcomes → distributes incentives.
  • Client: uses aggregated signals/models → gets a predictive result (access details not established).

Getting started (wallet/network)

  • What you need: instructions for mining/participation — in Docs/GitHub (see links_*).
  • Network/chain: Bittensor; Subnet 41 (see Explorer).
  • Fees: not established (Tier‑1).

Architecture/tech (non‑AI)

  • Components: the subnet (miners/validators) + the scoring/rewarding mechanism described in the white paper; the mining code — on GitHub.
  • Participant roles: miners (predictions/signals), validators (evaluation and incentives).
  • Where logic runs: submission/evaluation of predictions and incentives — in the subnet mechanics; external data on outcomes — 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/Medium (links — in links_*).
  • Keys/multisig: not established (Tier‑1).

Security and incidents

  • Audits: not established per Tier‑1.
  • Bug bounty: not established per Tier‑1.
  • Incidents: not established per Tier‑1.
  • Threat model: external data on outcomes/sources requires re‑checking; the token utility is not established.

Project status and timeline

  • Current status: active; network: mainnet.
  • Key releases/milestones: see Releases / Changelog in links_*.
  • Roadmap: see Roadmap in links_*.

Ecosystem/integrations

  • Integrations: the Bittensor ecosystem (subnet); integration 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 documentation claims a network where AI/ML developers publish predictive models; the models are evaluated against real outcomes.
  • What is truly onchain? The competition of miners and the distribution of incentives in Bittensor Subnet 41 (per the description of the mechanics).
  • Why is a token needed? Not established (Tier‑1).
  • Red flags (based on the information found): no Tier‑1 description of the token utility; it is not established exactly how external outcomes and data are obtained/verified.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
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 is a description of a working participation model (models/predictions), so “intent only without AI” is not singled out.
  • Evidence: Tier‑1 — https://docs.sportstensor.com/
  • Why sufficient / why not (one line): The Tier‑1 page describes the mechanism of competition between AI/ML models.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Participants publish predictive ML models/signals for sports events; the system evaluates the predictions against real outcomes.
  • Evidence: Tier‑1 — https://docs.sportstensor.com/ , https://docs.sportstensor.com/white-paper
  • Why sufficient / why not (one line): The Tier‑1 documentation directly describes ML models/predictions and scoring against outcomes.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a public dashboard/leaderboard at dashboard.sportstensor.com.
  • Evidence: Tier‑1 — https://dashboard.sportstensor.com/
  • Why sufficient / why not (one line): This is a reproducible demo surface of the project; at the same time, the quality metrics of the models (AI_3) are not disclosed in a verifiable form.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not established per Tier‑1 (apart from descriptions of ROI/volume as ideas in the white paper without a verifiable context).
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.sportstensor.com/white-paper
  • Why sufficient / why not (one line): There is wording about ROI/volume, but no explicit model quality metrics/versions/datasets for a strict AI_3.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): There is a white paper/docs describing scoring/rewarding miners and the incentive mechanism.
  • Evidence: Tier‑1 — https://docs.sportstensor.com/white-paper
  • Why sufficient / why not (one line): The documentation contains a technical description of the mechanism and its stages.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Bittensor
  • Addresses/identifiers: Subnet 41
  • Evidence: Tier‑2 — https://taostats.io/subnets/41/chart ; Tier‑1 — https://docs.sportstensor.com/white-paper
  • Why sufficient / why not (one line): The white paper states that the tournament structure is proposed on Bittensor; the subnet identifier is confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: competition/recording of results and distribution of incentives to participants (miners) based on the quality of signals.
  • Evidence: Tier‑1 — https://docs.sportstensor.com/white-paper
  • Why sufficient / why not (one line): The white paper describes scoring and rewarding miners.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not proven that the mechanism cannot work without the blockchain; this is not substantiated in Tier‑1.
  • Evidence: Tier‑1 — https://docs.sportstensor.com/white-paper
  • Why sufficient / why not (one line): There is a description of the incentive mechanism, but without a test of 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 project 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 collateral/penalties 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.sportstensor.com/ Description of the project: a network for AI/ML models and competition between predictions.
Tier‑1 https://docs.sportstensor.com/white-paper White paper: scoring/rewarding miners and the incentive mechanism.
Tier‑1 https://dashboard.sportstensor.com/ Public dashboard/leaderboard (what you can touch).
Tier‑2 https://taostats.io/subnets/41/chart Subnet 41 on Bittensor (explorer/metrics).
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