Table of Contents
Tempo is the payout clock that tells each Bittensor subnet when to settle rewards.
On Bittensor, miners and validators do not receive subnet alpha rewards continuously every block. Rewards accrue as blocks are produced, then settle at the end of a subnet’s tempo, which is the block interval between one consensus epoch and the next. For most modern subnets, the default tempo is 360 blocks, or roughly 72 minutes, because Bittensor produces a new block about every 12 seconds.
This distinction shapes how you read Bittensor rewards, subnet staking, validator scoring, and miner payouts. The chain may mint and account for emissions block by block, but the subnet’s internal reward distribution happens at epoch boundaries, after Yuma Consensus turns validator weights into miner incentives and validator dividends.
If Bittensor’s subnets are markets for useful AI work, tempo is the rhythm that determines when those markets settle.
Block Time vs. Tempo vs. Epoch
The easiest mistake is to treat Bittensor’s block time, tempo, and epoch as the same concept. They are related, but they answer different timing questions.
Bittensor’s blockchain produces a new block roughly every 12 seconds. Each block records network activity, including submitted extrinsics, staking activity, validator weight updates, emission accounting, and other on-chain state changes. The chain is the settlement and coordination layer for the network, while the actual AI work happens off-chain inside Bittensor subnets.
Tempo is not the block time. It is a subnet-level interval measured in blocks. If a subnet has a tempo of 360, the subnet waits 360 blocks between reward epochs. At roughly 12 seconds per block, that produces a reward cadence of about 72 minutes.
An epoch is the moment when that waiting period ends. At the epoch boundary, the subnet distributes the alpha that has accumulated since the previous epoch. That is when Yuma Consensus resolves validator weights into reward shares, and when miners and validators receive their portion of the subnet’s alpha emissions.
So if a reader asks, “How often are Bittensor miners paid?” the answer is not “every block.” A more precise answer is that subnet rewards accrue across blocks and settle at the subnet’s epoch boundary, which is usually every 360 blocks, or roughly every 72 minutes, unless that subnet has a different tempo.
What Happens During a Tempo
During a tempo, Bittensor’s subnet participants continue doing the work that makes the reward system meaningful.
Miners produce whatever output their subnet is designed to measure, such as inference, compute, data work, prediction, or another digital commodity. Validators evaluate miners and submit weights to the chain. Those weights express how much value the validator believes each miner is contributing under that subnet’s incentive mechanism.
At the same time, emissions continue to accrue. Bittensor’s emissions system runs in two broad layers. The chain mints and accounts for TAO at the block level, while each subnet accumulates participant-side alpha for later distribution at the next epoch. The official emissions documentation describes this as a two-stage process: every block, the chain mints TAO and injects liquidity across subnets; every tempo, each subnet distributes accumulated alpha through Yuma Consensus.
Tempo works as a settlement interval. The subnet stays active between epochs. Validators keep scoring, miners keep competing, and alpha keeps accumulating. The payout only finalizes when the epoch fires.
This also explains why Bittensor rewards can feel different from a simple per-block mining system. The work and accounting are continuous, but the settlement is periodic.
What Happens at the Epoch Boundary
At the epoch boundary, Bittensor turns the subnet’s accumulated activity into actual reward distribution.
Each subnet’s epoch fires once enough blocks have passed since its last epoch. In the default case, that means 360 blocks. When the epoch fires, the protocol runs the subnet’s reward logic and distributes the accumulated alpha to the hotkeys holding each UID at that moment.
This is where Yuma Consensus becomes important. Validators do not simply pick winners by themselves. They submit weights, and Yuma Consensus turns those weights into a stake-weighted agreement about which miners deserve rewards. The result determines miner incentives and validator dividends inside that subnet.
The epoch boundary does three things:
- It ends the subnet’s current reward interval.
- It resolves validator scoring through Yuma Consensus.
- It pays out the accumulated alpha to the eligible participants at that point in time.
The exact distribution depends on Bittensor’s current emissions rules, subnet parameters, validator weights, stake, and other protocol mechanics. The epoch is payday, and tempo is the clock that counts down to it.
How Tempo Fits Into Bittensor Rewards
Tempo is only one part of Bittensor’s reward system, but it helps make the rest of the system easier to understand.
Bittensor emissions involve both TAO and subnet alpha. TAO is the network’s native token, while alpha is the subnet-specific token used inside each subnet’s economy. In the current architecture, subnet participants generally earn alpha from the subnet where they contribute, while TAO remains the base asset for the broader network and the asset against which subnet alpha tokens are priced.
Inside a subnet, accumulated alpha is split among miners, validators and their stakers, and the subnet owner. TAO Media’s guide to how TAO rewards are distributed explains that the common subnet alpha split is roughly 41% to miners, 41% to validators and their stakers, and 18% to the subnet owner.
Tempo does not decide who deserves the largest share. Yuma Consensus handles that inside each subnet. Tempo decides when the accumulated distribution is settled.
Reward data can be misread if someone treats it as a continuous per-block stream. A miner’s latest emission value reflects the subnet’s most recent epoch settlement, not a guaranteed payout every 12 seconds. Likewise, validator and staker rewards depend on how the subnet settles at epoch boundaries, not on a simple clock that pays each participant identically every block.
Who Can Change Tempo?
Tempo is a subnet hyperparameter, which means it can be configured within protocol-defined limits.
According to Bittensor’s tempo documentation, subnet owners can set tempo within a range of 360 to 50,400 blocks. That spans roughly 72 minutes to roughly seven days at a 12-second block time. Owner changes are rate-limited to one change per 360 blocks, and root has broader authority to set values outside the owner-bounded range.
Changing tempo has practical consequences. A successful tempo change resets the epoch cycle, so the next epoch lands a full new tempo after the change. In practice, that means adjusting tempo changes the subnet’s payout cadence going forward.
A shorter tempo means more frequent settlement. A longer tempo means less frequent settlement. But tempo should not be interpreted as a quality signal by itself. A subnet’s tempo may reflect operational needs, incentive design, legacy settings, or administrative choices rather than whether the subnet is strong or weak.
Why Tempo Matters for Learners
Tempo answers one of the most practical questions in Bittensor, which is when rewards actually settle.
For miners, tempo affects when work turns into a payout. A miner may compete throughout a tempo, but the reward lands only when the subnet’s epoch fires. If the miner loses its UID before the epoch boundary, the emissions documentation states that the payout goes to whoever holds the UID when the epoch fires, and a neuron pruned mid-tempo receives no partial payout for that interval.
For validators, tempo frames the scoring cycle. Validators submit weights during the interval, and those weights are used when the subnet settles through Yuma Consensus. Validator permits are also recalculated every epoch, which makes epochs important for validator competition and participation.
For stakers, tempo helps explain why reward data may update in steps rather than as a smooth second-by-second yield stream. Delegated stake earns through validator dividends, and those dividends are tied to epoch settlement.
Tempo also anchors other subnet parameters. Bittensor’s documentation notes that activity cutoffs can be tied to tempo, and commit-reveal delays are counted in tempos. That makes tempo part of the subnet’s broader operating rhythm, not merely a payout timer.
How to Check a Subnet’s Tempo and Next Epoch
The safest way to know a subnet’s timing is to check the chain directly.
Bittensor exposes reads for tempo and epoch timing. The documentation points to queries such as tempo, epoch-status, and blocks-until-next-epoch, which show the subnet’s current tempo and how close it is to its next epoch.
The command syntax matters less than the habit of checking the current subnet state instead of relying on a generic assumption. The default tempo is 360 blocks, but some older subnets may differ, and subnet owners can update tempo within the allowed range.
If you are evaluating a miner, validator, or staking position, checking tempo can help you understand when the next reward update should arrive and whether a payout delay is simply part of the subnet’s settlement schedule.
Why Tempo Is Easy to Misunderstand
Tempo is easy to miss because it sits between more visible ideas.
The chain advances roughly every 12 seconds. Rewards, at a high level, go to miners, validators, stakers, and owners. Tempo is the timing layer that connects those two ideas.
Without tempo, a reader might assume that every block immediately pays every participant. That is not how subnet alpha distribution works. The chain can mint and account for emissions continuously while still settling a subnet’s participant rewards at epoch boundaries.
Tempo is also easy to confuse with broader Bittensor emission allocation. The network has mechanisms that determine how much emission flows toward different subnets, which TAO Media covers in its guide to how subnets compete for emissions. Tempo is narrower. It does not decide which subnet deserves more network-wide emission. It sets the cadence for when a specific subnet distributes its accumulated rewards internally.
That narrower role is what makes tempo useful as a learner concept. Once you understand it, the rest of the Bittensor reward system becomes less mysterious: blocks are the chain’s heartbeat, tempo is the subnet’s payout clock, and epochs are the settlement events.
Conclusion
Tempo makes sense once it is separated from block time.
A block is produced roughly every 12 seconds. A subnet’s tempo is the number of blocks between reward epochs. An epoch is the moment when the subnet settles its accumulated alpha rewards through Yuma Consensus. In the default case, that means a 360-block cycle, or roughly 72 minutes, though specific subnets can differ.
For miners, validators, stakers, and learners, tempo explains why subnet rewards are not best understood as continuous per-block payments. The work happens throughout the interval, the emissions accrue during the interval, and the payout settles at the boundary.
Tempo is the payout clock, and the epoch is payday.
This article is for informational and educational purposes only. It is not financial, investment, legal, or tax advice. Digital assets, staking, subnet tokens, and crypto infrastructure involve risk, and readers should do their own research before making financial decisions.
FAQs
What Is Tempo on Bittensor?
Tempo is the number of blocks between a subnet’s reward epochs. It sets how often the subnet settles accumulated alpha rewards through Yuma Consensus.
What Is the Default Tempo on Bittensor?
The default tempo is 360 blocks. Since Bittensor produces blocks roughly every 12 seconds, 360 blocks equals about 72 minutes.
Does Tempo Mean Miners Are Paid Every Block?
No. Miners may do work continuously and emissions may accrue across blocks, but subnet alpha rewards settle at epoch boundaries. The default cadence is roughly every 360 blocks, not every block.
What Is a Bittensor Epoch?
A Bittensor subnet epoch is the settlement event that occurs after the subnet’s tempo has passed. At the epoch boundary, accumulated alpha rewards are distributed according to the subnet’s reward logic and Yuma Consensus.
Can a Subnet Owner Change Tempo?
Yes. Subnet owners can set tempo within the owner-bounded range of 360 to 50,400 blocks, or roughly 72 minutes to seven days. Root has broader authority, and changing tempo resets the epoch cycle.
Do All Bittensor Subnets Use the Same Tempo?
No. The default is 360 blocks, but some older subnets may have smaller legacy tempo values, and subnet owners can change tempo within allowed bounds. The best approach is to check the specific subnet’s current tempo.
What Happens If a Miner Is Deregistered Before the Epoch?
If a miner loses its UID before the epoch fires, the payout goes to whoever holds that UID at the epoch boundary. The emissions documentation states that a neuron pruned mid-tempo does not receive a partial payout for that interval.
How Do I Check the Next Epoch for a Subnet?
Bittensor exposes reads such as tempo, epoch-status, and blocks-until-next-epoch. These can show a subnet’s current tempo and how many blocks remain before the next epoch.
