Log change over the last 30 days +11.69%: protocol buys 0.00%, root sells −56.08%, users net −32.91%, cross-subnet +100.68%, unattributed −0.0003%. 1 day still in progress is counted as far as known.

Protocol buy
User buy (staking)
Cross-subnet
Root sell (dividend claims)
User sell (unstaking)
Residual
Price path
Market candle

About this chart

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-04 UTC, as of ≈22:31 UTC (block 9,435,650)

Price, today so far: 0.004811 τ
Volume, today so far: 12.17 τ
Market cap incl. burned, today so far: 1.06K τ
TAO in pool, today so far: 530.45 τ
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

189/25667 open

Validators

5/6459 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

640.3638 τ

FDV

1,589.2174 τ

TVL

1,060.9024 τ

Lifetime Volume

27.43K τ

Holders

171

14d price

Revenue / Recycle

26.04×

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

≈ 34.6361 τ·34.6361 τ per day

Miners65.55%

4,719.3734 モ ≈ 22.7029 τ/day

Validators16.45%

1,184.6596 モ ≈ 5.6989 τ/day

Owner18.00%

1,295.9670 モ ≈ 6.2343 τ/day

Stake 1,000 τ here

2,233.3055 モ/day≈ 10.7435 τ·10.7435 τ per day

From the validator share, before commission

~392.14%staker APY (est.)

· 2,383.29% total subnet

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

For Miners

65.55% of emission

Slots

189/25667 open

Burn Cost

0.0500 τ

Est. per Miner

—

Pool / Epoch

235.9687 モ≈ 1.1351 τ

For Validators & Stakers

16.45% of emission

Validator Slots

5/6459 open

Est. per Validator

11.8466 モ/epoch≈ 0.0570 τ

Registration Activity

Neuron registration trends

This Interval

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

Target / Interval

Slots Available

67 open

189/256

Neurons

189

Development Activity

TatsuProject/ChipForge_SN108Python

542 contributors22 commits/30dLast commit 0d ago

MIT

ai-acceleratorbittensorbittensor-subnetchipforgehardware-designssn108subnettatsu

Top Contributors

atkinson-ai103

tatsu-developer4

What ChipForge does

Hardware design evaluation today relies on centralized services and expensive EDA tool licenses. Teams submitting designs for fabrication or optimization face bottlenecks in access to synthesis, place & route, and timing analysis tools. The evaluation process is slow, costly, and often proprietary.

A decentralized network of independent validators running identical EDA toolchains can evaluate designs transparently and at scale. By incentivizing validators to maintain these tools and score submissions consistently, a peer network eliminates central gatekeeping and distributes both the computational load and the authority to decide design quality.

ChipForge operates this model on Bittensor subnet 108: miners submit Verilog/SystemVerilog implementations for active design challenges; validators download submissions and evaluate them locally using Verilator, Yosys, OpenLane, and Icarus within strict batch deadlines; evaluation results (functionality, area, delay, power) are submitted to a central record ladder that tracks design performance over time.

Validators who consistently evaluate according to the evaluator specification earn rewards; winning designs are ranked transparently on-chain.

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

About

active

ChipForge is a decentralized hardware design subnet on Bittensor where miners submit optimized Verilog/SystemVerilog implementations for digital design challenges (AI accelerators, cryptographic modules, processors), and validators evaluate them using industry-standard EDA tools (Verilator, Yosys, Icarus, OpenLane) across functionality, area, performance, and power metrics. Winners become records on a probation-based ladder and earn rewards proportional to their stake.

How it works

ChipForge operates in on-chain cycles where the challenge server (1) activates design quests and (2) groups submitted designs into evaluation batches. Validators (3) poll the server for active challenges and claim batches, (4) download submissions and evaluate them on a local EDA server (Verilator, Yosys, OpenLane) within batch deadlines, and (5) submit scores back to the server. The server then (6) decides records (best designs) and publishes a reward ladder.

Validators (7) compute the ladder locally (same algorithm) so weights stay current even if the server is unreachable, and (8) set weights on-chain paying the record ladder with the miner emission percentage and burning the rest. Miners receive challenge notifications from validators (so they can download early), poll the server for new challenges, and submit solutions via the miner CLI. The evaluator bundle (EDA evaluator version and metric weights) is versioned by the server; validators manage its installation and use on their EDA server (EvaluatorManager).

Incentive mechanism

The challenge server decides records from every validator's results when batches close. Each record must pass both functionality and overall gates to count. Records enter probation (earn nothing), then pay for a fixed window.

Multiple records per challenge share emissions; their placement on the ladder decays by ratio^(i-1) where i is the rank. Unregistered hotkeys, burn UID, and banned coldkeys have their weight redistributed to payable records. If no record is being paid or emissions are banned (ban_emissions flag), everything burns.

