Subnet Hyperparameters

How Bittensor subnet hyperparameters shape subnet timing, weight flow, consensus behavior, and emission handling without defining the subnet task itself.

Subnet Hyperparameters

Subnet hyperparameters are protocol state variables that shape how a Bittensor subnet behaves. They do not define what useful work means on the subnet; that is the role of the subnet’s incentive mechanism. Instead, hyperparameters set boundaries and timing around validator weights, consensus processing, emission handling, and miner or validator lifecycle rules.

References: Subnet Hyperparameters, Understanding Incentive Mechanisms

What they control

Hyperparameters cover several kinds of subnet behavior. Timing settings such as tempo define a block-based cadence. Weight-related settings influence how validator weight submissions are paced or processed. Consensus-related settings can affect bonding, clipping, and Yuma behavior. Emission-related settings can influence how subnet rewards are handled once the broader emission system reaches the subnet.

References: Subnet Hyperparameters, Yuma Consensus, Commit Reveal

Relationship to incentive mechanisms

An incentive mechanism tells miners what to produce and validators how to evaluate that work. Hyperparameters do not replace that mechanism. They set the protocol envelope around it: how often subnet epochs advance, how validator signals are submitted, how consensus interprets those signals, and how rewards are ultimately distributed. This is why hyperparameters are closely related to subnet_creation_mechanisms|subnet mechanism design without being the same thing.

References: Understanding Incentive Mechanisms, Yuma Consensus, Emission

Timing and reward cadence

Tempo is the clearest timing example. The emission process accumulates rewards over blocks and distributes them at the end of a subnet tempo through yuma_consensus|Yuma Consensus. Commit Reveal also depends on tempo-based timing: its waiting period is measured in tempos, and converting that interval to blocks requires the subnet’s tempo value.

References: Emission, Subnet Hyperparameters, Commit Reveal

Authority and change control

Not every hyperparameter is controlled the same way. Some values are intended for subnet-level administration, while others require broader protocol authority. Readers should avoid assuming that any named value can be changed by the same actor or through the same process. Permission and update rules are part of the parameter definition, not just operational detail.

Reference: Subnet Hyperparameters

How to read hyperparameter claims

A hyperparameter claim should name the behavior being described rather than treating the value as a universal property of Bittensor. The important questions are whether the claim is about timing, consensus, emissions, or subnet administration, and whether the cited source supports that exact scope. Exact values should be checked against the relevant subnet source before making operational decisions.

References: Subnet Hyperparameters, Commit Reveal

Further Reading

Topics SubnetsConsensus