With the amount of new subnets being added it can be hard to get up to date information across all subnets, so data may be slightly out of date from time to time

Subnet 02

DaniLabs

Subnet stats · Subnet

● Loading…
Alpha price
–
 
Market cap
–
 
Price (τ) & daily volume
Loading price history…
Daily emission split
Pool depth (TAO vs alpha value)
24h trading flow
What do these numbers mean?
Alpha price
TAO per alpha token, calculated from the subnet's on-chain pool (TAO reserve ÷ alpha reserve).
Market cap
Price × total alpha issued (alpha in pool + alpha outstanding). FDV = price × 21M max supply.
TAO liquidity
TAO currently held in the subnet's pool.
Alpha outstanding
Alpha held outside the pool (staked to validators/miners/owner).
Alpha emission / day
Alpha emitted to participants each day (on-chain), valued in TAO at the current price.
TAO injected / day
TAO the network adds to this subnet's pool each day (on-chain).
Net TAO flow / day
Smoothed (EMA) net TAO staked minus unstaked per day.
Neurons
Registered UIDs / maximum UIDs on this subnet.
Neuron reg. cost
Current on-chain burn (TAO) to register one miner/validator UID on this subnet. This is not the cost of creating a subnet.
Sources: Bittensor chain (Finney, direct read) · tao.com · TaoMarketCap · TAO/USD: CoinGecko

ABOUT

What exactly does it do?

DaniLabs is Bittensor Subnet 2. The name stands for Distributed Accelerated Neural Intelligence, and the project’s tagline is “Intelligence, distributed.” DaniLabs is developing an inference subnet: a network focused on running AI models, so that developers and applications can send a request and get a useful response back.

Three design priorities guide how the network and the experience of using it are being built:

  • No data retention (your data): the network is being designed so that prompts and responses are processed without being stored after a request.
  • Fast responses (your time): speed is a core priority, optimising the time from a request to a useful response.
  • Low-cost inference (your budget): bringing down the cost of inference for developers and applications, with pricing to take shape alongside the offering.

DaniLabs took over Subnet 2 on 16 October 2026 under an agreement with Inference Labs, and the subnet’s on-chain name changed to DaniLabs shortly afterwards. The project describes the service as in development. Its first public subnet code, published on 21 October 2026, is validator software: validators are being built to score miners on latency, token throughput, completed requests and availability, so that generation speed alone does not decide a miner’s reward. Since 27 October 2026 the DaniLabs validator has been running in production on the subnet, with miner rewards burned for now while its scoring is verified.

DaniLabs is Bittensor Subnet 2. The name stands for Distributed Accelerated Neural Intelligence, and the project’s tagline is “Intelligence, distributed.” DaniLabs is developing an inference subnet: a network focused on running AI models, so that developers and applications can send a request and get a useful response back.

Three design priorities guide how the network and the experience of using it are being built:

  • No data retention (your data): the network is being designed so that prompts and responses are processed without being stored after a request.
  • Fast responses (your time): speed is a core priority, optimising the time from a request to a useful response.
  • Low-cost inference (your budget): bringing down the cost of inference for developers and applications, with pricing to take shape alongside the offering.

DaniLabs took over Subnet 2 on 16 October 2026 under an agreement with Inference Labs, and the subnet’s on-chain name changed to DaniLabs shortly afterwards. The project describes the service as in development. Its first public subnet code, published on 21 October 2026, is validator software: validators are being built to score miners on latency, token throughput, completed requests and availability, so that generation speed alone does not decide a miner’s reward. Since 27 October 2026 the DaniLabs validator has been running in production on the subnet, with miner rewards burned for now while its scoring is verified.

PURPOSE

What exactly is the 'product/build'?

What exists today

DaniLabs is at an early stage. Its website, danilabs.ai, sets out the idea and the three design priorities, labels the service “in development”, and offers an email sign-up for launch and progress updates. Announcements are posted on X at @danilabsai.

Subnet validator code (public since 21 October 2026)

The subnet repository named in the on-chain identity, github.com/DaniLabsAI/subnet, is now public. It holds the DaniLabs validator software: the code that is to evaluate miner performance, calculate scores and submit weights to Bittensor. According to its README, the validator is being developed to:

  • track subnet state and link registered miners to their on-chain identities;
  • check the source, format and freshness of miners’ performance reports, rejecting invalid or duplicate submissions;
  • evaluate inference performance using latency, token throughput, completed requests and availability;
  • turn eligible miner scores into weights and submit them to Bittensor.