The validator's reward_ladder.py implements the same algorithm as the server so probation ends and windows close on time even when the server is unreachable. Validators submit weights on chain when places change or per WEIGHTS_REFRESH_SECONDS (~20 min).

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

モ

ChipForge

Mo · Katakana letter · pronounced “mo”

ChipForge decentralizes silicon design. Miners anywhere compete to build chips that accelerate AI, scored on real AI models.

Owner: 5FBws…UvoB
Hotkey: 5HjH8…PZwk
Owner Cut: 18.00%
Contact: [email protected]

Registered: 1 month ago(Sep 20, 2026)
Block: 9,111,253
Slot history: Every subnet in SN108
Neurons: 189/256
Tempo: 360 blocks

Website

URL: https://www.chipforge.io/ (chipforge.io, opens in a new tab, external site)
Status: Up200
TLS: Valid
Title: ChipForge | Decentralizing chip design
Checked: 2026-11-04 04:00 UTC

Changes (5)

2026-11-04 04:00 UTCUp200ChipForge | Decentralizing chip design
2026-11-03 04:02 UTCUp200ChipForge | Decentralizing chip design
2026-11-01 04:01 UTCUp200ChipForge | Decentralizing chip design
2026-10-18 04:01 UTCUp200ChipForge | Decentralizing chip design
2026-10-13 07:59 UTCUp200ChipForge | Decentralizing chip design

Subnet History

Emissions started 2026-10-05 19:40 UTC

Block 9,218,891Extrinsic

SubnetIdentitySet 2026-09-24 19:08 UTC

Block 9,139,530Extrinsic

Subnet registered 2026-09-20 20:51 UTC

Block 9,111,253

SubnetOwnerHotkeySet 2026-09-20 20:51 UTC

Block 9,111,253

Recent Activity

FirstEmissionBlockNumberSet Block 9,218,891 Extrinsic2026-10-05 19:40 UTC
SubnetIdentitySet Block 9,139,530 Extrinsic2026-09-24 19:08 UTC
NetworkAdded Block 9,111,2532026-09-20 20:51 UTC
SubnetOwnerHotkeySet Block 9,111,2532026-09-20 20:51 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

GPU—

NetworkOutbound internet access to challenge server; no inbound ports required

Not yet verified: OS, Notes

Validator

Storage100 GB

NetworkOutbound internet access to challenge server and subtensor endpoint; keep EDA server port 8080 closed to internet

Not yet verified: GPU, RAM, Recommended RAM, CPU cores, OS, 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

Create Bittensor wallet with coldkey and hotkey

btcli wallet create --wallet-name mywallet --hotkey default

btcli subnets register --netuid 108 --network finney --wallet-name mywallet --hotkey default

Clone ChipForge subnet repository

git clone https://github.com/TatsuProject/ChipForge_SN108 && cd ChipForge_SN108

Copy environment template and edit with wallet configuration

cp .env.example .env

Create isolated Python 3.12 environment (if not using Docker)(optional)

conda create -n chipforge-subnet python=3.12 && conda activate chipforge-subnet

Install Bittensor SDK 10.x and ChipForge dependencies(optional)

pip install -r requirements.txt && pip install -e .

Start miner in Docker (recommended), or: ./start_miner.sh

make up ROLE=miner

Download and extract active challenge package (spec, testbench)

python3 python_scripts/miner_cli.py download

Submit solution after solving challenge (validates ZIP format and size)

python3 python_scripts/miner_cli.py submit solution.zip --check_status

Validator Setup

Create Bittensor wallet with coldkey and hotkey

btcli wallet create --wallet-name mywallet --hotkey default

btcli subnets register --netuid 108 --network finney --wallet-name mywallet --hotkey default

Stake to hotkey to obtain validator permit (top-staked hotkeys get permits)

btcli stake add --netuid 108 --amount <stake>

Clone and start ChipForge EDA server on validator machine

git clone https://github.com/TatsuProject/chipforge_eda_server

Start EDA server (keep port 8080 closed to internet)

make up

Clone ChipForge subnet validator repository

git clone https://github.com/TatsuProject/ChipForge_SN108 && cd ChipForge_SN108

Copy environment template and configure with validator wallet and VALIDATOR_SECRET_KEY

cp .env.example .env

Verify all required environment variables are set

make env-check

Start validator in Docker (recommended), or: ./start_validator.sh

make up

Monitor validator logs in real-time(optional)

make logs

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 ChipForge 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 ChipForge does

About

Website

Subnet History

Hardware Requirements

Miner Setup

Validator Setup