The chart follows the alpha price in τ. Each period starts at its opening price and steps through the mechanisms below, in a fixed order, to its closing price: a step that rises pushed the price up, one that falls pushed it down, and its height is how far it moved the price. A thin line carries each close into the next period’s open; it is dashed where the two differ. The faint candle behind each period is the market’s own open, high, low and close, for context.

With many periods on screen (90 days, or hours), the steps would be too thin to read, so the chart draws the price as a line instead and colours each period by the mechanism that moved it most. Hover a period for the full step-by-step breakdown.

Protocol buy: The chain spending excess emission TAO to buy alpha from the pool. A permanent protocol buyback; it pushes the price up.
Root sell: Root-dividend claims sold into the pool; they push the price down.
User buy / sell: Staking into and unstaking from this subnet.
Cross-subnet: Swaps from other subnets routed through this pool.
Residual: What the decomposition cannot attribute to a mechanism. It is always shown, never folded into another part.

Not here, because they do not move the spot price: the per-block TAO injection into the pool, and burns.

All figures are log changes, not simple percentage changes, so the parts add up exactly to the total; on big moves the two differ (a 10% log fall is a 9.5% price fall).

Today so far

2026-11-10 UTC, as of ≈21:27 UTC (block 9,478,525)

Price, today so far: 0.004685 τ
Volume, today so far: 9.00 τ
Market cap incl. burned, today so far: 18.46K τ
TAO in pool, today so far: 12.53K τ
Emission share, today so far: —not available yet

The day isn’t over yet, so these figures keep changing. They are in no daily total, average or rank.

Subnet Configuration

Pool & Mechanism

AMM Pool

Balancer

Mechanism

dTAO

Access

Registration

Open

Neurons

64/64Competitive

Validators

7/6457 open

Economics

Owner Cut

18.00%

Weights

Commit-Reveal

Enabled (v3, 3 epochs)

Liquid Alpha

Disabled

Weights Version

Weights Range

1–65535

Timing

Tempo

360~1.2h

Immunity Period

1,466~4.9h

Activity Cutoff

5,000~16.7h

Market & Economics

Market

Market Cap

10.10K τ

FDV

31.00K τ

TVL

25.07K τ

Lifetime Volume

430.78K τ

Holders

1,146−0.52% 7d·+2.69% 30d

Circulating alpha

2,155,735.8465 μ

Owner Locked

3,870.5371 μ(0.18% of circulating)Perpetual

14d price

Holder & circulating-alpha metrics as of 2026-11-10 00:00 UTC (daily close)

Revenue / Recycle

No recycle

last day

Emissions

0.00%of network emissions

TAO emitted to this subnet

Sent into its pool each day: its share of network emissions

0.0000 τ/day

0 τ per day

Daily distribution

Alpha paid out each day, valued at the pool price

7,200.0000 μ/day

≈ 33.7338 τ·33.7338 τ per day

Miners43.85%

3,157.0612 μ ≈ 14.7916 τ/day

Validators38.15%

2,746.9718 μ ≈ 12.8702 τ/day

Owner18.00%

1,295.9670 μ ≈ 6.0719 τ/day

Stake 1,000 τ here

219.1648 μ/day≈ 1.0268 τ·1.0268 τ per day

From the validator share, before commission

45.19%staker APY

· 30d avg 45.19% · Stable

90d

Pool emits 1.0000 μ/block at 0.004685 τ/μ. Yield varies with stake weight, pool price, and emission rate.

For Miners

43.85% of emission

Slots

64/64Competitive

Burn Cost

0.0005 τ

Est. per Miner

22.5504 μ/epoch≈ 0.1057 τ

Pool / Epoch

157.8531 μ≈ 0.7396 τ

For Validators & Stakers

38.15% of emission

Validator Slots

7/6457 open

Est. per Validator

19.6212 μ/epoch≈ 0.0919 τ

Registration Activity

Neuron registration trends

This Interval

24h: 0 registrations (0 burn · 0 PoW)

Target / Interval

Slots Available

Competitive

64/64

Neurons

Development Activity

backend-developers-ltd/ComputeHordePython

253528 contributors8 commits/30dLast commit 0d ago

MIT

Top Contributors

andreea-popescu-reef301

mzukowski-reef183

olzhasar-reef123

piotr-figwer-reef115

slawomir-gorawski-reef60

agoncharov-reef49

Recent Releases

library-v0.0.2715d ago library-v0.0.26454d ago library-v0.0.25490d ago v0.0.1606d ago library-v0.0.23627d ago

What Compute Horde does

