DSperse is Bittensor subnet 2 (SN2), a project in the Inference and Compute lane. Proof that the model really ran
Subnet 2 is one of Bittensor's oldest slots, and it just changed its name: Omron is now DSperse, a zkML proving cluster that aims to hand you a cryptographic receipt proving an AI model actually ran your request.
It is an educational deep dive, not a recommendation to stake. For live price, pool depth, and performance, always open the live subnet page.
What is DSperse (SN2)?
DSperse is a network for verifiable AI inference. When a normal AI service answers a question, you have to take its word that the answer came from the model it claims to use. DSperse turns that promise into a proof: it runs the model and attaches a zero-knowledge proof showing the output really came from that specific model, untampered.
In plain English: It's like a tamper-evident seal for AI. Anyone can check the seal and confirm the answer came from the right model, without trusting the company that served it.
Centralized reference points: Hosted inference APIs (OpenAI, AWS, Google), trusted-hardware attestation
How miners and validators work
Like every Bittensor subnet, SN2 is a two-sided market: miners produce work, validators score it, and emissions follow those weights under the network’s dTAO economics.
- Miners run AI models that have been compiled into zero-knowledge circuits, generate the prediction, and return it together with a proof.
- Validators hand out the work, then verify each miner's zero-knowledge proof and score it on proof size and response time.
Mechanism and design
The miner and validator are native Rust binaries that talk over HTTP and QUIC. According to the subnet's repository, miners receive input data from validators, run custom AI models that have been converted into zero-knowledge circuits, and return the prediction along with a proof. Validators produce the input, distribute the requests, verify the authenticity of each returned proof, and score miners on cryptographic integrity, proof size, and response time. Because the heavy lifting is the proof rather than a giant GPU job, the design lets non-GPU machines participate, while still rewarding faster, more efficient proving systems.
The DSperse name points at the team's approach to a hard problem: proving a whole model is costly. As community write-ups describe it, DSperse leans on targeted verification, splitting a model into slices and proving only the critical ones rather than the entire pipeline, which cuts the proof cost and memory needed to make zkML practical. The repository reflects this in its handling of model slices and per-slice circuits.
There is a second thread here worth knowing about. The same proving capability backs Proof of Weights, where validators on other subnets can produce a proof that they ran their incentive mechanism correctly. The subnet's own documentation describes Subnet 2 positioning itself as an "execution layer" for that work, citing a capability of producing over 300,000 proofs per day. Treat that figure as the team's stated capacity rather than an independently measured number, but it captures the ambition: a general-purpose proving cluster other parts of the network can lean on.
Why the project exists
- The problem it solves: AI output is unauditable. When a model makes a financial call, a moderation decision, or an oracle reading, you cannot independently confirm which model ran or that nobody swapped the result. DSperse makes that checkable.
- The opportunity: Verifiable inference is a building block other systems can sit on top of, from on-chain oracles to AI used inside agreements where the parties do not trust each other. The new "DSperse" branding leans into this, positioning the subnet as a source of verifiable oracles for any computation.
- The Bittensor advantage: Generating zero-knowledge proofs is expensive, so it suits a decentralized cluster of miners competing on speed and efficiency. Bittensor's incentive mechanism pays for exactly that: a standing fleet of provers rather than one company's servers.
- Traction signals: Development is active. Inference Labs, the team behind the subnet, has raised over $6 million for verifiable AI, according to The Defiant. The codebase carries over 2,100 GitHub stars.
What stakers should check before buying alpha
Subnet storytelling is cheap. On-chain and product checks are not. Use the same framework as our subnet metrics guide:
| Check | Why |
|---|---|
| Real product / docs / repo | Separates shipping teams from narrative-only slots |
| Pool depth (TAO) | Your exit door: thin pools amplify slippage |
| Net flows (7d / 30d) | Under flow-based emissions, capital votes with its feet |
| Emission share | Whether the market is funding this subnet right now |
| Ownership concentration | Large holders can move a small alpha market |
| Immunity / deregistration | Post-immunity weak slots can lose the race (see immunity guide) |
Pull the live numbers on DSperse · SN2 rather than trusting any static screenshot in a blog post.
Risk factors
- Deregistration: Subnet 2 is well past its 4-month immunity window, so it is exposed to automatic deregistration if its EMA price sits at the bottom of the non-immune set. With recent net outflows and minimal current emission, this is the risk to watch.
- Adoption over demos: Verifiable inference is technically real, but the value depends on other systems actually consuming the proofs. A proving cluster needs paying demand, on-chain or off, to matter beyond the benchmark.
- Execution and rebrand risk: Renaming Omron to DSperse and narrowing toward verifiable oracles and targeted verification is a bet. The work is genuine, but the product framing is newer than the subnet, and reputational continuity has to carry across the name change.
- Concentration: Ownership of the alpha token is concentrated, with a high gini reading across the top positions. A few large positions moving in or out can swing a thin pool.
How this fits a TAO portfolio
Many holders keep a root vs subnet split: root for calmer TAO exposure, subnets like DSperse for thematic upside (and higher variance). If you use TaoScale, you can size SN2 from your wallet without handing over custody. See non-custodial staking.
- Live market: SN2 on TaoScale
- Browse and stake: /invest
- More subnet explainers: /blog/subnets
FAQ
What does DSperse do on Bittensor?
It's like a tamper-evident seal for AI. Anyone can check the seal and confirm the answer came from the right model, without trusting the company that served it.
What is the SN2 alpha token?
When you stake TAO into subnet 2, you receive that subnet’s alpha. Its price versus TAO moves with the subnet’s pool (see what is dTAO).
How do I research DSperse before staking?
Read the mechanism above, open the official repo/docs when available, then verify pool depth, flows, and activity on SN2. Cross-check with the metrics checklist.
Is this financial advice?
No. TaoScale publishes educational explainers and live tools. Decisions to stake are yours alone.
Not financial advice. Educational overview of DSperse (SN2) compiled from public project materials and ecosystem documentation. Mechanisms and market structure change, so verify live data and official sources before acting.
