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-09 UTC, as of ≈23:43 UTC (block 9,472,006)

Price, today so far: 0.03015 τ
Volume, today so far: 873.72 τ
Market cap incl. burned, today so far: 10.56K τ
TAO in pool, today so far: 1.70K τ
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

256/256Competitive

Validators

4/6460 open

Economics

Owner Cut

18.00%

Weights

Commit-Reveal

Enabled (v3, 1 epochs)

Liquid Alpha

Disabled

Weights Version

Weights Range

1–65535

Timing

Tempo

360~1.2h

Immunity Period

5,000~16.7h

Activity Cutoff

5,000~16.7h

Market & Economics

Market

Market Cap

7,399.1374 τ

FDV

12.26K τ

TVL

3,392.7975 τ

Lifetime Volume

78.52K τ

Holders

272

14d price

Revenue / Recycle

498.37×

last day · Net positive

Emissions

0.00%of network emissions

Emission history is being recalculated from on-chain allocation.

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

≈ 217.1084 τ·217.1084 τ per day

Miners63.49%

4,571.4378 ъ ≈ 137.8469 τ/day

Validators18.51%

1,332.5952 ъ ≈ 40.1830 τ/day

Owner18.00%

1,295.9670 ъ ≈ 39.0785 τ/day

Stake 1,000 τ here

785.5436 ъ/day≈ 23.6872 τ·23.6872 τ per day

From the validator share, before commission

335,678,834,817,284,160,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00%staker APY

· 30d avg 335,678,834,817,284,160,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000,000.00%

90d

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

For Miners

63.49% of emission

Slots

256/256Competitive

Burn Cost

0.0012 τ

Est. per Miner

—

Pool / Epoch

228.5719 ъ≈ 6.8923 τ

For Validators & Stakers

18.51% of emission

Validator Slots

4/6460 open

Est. per Validator

16.6574 ъ/epoch≈ 0.5023 τ

Registration Activity

Neuron registration trends

This Interval

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

Target / Interval

Slots Available

Competitive

256/256

Neurons

256

Development Activity

carbonphysicsai/CarbonPython

726 contributors4,331 commits/30dLast commit 0d ago

NOASSERTION

Top Contributors

Recent Releases

worker-images-v524d agopre worker-images-v425d ago worker-images-v332d ago worker-images-v232d ago worker-images-v133d ago

What Carbon does

Physics-informed optimization tasks—predicting battery aging, designing thermal systems, optimizing mechanical components—require both specialized domain knowledge and rigorous validation. Centralized approaches struggle to scale research participation and validation capacity. A decentralized network of researchers (miners) and evaluators (validators) allows distributed development of strategies with verifiable, independent scoring on shared benchmarks.

Carbon implements this as a Bittensor subnet where miners develop neural network strategies locally, practice on public cases, and submit frozen candidates to validators. Validators independently reconstruct each strategy using pinned software and validator-controlled randomness, score results on hidden benchmark cases, and publish performance rankings to the chain. Miners are rewarded based on strategy quality, while validators are incentivized to maintain rigorous evaluation standards.

The system enforces reproducibility through deterministic reconstruction settings, isolates miner research from validator evaluation logic, and supports multi-validator submission so strategies are verified across independent evaluators.

Commitment transactions optionally bind submissions to the chain, creating an auditable record of what was submitted and when.

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

About

active

Carbon is a Bittensor subnet (netuid 567) for AI research and optimization. It provides a platform where miners develop and submit neural network strategies that are reconstructed and evaluated by validators on hidden benchmark cases. The subnet enables distributed research on physics-informed optimization tasks like battery aging and thermal design, with miners receiving rewards based on the quality of their submitted models.

How it works

Carbon is a distributed research optimization subnet. Miners use a local Control Center (Python HTTP server) to run research campaigns driven by AI agents (Graphite, custom MCP agents, or Hermes). Miners connect to inference providers (Engy, Chutes) and computational backends (CPU, GPU, remote SSH-Docker).

They develop strategies, practice on public cases, freeze candidates, and submit to validators through an authenticated HTTPS intake. Validators run a persistent daemon that admits submissions via btauth/1 authentication, binds submissions to replay journals and per-hotkey windows, reconstructs strategies on declared GPU or CPU backends with validator-controlled randomness, scores results on hidden cases, and publishes weights to the chain under owner-approved policies. A single miner hotkey is registered on Bittensor testnet netuid 567; the same hotkey signs research requests and submissions.

The miner's private hotkey never enters Carbon code—an external signer (carbon-miner-signer) holds it. Validators store private roots, seed journals, pool state, and service keys on secure host instances. Multi-validator submission is supported: one frozen strategy can be sent to multiple validators' intakes simultaneously.

Commitments are optional (testnet now); mainnet will bind submissions to on-chain recipe-hash commitments. The platform enforces deterministic reconstruction via pinned software, determinism settings, and DEVELOPMENT-only testing; production qualification remains separate.

Incentive mechanism

Miners develop strategies through local practice on public cases, freeze a strategy with a contract digest, optionally post that digest on-chain as a commitment, then submit to a validator's intake. The validator rebuilds the strategy using validator-controlled randomness (seed), evaluates it on hidden cases, and returns a sealed verdict only after the material's registered release window. Scoring gates mandate reference validity, infrastructure success, and decision-quality thresholds.

Admission windows per hotkey per 360-block window limit submissions. Validators rank admitted submissions and publish weights via testnet_winner_publication. Testnet mining grants no earnings; mainnet registration, policy bounds, coldkey custody, and payment qualification are owner decisions not yet made.

