
ChipForge
モ (Mo)SN108ChipForge decentralizes silicon design. Miners anywhere compete to build chips that accelerate AI, scored on real AI models.
Overview
Registration Activity
Neuron registration trends

ChipForge decentralizes silicon design. Miners anywhere compete to build chips that accelerate AI, scored on real AI models.
Neuron registration trends
The alpha price in τ, day by day, and what moved it each way.
Log change over the last 30 days −104.22%: protocol buys 0.00%, root sells −60.50%, users net −41.98%, cross-subnet −1.74%, unattributed +0.0003%.
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.
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).
2026-11-10 UTC, as of ≈04:04 UTC (block 9,473,310)
The day isn’t over yet, so these figures keep changing. They are in no daily total, average or rank.
Emission history is being recalculated from on-chain allocation.
Hardware design quality evaluation is expensive and centralized. Teams typically rely on expensive EDA tools (Verilator, Yosys, OpenLane) running on local infrastructure, and design competitions require coordinating independent evaluators to score submissions consistently across multiple metrics: functionality, area, delay, and power. This creates bottlenecks for validation and makes it difficult to scale open design challenges.
A decentralized network of validators, each running industry-standard EDA tools and scoring submissions against shared challenge specifications, can evaluate designs at scale with transparent, reproducible results. Validators competing for rewards through an on-chain record ladder are incentivized to evaluate accurately, while miners competing to improve their scores drive innovation.
ChipForge implements this on Bittensor subnet 108: miners download Verilog specifications and testbenches, design solutions, and submit them as ZIP files. Validators claim evaluation batches, run each design through Verilator (simulation), Yosys, and OpenLane (synthesis and timing), and submit standardized scores.
The challenge server aggregates results, determines winning records, and distributes rewards to top performers through a probation and payment window system.
Auto-generated from the GitHub repository and may not reflect the latest changes.
ChipForge is a decentralized hardware design subnet on Bittensor where miners submit Verilog/SystemVerilog hardware designs for challenges, and validators evaluate submissions using industry-standard EDA tools (Verilator, Yosys, Icarus, OpenLane), scoring them on functionality, area, delay, and power metrics, with rewards distributed to top-performing designs through a record ladder system.
Miners download challenge packages (Verilog specs, testbenches), design solutions, and submit them as ZIP files via the challenge server API. The challenge server groups submissions into batches with download and evaluation windows. Validators claim batches, download all submissions with verified SHA256 hashes, evaluate each on their EDA server (running Verilator for simulation, Yosys/OpenLane for synthesis and area/timing analysis), and submit scores.
The challenge server aggregates validator results, determines records, manages the probation and paid windows, and sends the record ladder to validators every sync. Validators apply weights on-chain following the ladder (paying records, burning non-payable designs and excess weight). Miners receive notifications of new challenges and batch completions via the validator's axon using the SimpleMessage synapse.
The EDA server (separate deployment) performs the actual simulations and synthesis.
When a batch closes, the challenge server identifies records (designs beating the score-to-beat) from aggregated validator results. Each record enters probation before being paid for a fixed window. The record ladder maintains up to N records (default 3) ranked by submission time within the paid window, with each position receiving ratio^(i-1) of the miner emission share (ratio 0.6).
Records with unregistered hotkeys, banned coldkeys, or the burn UID are skipped. If no payable record exists or all are in probation, everything is burned. The validator applies these weights on-chain at most every WEIGHTS_REFRESH_SECONDS (default 1200), or immediately if the target changes.
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)
ChipForge decentralizes silicon design. Miners anywhere compete to build chips that accelerate AI, scored on real AI models.
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.
Not yet verified: OS, Notes
Not yet verified: GPU, RAM, Recommended RAM, 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 9 Nov 2026
Clone the ChipForge subnet repository
git clone https://github.com/TatsuProject/ChipForge_SN108 && cd ChipForge_SN108
Create isolated Python 3.12 environment
conda create -n chipforge-subnet python=3.12 && conda activate chipforge-subnet
Install Bittensor 10.x SDK and dependencies
pip install -r requirements.txt && pip install -e .
Create Bittensor wallet with coldkey and hotkey
btcli wallet create --wallet-name mywallet --hotkey default
Register hotkey on subnet 108 (or testnet with appropriate netuid)
btcli subnets register --netuid 108 --network finney --wallet-name mywallet --hotkey default
Copy example environment configuration
cp .env.example .env
Configure miner wallet and API settings in .env
# Edit .env with: MINER_WALLET_DIR, MINER_WALLET_NAME, MINER_HOTKEY, CHALLENGE_API_URL
Start miner using Docker (recommended), or ./start_miner.sh for direct execution
make up ROLE=miner
Download active challenge package and testbench(optional)
python3 python_scripts/miner_cli.py download
Submit Verilog/SystemVerilog solution as ZIP file
python3 python_scripts/miner_cli.py submit solution.zip --check_status
Clone the ChipForge subnet repository
git clone https://github.com/TatsuProject/ChipForge_SN108 && cd ChipForge_SN108
Clone and setup ChipForge EDA server (required for validators)
git clone https://github.com/TatsuProject/chipforge_eda_server && cd chipforge_eda_server
Start EDA server before starting validator
# Follow EDA server README to start it; default listens on http://localhost:8080
Create Bittensor wallet with coldkey and hotkey
cd ChipForge_SN108 && btcli wallet create --wallet-name mywallet --hotkey default
Register hotkey on subnet 108 with sufficient stake for validator permit
btcli subnets register --netuid 108 --network finney --wallet-name mywallet --hotkey default
Stake TAO to gain validator permit (top-staked hotkeys on subnet)
btcli stake add --netuid 108 --wallet-name mywallet --hotkey default --amount <stake>
Copy example environment configuration
cp .env.example .env
Configure validator wallet, secret key, and API settings in .env
# Edit .env with: VALIDATOR_WALLET_DIR, VALIDATOR_WALLET_NAME, VALIDATOR_HOTKEY, VALIDATOR_SECRET_KEY, EDA_SERVER_URL, CHALLENGE_API_URL
Verify all required environment variables are set
make env-check
Start validator using Docker (recommended), or ./start_validator.sh for direct execution
make up
Monitor validator and EDA server logs(optional)
make logs
Verify EDA server is reachable and healthy(optional)
curl http://localhost:8080/health