Tempo

How Bittensor subnets use tempos as block-based intervals for reward distribution, weight processing, and subnet timing.

Tempo

A tempo is a block-based timing interval used by Bittensor subnets. Rewards accumulate during a tempo and are distributed at the end of that interval through yuma_consensus|Yuma Consensus. As a subnet hyperparameter, tempo specifies the number of blocks between epoch transitions.

References: Emission, Subnet Hyperparameters

What a tempo controls

Tempo gives subnet processes a shared cadence. It does not define what useful work means on a subnet; that comes from the subnet’s incentive mechanism. Instead, tempo helps determine when periodic subnet work is grouped, processed, and paid out. This is why tempo sits near both subnet_creation_mechanisms|subnet mechanism design and dynamic_tao|emission allocation.

References: Subnet Hyperparameters, Understanding Incentive Mechanisms

Emission timing

Bittensor emission has a two-stage flow: rewards are injected into subnet pools over blocks, and then distribution happens at the end of each tempo. Yuma Consensus is the aggregation step that uses validator-submitted evaluations to determine how those rewards are allocated inside the subnet.

References: Emission, Yuma Consensus

Hyperparameter context

Tempo is also a subnet hyperparameter, so articles should not treat one timing value as a universal property of every subnet. Exact timing claims belong next to the source that supports them, and operational decisions should use the relevant subnet’s parameter value rather than a generic description.

Reference: Subnet Hyperparameters

Commit Reveal timing

Commit Reveal uses tempo-based timing as part of delayed weight visibility. Its commit_reveal_period value is measured in tempos, and converting the reveal interval to blocks requires multiplying that period by the subnet tempo. This is one practical reason tempo matters beyond ordinary reward distribution.

References: Commit Reveal, Subnet Hyperparameters

How to read tempo claims

A tempo claim should make clear whether it is describing the concept, a hyperparameter, or a process that depends on tempo. The stable concept is the block-based cadence. Claims about exact length, reward timing, or reveal timing need the specific protocol documentation or subnet parameter source that supports them.

References: Emission, Subnet Hyperparameters

Further Reading

Topics ConsensusSubnets