Loading
Loading
Neuron registration trends
Hardware design teams face significant barriers to validation and manufacturing: design tools require expensive licenses, testing silicon involves months of fabrication lead times and costs exceeding millions of dollars, and there's no efficient marketplace for quality design talent. Engineers often work in isolated environments without exposure to competing implementations or objective performance comparisons.
A distributed design platform solves this by creating an open competition where engineers submit implementations of well-defined challenges. Designs are evaluated consistently using industry-standard EDA tools (synthesis, place & route, timing analysis) against shared specifications and testbenches. This approach lets teams see how their work compares on objective metrics—functionality, resource efficiency, timing performance, and power consumption—without requiring expensive fabrication cycles.
ChipForge implements this as an on-chain subnet. Miners (hardware engineers) submit Verilog/SystemVerilog designs for active challenges like AI accelerators and cryptographic processors. Validators run standardized EDA evaluations and score submissions. The highest-scoring design wins rewards; submitted designs become manufacturable IP that can be fabricated and monetized, with revenue reinvested into the ecosystem.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
ChipForge is a decentralized hardware design subnet where miners submit Verilog/SystemVerilog implementations of silicon designs (AI accelerators, cryptographic modules, processors) for active challenges. Validators evaluate submissions using industry-standard EDA tools (Verilator, Yosys, Icarus, Openlane) based on functionality and performance metrics, with rewards distributed in a winner-takes-all mechanism to the highest-scoring design.
ChipForge follows a distributed evaluation architecture with several key components: (1) Miners download active challenge specifications from GitHub via the Challenge Server, design Verilog/SystemVerilog implementations locally, and submit ZIP files through the Challenge API (max 10MB, 5 submissions per hotkey per challenge). (2) The Challenge Server manages challenge lifecycle, batches submissions into evaluation groups with 10-minute download windows and 20-minute evaluation windows, and exposes one batch at a time to validators. (3) Validators continuously poll for active challenges, download batches of submissions, run evaluations using the external Chipforge EDA Server (which invokes Verilator, Yosys, Icarus, and Openlane), and submit scores back to the Challenge Server. (4) The EDA Server performs synthesis, place & route, and timing analysis to generate evaluation metrics. (5) Validators set Bittensor subnet weights based on challenge winners, with support for emission burning when no qualified submissions exist or emissions are banned. The workflow cycles through: Challenge Activation → Miner Submissions → Batch Creation → Validator Downloads → EDA Evaluation → Score Submission → Weight Setting → Challenge Completion.
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 for the latest instructions.
Validators evaluate all submissions in a batch using EDA tools and assign scores across multiple dimensions. Currently, Functionality (0-100) is the primary metric, with Area, Delay, and Power metrics marked as TBD for future implementation. Submissions are ranked competitively; only those exceeding the challenge-wide best score qualify for rewards.
The winner receives configurable emission distribution (0-100%) for a set duration after challenge completion. Banned coldkeys are excluded from receiving rewards. The mechanism includes crash recovery to maintain winner rewards across validator restarts and grace periods for challenge transitions.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes.
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Holder & total-staked metrics as of 4h ago (hourly snapshot)
Miners primarily design hardware in Verilog/SystemVerilog and submit ZIP files (max 10MB). No specialized hardware required for design phase.
Validators require access to Chipforge EDA Server (separate repository) with Verilator, Yosys, Icarus Verilog, and OpenLane tools installed. EDA tool dependencies are managed by the external EDA server, not the subnet code.
Clone the ChipForge subnet repository
git clone https://github.com/TatsuProject/ChipForge_SN84 && cd chipforge-subnet
Install Python dependencies and the subnet package
pip install -r requirements.txt && pip install -e .
Create a Bittensor wallet and coldkey for registration
python3 -m btcli wallet new_coldkey --wallet.name YOUR_WALLET
Register your hotkey on subnet 84
python3 -m btcli subnet register --netuid 84 --wallet.name YOUR_WALLET --wallet.hotkey YOUR_HOTKEY
Create and configure .env file with wallet name, hotkey, and API URL
cp .env.example .env && nano .env
Start the miner process
./start_miner
Download the active challenge specifications and test cases
python3 python_scripts/miner_cli.py download
Submit your completed design solution as a 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_SN84 && cd chipforge-subnet
Install Python dependencies and the subnet package
pip install -r requirements.txt && pip install -e .
Clone and set up the Chipforge EDA Server (separate repository with tool dependencies)
git clone https://github.com/TatsuProject/chipforge_eda_server && cd chipforge_eda_server
Create a Bittensor wallet and coldkey for registration
python3 -m btcli wallet new_coldkey --wallet.name YOUR_WALLET
Register your hotkey on subnet 84
python3 -m btcli subnet register --netuid 84 --wallet.name YOUR_WALLET --wallet.hotkey YOUR_HOTKEY
Configure .env with wallet details, validator_secret_key, challenge_api_url, and miner_emission_percentage
cp .env.example .env && nano .env
Start the validator process (ensure EDA server is running first)
./start_validator