Skip to main content

Score Vision

Score Vision — 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).

Score Vision — an AI/Other | 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 (SN44) with open‑source miner/validator code for computer vision and video analysis tasks (focus — football game state recognition).
  • Who it’s for: Bittensor miner/validator operators and teams that want to participate in the CV compute/validation network; as an application layer — for video analytics scenarios.
  • Why onchain/token: as a subnet in Bittensor — onchain is needed for the incentive mechanics (weights/rewards); 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 Miner Setup / Validator Setup instructions and launching a miner/validator from the official repository.

How it works (very briefly)

  1. The user does: runs a miner that receives a video stream/frames and returns detections/tracks for the task.
  2. The system does: validators select frames and check the quality of the results (including via a lightweight validation approach).
  3. The user gets: a quality evaluation and the distribution of incentives among network participants (within the subnet mechanics).
  4. Where the blockchain is: the onchain part is the Bittensor subnet (netuid 44), where parameters/weights are recorded and incentives are distributed.
  5. 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 Score Vision
Also known as (aliases) Score, SN44, Subnet 44
Logo (logo) ../assets/433_score_logo.svg
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) native
Token contract Subnet netuid 44 (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) computer vision framework (video analysis)
Use‑case (use_case) football video analytics (GSR)
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

General project overview

Score Vision describes itself as a decentralized computer vision framework based on Bittensor (Subnet 44), focused on video processing and analysis. The project’s README describes the roles of miners/validators and an approach to “lightweight” validation of results, as well as the target application case — recognition of the game state in football (Game State Recognition).

Features/modules

  • Miner/validator base code for participating in the subnet.
  • Video processing architecture and verification of results by validators.
  • A described set of metrics and an evaluation methodology (at the level of a concept/description).

Typical scenarios

  • Scenario 1: an operator runs a miner → processes video/frames → receives an evaluation/reward within the subnet.
  • Scenario 2: an operator runs a validator → checks miners’ results → influences the distribution of incentives.

Getting started (wallet/network)

  • What you need: follow the Miner Setup / Validator Setup instructions in the official repository.
  • Network/chain: Bittensor (subnet netuid 44).
  • Fees: depend on participation in the Bittensor network and on hardware/infrastructure requirements.

Architecture/tech (non‑AI)

  • Components: miners (processing) + validators (verification) + Bittensor protocol mechanics (incentives/weights).
  • Where logic runs: video processing and models — offchain at the miners; evaluation/incentives and recording of parameters — via the onchain state of the Bittensor network.

Token/economics (expanded, no forecasts)

  • Incentive model: the subnet operates within Bittensor — the distribution of incentives depends on the quality of miners’ results and on the validation 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: not established per Tier‑1.
  • Threat model: typical risks for a subnet — manipulation of evaluation/sybil behavior; specific measures depend on validator implementations and network parameters.

Project status and timeline

  • Current status: active (there is a repository with code and a mainnet subnet netuid 44).
  • Roadmap: the roadmap section is given in the repository README.

Ecosystem/integrations

  • Where it’s actually used: the state of the subnet and its dynamics are observable via taostats (netuid 44).

AI component of the project

  • What is real AI here? Tier‑1 (README) describes a computer vision framework for video analytics (object detection/tracking and quality evaluation), with a claimed GSR case.
  • What is truly onchain? This is a Bittensor subnet (netuid 44) — the onchain layer is used for parameters/weights and the distribution of incentives.
  • 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): the existence of Tier‑2 “SCORE” profiles on aggregators without a Tier‑1 link between the token and the product; evaluating the quality of CV models requires reproducible metrics/results, not just a description of metrics.

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 working part (CV framework/subnet), not just an intent.
  • Evidence: Tier‑1 — https://github.com/score-technologies/score-vision
  • Why sufficient / why not (one line): when there is a Tier‑1 description of how the system works, the “intent” flag adds no signal.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): processing of video/frames for computer vision tasks and game state recognition (detections/tracking).
  • Evidence: Tier‑1 — https://github.com/score-technologies/score-vision
  • Why sufficient / why not (one line): the README describes the purpose and the processing/validation architecture.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The official repository contains reproducible instructions for launching a miner/validator (Miner Setup / Validator Setup).
  • Evidence: Tier‑1 — https://github.com/score-technologies/score-vision#miner-setup ; https://github.com/score-technologies/score-vision#validator-setup
  • Why sufficient / why not (one line): this is a reproducible “how‑to” artifact, analogous to a demo surface for a subnet.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://github.com/score-technologies/score-vision
  • Why sufficient / why not (one line): Tier‑1 contains a description of the metric/approach, but there are no recorded measurements/results with context to set 1.

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

  • AI_4 (decision): 1
  • Claim (one line): the README describes the architecture, the roles (miner/validator/subnet owner) and the validation stages.
  • Evidence: Tier‑1 — https://github.com/score-technologies/score-vision
  • Why sufficient / why not (one line): a tech description at the architecture level exists, although without details of models/versions.

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Bittensor
  • Addresses/identifiers: subnet netuid 44
  • Evidence: Tier‑1 — https://taostats.io/subnets/44/chart
  • Why sufficient / why not (one line): taostats records the existence of the subnet on the Bittensor network.

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

  • OC_2 (decision): 1
  • What useful logic is onchain: weights/incentives and subnet parameters are recorded as part of the Bittensor protocol mechanics.
  • Evidence: Tier‑1 — https://taostats.io/subnets/44/chart
  • Why sufficient / why not (one line): the subnet exists in an onchain network; the distribution of incentives is tied to the state of the network.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the trustless mechanics of distributing incentives/weights between miners and validators break down.
  • Evidence: Tier‑1 — https://docs.learnbittensor.org/subnets/understanding-subnets ; https://taostats.io/subnets/44/chart
  • Why sufficient / why not (one line): the “incentive network” model presupposes onchain recording and distribution of incentives.

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 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 mechanics on the project token.

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

  • TK_2 (decision): 1
  • Claim (one line): subnet economics distribute emissions/incentives among miners/validators and rely on the onchain mechanics of Bittensor (Dynamic TAO).
  • Evidence: Tier‑1 — https://docs.learnbittensor.org/subnets/understanding-subnets ; https://taostats.io/subnets/44/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): governance via 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 mechanics of 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://github.com/score-technologies/score-vision Description of the purpose (CV/video analysis) and the subnet architecture (miner/validator), including the validation methodology.
Tier‑1 https://github.com/score-technologies/score-vision#miner-setup Tier‑1: reproducible launch of a miner (what-to-run/how-to).
Tier‑1 https://github.com/score-technologies/score-vision#validator-setup Tier‑1: reproducible launch of a validator (what-to-run/how-to).
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/44/chart Onchain fact of the existence of Bittensor subnet netuid 44.
Tier‑2 https://www.coingecko.com/en/coins/score Reference “SCORE” profile and link navigation (not proof of the project’s token mechanics).
Tier‑2 https://coinmarketcap.com/currencies/score/ Reference “SCORE” profile and link navigation (not proof of the project’s token mechanics).

No comments to display

Back to top