Validator reports are meant to carry operational measurements only, without customer prompts or generated responses. The first executable release is a read-only chain observer pilot (commands status, watch and shadow) that checks finalized subnet identities and validator state on a CPU-only host; it opens no wallet and does not submit weights. The scoring formula, eligibility rules and measurement definitions are still being developed and are to be documented and tested in the repository before live weight submission is enabled.

Localnet validator pilot (since 24 October 2026)

The repository now also contains a pilot of how the validator is to be operated, run on a private local development chain. It adds an isolated signer, the only part allowed to set weights and restricted to that development chain and a development key; a supervised worker process that holds no private key; and an automatic updater that installs new worker releases in stages, runs tests and health checks, and rolls a failing update back. In this pilot the validator directs its weight to the subnet owner’s UID and checks that the result settles on chain as expected. Changes are tested on this local chain before they are deployed to Finney, Bittensor’s main network.

Signer key custody and recovery (added 26 October 2026)

The signer now has one fixed transaction policy: it can only set the full weight to the verified subnet owner’s UID, and the worker and updater cannot change the destination, weight, subnet or payload. The validator hotkey is kept as a standard encrypted Bittensor keyfile, and no coldkey private key is needed. Every signer start is locked: the key is held in memory only after a custodian unlocks it on the host. An optional recovery service can unlock the signer automatically after a reboot or crash, using a password stored in Oracle Cloud (OCI) Secret Management, and a persistent emergency lock overrides that recovery.

Production validator on Finney (since 27 October 2026)

On 27 October 2026 DaniLabs announced that its validator switchover was live on Subnet 2. The production validator now runs on Finney in a 100% burn mode: it sets the full weight to the subnet owner’s UID, so miner incentive is burned for now, and it checks separately that the weight row and the burn settle on chain.

Candidate scoring (logged, not yet rewarded)

Once per chain epoch the validator fetches signed performance measurements from the DaniLabs API, verifies the signature against a pinned public key, and checks each miner’s UID, hotkey and registration block against finalized chain state, rejecting stale, duplicate or inconsistent reports. Reports carry no customer prompts or responses. The current scoring policy (performance v2) weights decode speed in tokens per second at 50%, time to first token at 35%, completion reliability at 10% and gateway-to-miner round-trip time at 5%, measured against per-model targets (initially 300 tokens per second and 500 ms to first token for openai/gpt-oss-20b). The resulting candidate weights are logged alongside the burn but are not yet used for rewards: token usage is still reported by the miners themselves, so scores stay ineligible until token counts and correctness can be verified independently.

Other components

The DaniLabs GitHub organisation (github.com/DaniLabsAI) also lists:

  • Service: hosted backend services and APIs.
  • Platform: the frontend website and application.
  • Miner kit (ManagedVNetIR): all miner software, including a Rust miner kit, onboarding, a managed inference runtime and streaming. Miners will use this separate kit rather than the validator repository.

The service, platform and miner-kit repositories are not yet publicly visible.

What exists today

DaniLabs is at an early stage. Its website, danilabs.ai, sets out the idea and the three design priorities, labels the service “in development”, and offers an email sign-up for launch and progress updates. Announcements are posted on X at @danilabsai.

Subnet validator code (public since 21 October 2026)

The subnet repository named in the on-chain identity, github.com/DaniLabsAI/subnet, is now public. It holds the DaniLabs validator software: the code that is to evaluate miner performance, calculate scores and submit weights to Bittensor. According to its README, the validator is being developed to:

  • track subnet state and link registered miners to their on-chain identities;
  • check the source, format and freshness of miners’ performance reports, rejecting invalid or duplicate submissions;
  • evaluate inference performance using latency, token throughput, completed requests and availability;
  • turn eligible miner scores into weights and submit them to Bittensor.

Validator reports are meant to carry operational measurements only, without customer prompts or generated responses. The first executable release is a read-only chain observer pilot (commands status, watch and shadow) that checks finalized subnet identities and validator state on a CPU-only host; it opens no wallet and does not submit weights. The scoring formula, eligibility rules and measurement definitions are still being developed and are to be documented and tested in the repository before live weight submission is enabled.