The intake authenticates via btauth/1 (Bittensor v11 HTTP auth), journals against replay, and enforces per-hotkey rate limits.

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

Carbon

Hard Sign · Cyrillic letter · pronounced “yer”

Transforming engineering simulations through machine learning

Owner: 5D5Rw…Ynj9
Hotkey: 5DDLU…GUTk
Owner Cut: 18.00%
Contact: [email protected]

Registered: 1 month ago(Oct 4, 2026)
Block: 9,210,632
Slot history: Every subnet in SN116
Neurons: 256/256
Tempo: 360 blocks

Website

URL: https://carbonphysics.ai/ (carbonphysics.ai, opens in a new tab, external site)
Status: Up200
TLS: Valid
Title: Carbon — Discovery + Evidence Infrastructure for Physics AI
Checked: 2026-11-09 04:01 UTC

Changes (10)

2026-11-09 04:01 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-08 04:01 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-07 04:01 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-06 04:00 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-05 04:01 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-04 04:00 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-03 04:02 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-02 04:01 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-11-01 04:01 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI
2026-10-31 04:01 UTCUp200Carbon — Discovery + Evidence Infrastructure for Physics AI

Subnet History

SubnetIdentitySet 2026-10-21 22:04 UTC

Block 9,334,721Extrinsic

SubnetIdentitySet 2026-10-05 13:50 UTC

Block 9,217,141Extrinsic

Emissions started 2026-10-04 18:10 UTC

Block 9,211,241Extrinsic

Subnet registered 2026-10-04 16:09 UTC

Block 9,210,632

SubnetIdentitySet 2026-10-04 16:09 UTC

Block 9,210,632

Recent Activity

SubnetIdentitySet Block 9,334,721 Extrinsic2026-10-21 22:04 UTC
SubnetIdentitySet Block 9,217,141 Extrinsic2026-10-05 13:50 UTC
FirstEmissionBlockNumberSet Block 9,211,241 Extrinsic2026-10-04 18:10 UTC
NetworkAdded Block 9,210,6322026-10-04 16:09 UTC
SubnetIdentitySet Block 9,210,6322026-10-04 16:09 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

RAM4 GB

OSLinux x86-64 or WSL2 on Windows

Not yet verified: GPU, Storage, CPU cores, Network, Notes

Validator

GPURequired

RAM4.29 GB

Not yet verified: GPU model, GPU count, CPU cores, OS, Network, Notes

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 2 Nov 2026

Miner Setup

Clone the Carbon repository

git clone https://github.com/carbonphysicsai/Carbon.git ~/carbon

Run the installer to set up the environment, build images, and start the Control Center. Add --gpu for GPU worker, --service for systemd integration.

~/carbon/scripts/install_miner.sh

Start the external signer in a separate terminal to hold your hotkey and sign requests

~/carbon/.venv/bin/carbon-miner-signer --wallet YOUR_WALLET --hotkey YOUR_HOTKEY

Access the Control Center web interface for setup and campaign management

Open browser to address printed by Control Center with the printed session token

Configure profile through the Control Center UI (Inference → Compute → Agent → Review)

Complete setup steps: confirm registration, select inference provider, configure compute, choose agent

Choose a Challenge and begin research campaign with selected agent and compute

Select Challenge and launch campaign through Campaigns tab

Iterate, freeze candidate strategy, and submit to validator intake for evaluation

Practise on CPU or GPU, freeze strategy, optionally commit digest on-chain, then submit

Update to latest main; rebuilds images and re-checks setup(optional)

~/carbon/scripts/install_miner.sh --update

Validator Setup

Prepare intake configuration as owner-only JSON file mode 0600

Write intake configuration file (carbon.battery.intake.v1 schema) with deployment, transport journal, inbox, receiver hotkey, host/port bindings

Prepare validator service configuration as owner-only JSON file mode 0600

Write service configuration file (carbon.battery.validator-service.v1 schema) with intake, state_dir, backups, practice_images, run_every_s

Create initial backup of root, journal, state before any changes

python -m scripts.dev.battery_validator_service backup --config S

Run comprehensive preflight checks including Docker, images, deployment upgrade, exposure, and parity

python -m scripts.dev.battery_validator_service preflight --config S

Verify validator's images match pinned practice manifests that miners use

python -m scripts.dev.battery_validator_service parity --config S

Generate systemd user units and install them for intake and daemon(optional)

python -m scripts.dev.battery_validator_service units --config S --out <units dir> && cp <units dir>/carbon-battery-*.service ~/.config/systemd/user/

Start the intake and validator daemon services via systemd(optional)

systemctl --user daemon-reload && systemctl --user enable --now carbon-battery-intake.service carbon-battery-validator.service

Verify both services are healthy and intake is serving requests

python -m scripts.dev.battery_validator_service status --config S

Confirm intake is responding with correct network, netuid 567, Challenge, and receiver

curl -s http://127.0.0.1:8467/carbon/v1/battery/intake

Configure TLS and public binding only after owner approval and security review(optional)

For public exposure: update intake config with host, exposure_record, tls_cert, tls_key; then preflight and restart

Backup deployment state before any code or image updates(optional)

python -m scripts.dev.battery_validator_service backup --config S

Upgrade deployment to new rule/image/material when needed(optional)

python -m carbon.battery.operate upgrade --config <deployment.json>

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

What moved the price

Overview

Today so far

Subnet Configuration

Market & Economics

For Miners

For Validators & Stakers

Registration Activity

Development Activity

What Carbon 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 Carbon does

About

Website

Subnet History

Hardware Requirements

Miner Setup

Validator Setup