Bittensor validators need GPU resources to validate other subnets, but access to reliable, scalable computing is limited. Running validators on centralized cloud services creates dependency on third parties and increases operational costs. ComputeHorde addresses this by creating a decentralized network where miners contribute GPU capacity through executors—individual compute instances that perform validation tasks. Validators access this capacity through a stake-proportional allowance system, ensuring fair resource distribution without centralized intermediaries. The subnet uses a trusted miner (an unregistered validator-operated GPU) to verify miner work integrity, collateral-based slashing to enforce honesty, and hardware class specifications to match job requirements to available resources.

Auto-generated from the GitHub repository and may not reflect the latest changes.

About

active

ComputeHorde is a Bittensor subnet (netuid 12) that provides decentralized, scalable GPU computing power to validators across the Bittensor ecosystem. It enables miners to offer GPU resources through executors, which validators use to run synthetic validation tasks and organic jobs from other subnets, with a scoring mechanism based on allowance blocks, executor uptime, and hardware class matching.

How it works

ComputeHorde consists of four main components: (1) Facilitator - gateway for organic requests from other subnets' validators, routes tasks via WebSocket protocol; (2) Validator - receives organic jobs, distributes to miners, uses trusted miner (unregistered, runs on separate GPU) for cross-validation of results, integrates with collateral smart contracts for slashing; (3) Miner - accepts job requests from validators, manages executors, can deposit collateral for organic job eligibility; (4) Executor - Docker container instances spawned by miners to perform individual tasks with restricted network access (communication with miner, Docker image download, job data transfer only). Jobs flow through three pathways: synthetic (pre-known results for miner assessment), organic (black-box Docker execution), and streaming organic (whitelisted images for service deployment). Validators communicate with facilitator via WebSocket at /ws/v0/ using authentication, job requests, status updates, and heartbeat messages.

Incentive mechanism

The allowance pool recalculates every block reflecting executor count and validator stake changes. Validators spend specific allowance blocks to cover job runtime. During scoring, blocks must be fresh, unspent, and sufficient; overspending voids incentives.

If a miner lowers executor count, tied allowance blocks are invalidated. Validators score all miners' work regardless of who paid, as long as jobs fit valid allowance blocks. Hardware class weights adjust final scores based on network demand.

The dancing bonus (10% boost on coldkey score) triggers when main hotkey changes from previous cycle, encouraging variance to prevent weight-copying.

The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository (github.com, opens in a new tab, external site)

On-Chain Identitysigned on-chain by subnet owner

Compute Horde

Mu · Greek letter · pronounced “mu”

Trusted compute for bittensor validators

Owner: 5ELzh…6PCp
Hotkey: 5ELzh…6PCp
Owner Cut: 18.00%
Contact: ~

Registered: 2y 9mo ago(Jan 30, 2024)
Block: 2,256,433
Slot history: Every subnet in SN12
Neurons: 64/64
Tempo: 360 blocks

Website

URL: https://computehorde.io/ (computehorde.io, opens in a new tab, external site)
Status: Up200
TLS: Valid
Title: ComputeHorde (Subnet 12)
Checked: 2026-11-10 04:01 UTC

Changes (1)

2026-10-13 08:00 UTCUp200ComputeHorde (Subnet 12)

Subnet History

SubnetIdentitySet 2026-10-12 15:18 UTC

Block 9,267,976Extrinsic

SubnetIdentitySet 2025-03-07 18:27 UTC

Block 5,077,770Extrinsic

Subnet registered 2024-01-30 17:18 UTC

Block 2,256,433Extrinsic

Recent Activity

SubnetIdentitySet Block 9,267,976 Extrinsic2026-10-12 15:18 UTC
SubnetIdentitySet Block 5,077,770 Extrinsic2025-03-07 18:27 UTC
NetworkAdded Block 2,256,433 Extrinsic2024-01-30 17:18 UTC

This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository (github.com, opens in a new tab, external site) for the latest instructions.

Hardware Requirements

Miner

GPURequired

GPU ModelA6000

OSUbuntu Server

Not yet verified: Storage, Notes

Validator

GPURequired

GPU ModelA6000

OSLinux

Validator uses trusted miner for cross-validation of organic job results, requires two S3 buckets for LLM data sharing, and runs on separate standard machine for validation and weight-setting.

Machine-extracted from the subnet's repository docs; may be wrong or out of date. Check the repository before buying or renting hardware. Open the repository (github.com, opens in a new tab, external site) · Extracted 28 Sep 2026

Miner Setup

Execute installation script from local machine with wallet files. Replace SSH_DESTINATION with server connection info (username@ip) and HOTKEY_PATH with path to hotkey.

curl -sSfL https://github.com/backend-developers-ltd/ComputeHorde/raw/master/install_miner.sh | bash -s - production SSH_DESTINATION HOTKEY_PATH