Localnet validator pilot (since 24 October 2026)

The repository now also contains a pilot of how the validator is to be operated, run on a private local development chain. It adds an isolated signer, the only part allowed to set weights and restricted to that development chain and a development key; a supervised worker process that holds no private key; and an automatic updater that installs new worker releases in stages, runs tests and health checks, and rolls a failing update back. In this pilot the validator directs its weight to the subnet owner’s UID and checks that the result settles on chain as expected. Changes are tested on this local chain before they are deployed to Finney, Bittensor’s main network.

Signer key custody and recovery (added 26 October 2026)

The signer now has one fixed transaction policy: it can only set the full weight to the verified subnet owner’s UID, and the worker and updater cannot change the destination, weight, subnet or payload. The validator hotkey is kept as a standard encrypted Bittensor keyfile, and no coldkey private key is needed. Every signer start is locked: the key is held in memory only after a custodian unlocks it on the host. An optional recovery service can unlock the signer automatically after a reboot or crash, using a password stored in Oracle Cloud (OCI) Secret Management, and a persistent emergency lock overrides that recovery.

Production validator on Finney (since 27 October 2026)

On 27 October 2026 DaniLabs announced that its validator switchover was live on Subnet 2. The production validator now runs on Finney in a 100% burn mode: it sets the full weight to the subnet owner’s UID, so miner incentive is burned for now, and it checks separately that the weight row and the burn settle on chain.

Candidate scoring (logged, not yet rewarded)

Once per chain epoch the validator fetches signed performance measurements from the DaniLabs API, verifies the signature against a pinned public key, and checks each miner’s UID, hotkey and registration block against finalized chain state, rejecting stale, duplicate or inconsistent reports. Reports carry no customer prompts or responses. The current scoring policy (performance v2) weights decode speed in tokens per second at 50%, time to first token at 35%, completion reliability at 10% and gateway-to-miner round-trip time at 5%, measured against per-model targets (initially 300 tokens per second and 500 ms to first token for openai/gpt-oss-20b). The resulting candidate weights are logged alongside the burn but are not yet used for rewards: token usage is still reported by the miners themselves, so scores stay ineligible until token counts and correctness can be verified independently.

Other components

The DaniLabs GitHub organisation (github.com/DaniLabsAI) also lists:

  • Service: hosted backend services and APIs.
  • Platform: the frontend website and application.
  • Miner kit (ManagedVNetIR): all miner software, including a Rust miner kit, onboarding, a managed inference runtime and streaming. Miners will use this separate kit rather than the validator repository.

The service, platform and miner-kit repositories are not yet publicly visible.

WHO

Team Info

Team

DaniLabs is led by Dan (@opendansor on X). According to Inference Labs, Dan joined its team from the Opentensor Foundation (OTF) and his applied research helped scale DSperse, the system previously run on Subnet 2. He describes himself as the architect of DSperse and links its research paper, “DSperse: A Framework for Targeted Verification in Zero-Knowledge Machine Learning” (arXiv 2508.06972). Announcing the move, he wrote that his subnet journey started on SN2 and that he is now leading its next chapter. The on-chain contact is [email protected].

On 27 October 2026 DaniLabs announced that engineer Xen (@xen43 on X) had joined the team to build out its inference platform and infrastructure, with a focus on speed, reliability and keeping costs low.

Subnet ownership

On 16 October 2026 Inference Labs announced that it had entered into an agreement for Dan to take over Subnet 2 as DaniLabs and lead its direction and development, focused on fast, affordable AI inference. The subnet’s registration dates from block 2,734,060 (April 2024) and its owner coldkey (5EcYQ3W77ndrmMWdvVQusoFqY8doxfP3U2zrh7xZQiaz7avY) is unchanged; the on-chain identity was updated to DaniLabs, with the new website, GitHub and X links, on 18 October 2026.

Community

Follow the build on X at @danilabsai and sign up for updates at danilabs.ai. DaniLabs runs its own Discord server (linked above, invite shared by @danilabsai on X on 30 October 2026); general subnet discussion also takes place on the main Bittensor Discord.

Team

