Subnet 1: Apex
Apex is Bittensor’s first subnet (netuid 1), operated by Macrocosmos. Its incentive mechanism runs open competitions where miners submit algorithms and validators continuously score those submissions against benchmarks. Rewards flow to miners whose solutions perform best, creating a permissionless environment for algorithmic and agentic optimization research.
How the Mechanism Works
The Apex overview describes the subnet around three layers:
- Competition: A defined problem domain with scoring criteria. Multiple competitions can run simultaneously on the subnet.
- Round: A discrete evaluation cycle within a competition. Submissions are scored each round, and cumulative performance across rounds determines a miner’s rank.
- Submission: An algorithm a miner contributes for evaluation. Validators score each submission against the competition’s benchmark.
Validators score active miner submissions each round. Those round scores shape the validator weights validators submit on netuid 1; Yuma Consensus then settles those weights into emission shares each tempo—competition scoring is evaluation input, not the emission payout itself (Apex overview, Yuma Consensus, Emission). Miners with consistently high-performing submissions earn the larger share. The active competition set rotates over time (Apex overview).
Miner and Validator Roles
Subnet 1 operates under the standard Bittensor two-role structure. Miners supply algorithmic submissions for the active competition, and validators evaluate those contributions against each competition’s benchmark before setting weights (Apex overview, Understanding Subnets).
Reward distribution follows Yuma Consensus.
On-Chain Identity
Subnet 1 is registered at netuid 1 with 256 neurons. Live identity fields are available on TaoStats (Apex overview).
Distinction from Yuma Consensus
Apex on netuid 1 is a competition-based subnet where miners submit algorithms for active competitions and validators score those submissions against each competition’s benchmark. That competition-scoring vocabulary names how Apex ranks miner performance on netuid 1, not the on-chain step that turns validator weight submissions into emission shares each tempo (Apex incentive mechanism, Yuma Consensus).
Yuma Consensus is the on-chain mechanism that runs at the epoch boundary on the selected netuid. It reads the weight matrix from eligible validators, applies clipping and bonding, and converts the result into miner incentives and validator dividend shares (Yuma Consensus, Emission).
Earlier sections describe competitions, rounds, and submissions as the scored work layers. Those inputs shape the validator weights; they do not settle emissions themselves. Yuma aggregates the weight signals that flow from that competition-scoring path rather than running benchmark evaluations itself (Apex incentive mechanism, Understanding Subnets).
Competition scoring therefore sits upstream of settlement. Yuma still credits emissions from included validator weights on netuid 1 once the tempo closes (macrocosm-os/apex, Emission).
Readers should treat Apex as the competition-based benchmark subnet on netuid 1, and Yuma Consensus as the recurring mechanism that allocates rewards from validator weights each tempo.
- Subnet 1 (Apex) — competition-scored benchmark subnet.
- Yuma Consensus — epoch-boundary settlement from validator weights to emission shares on a task subnet (Yuma Consensus: Validator emissions).
Reader Boundary
Subnet 1 Apex should not be read as generic Bittensor subnet documentation, a guarantee of current competition results, or proof that every subnet behaves like Apex. It names one mainnet subnet’s competition-based incentive context (Understanding Subnets).