Restart services after configuration changes or deployment(optional)

docker compose down --remove-orphans && docker compose up -d

Verify miner is reachable from different machine. Port and address from metagraph. Should return HTTP/1.1 200 OK.(optional)

curl {ADDRESS}:{PORT}/admin/login/ -i

Check jobs and outcomes via database query(optional)

docker-compose exec miner-runner docker-compose exec db psql postgres -U postgres -c 'select * from miner_acceptedjob order by id desc;'

Validator Setup

Set up trusted miner for cross-validation of organic task results

See validator's README for setting up trusted miner

Set up S3 buckets for sharing LLM data (small text files)

Prepare two S3 buckets

Set environment variables for trusted miner connection on local machine with wallet files

export TRUSTED_MINER_ADDRESS=... && export TRUSTED_MINER_PORT=...

Execute installation script from local machine. Replace SSH_DESTINATION with server connection info and HOTKEY_PATH with path to hotkey.

curl -sSfL https://github.com/backend-developers-ltd/ComputeHorde/raw/master/install_validator.sh | bash -s - SSH_DESTINATION HOTKEY_PATH

Restart validator after configuration changes(optional)

docker compose down --remove-orphans && docker compose up -d

View validator logs for troubleshooting(optional)

docker compose logs

No hardware? Back this subnet by staking instead New to mining? Start with the setup guide Validator setup guide

Day (UTC)

2026-11-09

0.00%

2026-11-08

0.00%

2026-11-07

0.00%

2026-11-06

0.00%

2026-11-05

0.00%

2026-11-04

0.00%

2026-11-03

0.00%

2026-11-02

0.00%

2026-11-01

0.00%

2026-10-31

0.00%

2026-10-30

0.00%

2026-10-29

0.00%

2026-10-28

0.00%

2026-10-27

0.00%

2026-10-26

0.00%

2026-10-25

0.00%

2026-10-24

0.00%

2026-10-23

0.00%

2026-10-22

0.00%

2026-10-21

0.00%

2026-10-20

0.00%

2026-10-19

0.00%

2026-10-18

0.00%

2026-10-17

0.00%

2026-10-16

0.00%

2026-10-15

0.00%

2026-10-14

0.00%

2026-10-13

0.00%

2026-10-12

0.00%

2026-10-11

0.00%

2026-10-10

0.00%

2026-10-09

0.00%

2026-10-08

0.00%

2026-10-07

0.00%

2026-10-06

0.00%

2026-10-05

0.00%

2026-10-04

0.00%

2026-10-03

0.00%

2026-10-02

0.00%

2026-10-01

0.00%

2026-09-30

0.00%

2026-09-29

0.00%

2026-09-28

0.00%

2026-09-27

0.00%

2026-09-26

0.00%

2026-09-25

0.00%

2026-09-24

0.00%

2026-09-23

0.00%

2026-09-22

0.00%

2026-09-21

0.00%

2026-09-20

0.00%

2026-09-19

0.00%

2026-09-18

0.00%

2026-09-17

0.00%

2026-09-16

0.00%

2026-09-15

0.00%

2026-09-14

0.00%

2026-09-13

0.00%

2026-09-12

0.00%

2026-09-11

0.00%

2026-09-10

0.00%

2026-09-09

0.00%

2026-09-08

0.00%

2026-09-07

0.00%

2026-09-06

0.00%

2026-09-05

0.00%

2026-09-04

0.00%

2026-09-03

0.00%

2026-09-02

0.00%

2026-09-01

0.00%

2026-08-31

0.00%

2026-08-30

0.00%

2026-08-29

0.00%

2026-08-28

0.00%

2026-08-27

0.00%

2026-08-26

0.00%

2026-08-25

0.00%

2026-08-24

0.00%

2026-08-23

0.00%

2026-08-22

0.00%

2026-08-21

0.00%

2026-08-20

0.00%

2026-08-19

0.00%

2026-08-18

0.00%

2026-08-17

0.00%

2026-08-16

0.00%

2026-08-15

0.00%

2026-08-14

0.00%

2026-08-13

0.00%

2026-08-12

0.00%

What moved the price

Overview

Today so far

Subnet Configuration

Market & Economics

For Miners

For Validators & Stakers

Registration Activity

Development Activity

What Compute Horde does

About

Website

Subnet History

Recent Activity

Participate

Hardware Requirements

Miner Setup

Validator Setup

What moved the price

Today so far

Subnet Configuration

Market & Economics

For Miners

For Validators & Stakers

What Compute Horde does

About

Website

Subnet History

Hardware Requirements

Miner Setup

Validator Setup