SN 44. Rank 8 of 32 by emission
Score
TurboVision is Score's decentralized intelligence layer for live video and imagery.
In their own words · raw.githubusercontent.comSN44 Score turns sports footage into a play-by-play data feed, the way a press-box statistician logs every player's position, except the statisticians are competing computer-vision models and only the most accurate one per task is paid.
The commodity, explained from zero
The product is structured data pulled from video: where each player is in every frame, where the ball is, where the pitch lines fall, and who plays which role. The README calls it "structured, decision-ready data in real time", made from raw footage, "with early deployments focused on professional sports".
It has a price because the human version is slow and expensive. The older Score Vision repository, which the site still links as its documentation, puts manual annotation at $10 to $55 per minute of footage and says the goal is to cut that cost "by 10x to 100x". That page names four kinds of customer: clubs and leagues, broadcasters, betting operators and analytics providers.
Who buys today is not stated. The front page shows customer logos as images and demo clips of football, NFL and NBA footage, but names no customer in text and gives no numbers or dates.
Why it is on Bittensor at all
The stated change is cost. The older repository says distributing the computation across miners, with a lightweight check on their output, is what makes the 10x to 100x reduction possible. The current README says only that the network "pairs expert models with a global community of validators and miners". Neither page compares this with a company running the same models on its own servers, so whether decentralization, rather than the models, makes it cheaper is not settled.
How the work gets done
Miners, the statisticians, train a model, host it on Chutes (a separate Bittensor subnet that rents model hosting) and record its fingerprint on chain. Validators, the editors, pull a video challenge, build an answer key (real, or made by a segmentation model called SAM3), send frames to every eligible miner and score the replies. Each task, called an Element, has weighted sub-scores such as overlap with the answer key, player count, smoothness and role, gated by a minimum threshold and multiplied by a difficulty factor. The highest average per Element wins its share of the emission, the subnet's share of newly minted TAO; a copied model loses the tie to whichever was committed on chain first. Here the press-box comparison breaks: a club pays its statistician whether or not they are the league's best, while Score pays one winner per Element and nobody else.
How you would know it works
No dated artifact exists on the subnet's site. The front page carries demo videos with no dates or figures, the Console is an empty shell, and the evaluation reports and 2025 draft whitepaper sit in a repository folder nothing links to.
What is missing
There is no price list and no named customer in text. The README's link to the miner guide returns a 404; the guide and the scoring note with its worked table exist, in folders the README never points to. The site's Documentation link goes to the older score-vision repository, not the one the chain identity names. The chain contact hello@wearescore.com appears nowhere on the site, the discord field is empty, and there is no status page or support path beyond a contact form and GitHub issues.
Go deeper
Sources for this explainer
- https://www.wearescore.com/
- https://raw.githubusercontent.com/score-technologies/turbovision/main/README.md
- https://raw.githubusercontent.com/score-technologies/turbovision/main/scorevision/miner/op
- https://raw.githubusercontent.com/score-technologies/turbovision/main/notes/documentation/
- https://raw.githubusercontent.com/score-technologies/score-vision/main/README.md
Metaphor: a press-box statistician. Every claim is drawn from the evidence set or the subnet's own materials; "(inferred)" marks a conclusion rather than a quote. Corrections.
How we scored it
Four audiences, four questions each, scored on what a first-time reader can find in five minutes. Method in the rubric.
- subnet_name
- Score
- github_repo
- github.com
- subnet_contact
- hello@wearescore.com
- subnet_url
- wearescore.com
- discord
- not set
- description
- Making every camera intelligent
- additional
- not set
Stakers and validators●●●●● 2.3
Should I allocate here? · rank 27 of 32 for this audience
Q1What it is●●●●● 3
TurboVision is Score's decentralized intelligence layer for live video and imagery.
output is structured data from footage, no unit or price, chain description is the site headline
Q2Who it is for●●●●● 1
with early deployments focused on professional sports
is the only demand statement, no numbers, no named customers in text, the front page customer logos are images only, no dashboard
Q3How it resists gaming or fails●●●●● 2
pillar weights, baseline gate and difficulty multiplier with a worked table, copy protection in MINER.md, attack vectors in a draft whitepaper dated 2025-10-26, all in folders the README never links
Q4Identity and documentation●●●●● 3
identity 5 of 7 (discord and additional not set), github and url resolve, the site Documentation link points at the older score-vision repo rather than the chain github_repo, no staker page
Miners●●●●● 3.0
Can I compete, and what wins? · rank 25 of 32 for this audience
Q1What it is●●●●● 3
Miners publish models, deploy them to Chutes, and commit metadata on-chain.
a model answers validator challenge payloads per Element, schema only in code, the README link to MINER.md returns 404
Q2Who it is for●●●●● 3
Have GPU/cloud capacity for inference.
plus a p95 latency rule of 100 ms per frame on 2 vCPU, a funded Chutes developer account, no hardware table, registration cost not stated (burn 0.008 TAO)
Q3How it resists gaming or fails●●●●● 3
pillar scores times manifest weights, baseline theta, delta floor and beta with an example table, highest average wins and copy protection by commit block in MINER.md, no immunity or churn policy
Q4Identity and documentation●●●●● 3
step by step guide matching the current sv deploy-os-miner CLI, repo pushed 2026-08-26, no releases or changelog, the README links MINER.md at the repo root where it does not exist
Buyers and enterprises●●●●● 1.5
Can I use this today? · rank 26 of 32 for this audience
Q1What it is●●●●● 2
We’re building models that turn raw video into structured intelligence.
Console link opens a JS-only Score Dashboard shell, Let's Talk is a contact form, no product page, no endpoint, no example
Q2Who it is for●●●●● 2
Our solution serves four primary market segments.
clubs, broadcasters, betting operators and analytics providers named in the older repo the site links as Documentation, no pricing anywhere
Q3How it resists gaming or fails●●●●● 1
File issues or ideas in this repo.
and a contact form on the site are the only support paths, no status page, SLA or response expectation
Q4Identity and documentation●●●●● 1
no API reference in the repo or on the site, the get-started page is a contact form with no address, subnet_contact hello@wearescore.com appears nowhere on the site
Newcomers●●●●● 3.0
What is this and why does it matter? · rank 22 of 32 for this audience
Q1What it is●●●●● 4
Frame by frame, Score transforms how machines perceive movement, context, and causality
plain paragraph under Making Every Camera Intelligent, matching the chain description, subnet unmentioned
Q2Who it is for●●●●● 3
Score Vision aims to reduce these costs by 10x to 100x while dramatically improving speed and accuracy
against manual annotation, a concrete comparison but in the older repo, not on the site
Q3How it resists gaming or fails●●●●● 2
front page carries football, NFL and NBA demo videos with no dates or numbers, evaluation PDFs sit in an unlinked documentation folder, the 19MB model benchmark appears only in third-party posts
Q4Identity and documentation●●●●● 3
subnet_name Score matches We Are Score, description is a human phrase, url resolves, no about or learn page (the Documentation link leaves for GitHub)
How this score came to be. Verified means the scorer fetched the page and the words are on it; inferred means concluded from code, absence, or a third party. The link badge is a separate automated check made before publication.
Something wrong? Corrections of fact are applied as they arrive during the window; score disputes are batched at its close. How to file one · GitHub issue · email.