DaniLabs is led by Dan (@opendansor on X). According to Inference Labs, Dan joined its team from the Opentensor Foundation (OTF) and his applied research helped scale DSperse, the system previously run on Subnet 2. He describes himself as the architect of DSperse and links its research paper, “DSperse: A Framework for Targeted Verification in Zero-Knowledge Machine Learning” (arXiv 2508.06972). Announcing the move, he wrote that his subnet journey started on SN2 and that he is now leading its next chapter. The on-chain contact is [email protected].

On 27 October 2026 DaniLabs announced that engineer Xen (@xen43 on X) had joined the team to build out its inference platform and infrastructure, with a focus on speed, reliability and keeping costs low.

Subnet ownership

On 16 October 2026 Inference Labs announced that it had entered into an agreement for Dan to take over Subnet 2 as DaniLabs and lead its direction and development, focused on fast, affordable AI inference. The subnet’s registration dates from block 2,734,060 (April 2024) and its owner coldkey (5EcYQ3W77ndrmMWdvVQusoFqY8doxfP3U2zrh7xZQiaz7avY) is unchanged; the on-chain identity was updated to DaniLabs, with the new website, GitHub and X links, on 18 October 2026.

Community

Follow the build on X at @danilabsai and sign up for updates at danilabs.ai. DaniLabs runs its own Discord server (linked above, invite shared by @danilabsai on X on 30 October 2026); general subnet discussion also takes place on the main Bittensor Discord.

FUTURE

Roadmap

DaniLabs has not published a dated roadmap. Its website describes the work in three stages:

  • 01 – The priorities (defined): no data retention, speed and cost guide the design of DaniLabs.
  • 02 – The subnet (in development): developing the inference subnet; technical details will follow as the design takes shape.
  • 03 – The next chapter (ahead): future announcements and ways to participate will be shared on the DaniLabs X account.

Progress so far

  • Done (21–22 October 2026): subnet validator repository made public, with a read-only chain observer pilot and an operator guide.
  • Status update (@danilabsai, 22 October 2026): chain identity updated, coordinating with validators, code migration under way with integration news to follow, onboarding new team members and talking with potential customers.
  • Done (24 October 2026): localnet validator pilot added, with an isolated signer limited to a private development chain, a keyless supervised worker and a staged auto-updater with health checks and rollback, plus a localnet operator guide.
  • Done (26 October 2026): encrypted hotkey custody with a signer that always starts locked and a fixed signing policy, optional automatic recovery through OCI Secret Management with a persistent emergency lock, and a signer custody and activation guide.
  • Done (27 October 2026): validator switchover live on SN2: the production validator runs on Finney in 100% burn mode, and signed performance reports are scored under a documented policy (performance v2), with candidate weights logged only. Engineer Xen (@xen43) joined the team.
  • Next: independent verification of miner token usage and correctness, then moving rewards from the burn to scored miners.
  • Later: the backend service, platform and Rust miner kit repositories are to be made public as they become ready.

DaniLabs has not published a dated roadmap. Its website describes the work in three stages:

  • 01 – The priorities (defined): no data retention, speed and cost guide the design of DaniLabs.
  • 02 – The subnet (in development): developing the inference subnet; technical details will follow as the design takes shape.
  • 03 – The next chapter (ahead): future announcements and ways to participate will be shared on the DaniLabs X account.

Progress so far

  • Done (21–22 October 2026): subnet validator repository made public, with a read-only chain observer pilot and an operator guide.
  • Status update (@danilabsai, 22 October 2026): chain identity updated, coordinating with validators, code migration under way with integration news to follow, onboarding new team members and talking with potential customers.
  • Done (24 October 2026): localnet validator pilot added, with an isolated signer limited to a private development chain, a keyless supervised worker and a staged auto-updater with health checks and rollback, plus a localnet operator guide.
  • Done (26 October 2026): encrypted hotkey custody with a signer that always starts locked and a fixed signing policy, optional automatic recovery through OCI Secret Management with a persistent emergency lock, and a signer custody and activation guide.
  • Done (27 October 2026): validator switchover live on SN2: the production validator runs on Finney in 100% burn mode, and signed performance reports are scored under a documented policy (performance v2), with candidate weights logged only. Engineer Xen (@xen43) joined the team.
  • Next: independent verification of miner token usage and correctness, then moving rewards from the burn to scored miners.
  • Later: the backend service, platform and Rust miner kit repositories are to be made public as they become ready.

NEWS

Announcements

Latest on X

Loading…