Adjustment Interval
Adjustment interval is a per-subnet hyperparameter, listed as AdjustmentInterval in Bittensor
documentation, that sets the number of blocks between automatic recalibrations of the dynamic
registration burn cost. The
Subnet Hyperparameters reference
lists AdjustmentInterval alongside the burn band parameters that define the floor and ceiling of
the registration cost being adjusted
(Glossary: Register).
The term names the recalibration cadence. It does not set the burn cost itself; it sets the block window over which actual registrations are compared to the target registration rate to decide whether the cost moves up, down, or holds.
What It Controls
The hyperparameter determines how frequently the subnet’s registration burn is recalibrated against the target registration rate. Each adjustment interval, the network compares how many registrations occurred during the window to the target rate set by the subnet owner. If actual registrations exceeded the target, the burn cost rises; if they fell short, the burn cost eases toward the floor (Subnet Hyperparameters, Glossary: Burn Cost).
A shorter adjustment interval means the burn cost responds to registration demand more frequently on netuid 1 and other active subnets, so spikes in registration activity are reflected in cost sooner. A longer interval smooths the recalibration over more blocks, making the burn cost less reactive to short-term fluctuations.
The interval therefore shapes the responsiveness of the registration cost mechanism without setting the cost band itself. The burn floor and ceiling are separate parameters that define the range inside which each adjustment operates.
Removed From Hyperparameters V3
The canonical hyperparameter API get_subnet_hyperparams_v3 no longer returns AdjustmentInterval.
Official documentation lists adjustment_interval among parameters removed from V3, alongside
adjustment_alpha, difficulty, min_difficulty, max_difficulty, and rho. Neuron registration
is now governed by continuous burn pricing through BurnHalfLife and BurnIncreaseMult rather than
interval-based demand comparison against a target registration rate
(Subnet Hyperparameters).
Readers encountering adjustment interval in older material should treat it as legacy registration-pricing vocabulary. Live subnet registration economics on ordinary subnets are set through the burn band and per-registration step-up parameters in the current hyperparameter table.
Documented Type and Setter
The Subnet Hyperparameters
reference no longer exposes AdjustmentInterval through the canonical get_subnet_hyperparams_v3
API. It is listed among parameters removed from V3, so readers should not expect to read or set an
adjustment interval row on current hyperparameter tables.
Neuron registration pricing on ordinary subnets is instead governed by the continuous burn
parameters BurnHalfLife and BurnIncreaseMult, which step and decay the live burn between
registrations rather than recalibrating it on a fixed interval window
(Subnet Hyperparameters).
The sections above describe the interval-based vocabulary for readers encountering legacy material; live registration economics should be verified through the current burn hyperparameters on the relevant netuid.
Distinction from Target Registrations Per Interval
Adjustment interval sets the block window between burn recalibrations. Target registrations per interval sets how many registrations the mechanism aims for during that window (Subnet Hyperparameters).
- Adjustment interval — blocks between demand-comparison recalibrations.
- Target registrations per interval — reference registration count for each window.
Distinction from Burn Increase Mult
Burn increase mult steps the live registration burn up immediately after each successful slot claim, while adjustment interval waits until a block window ends and then recalibrates burn against the target registration rate for that window (Subnet Hyperparameters, Glossary: Register).
- Burn increase mult — per-registration step-up when a slot is claimed.
- Adjustment interval — block window between demand-comparison recalibrations.
Distinction from Burn Half Life
Burn half life and adjustment interval both affect how the registration burn cost changes over time, but they control different parts of the mechanism (Subnet Hyperparameters). Burn half life sets the decay horizon over which the elevated burn cost eases back toward the floor between registration events; adjustment interval sets the block window between demand-comparison recalibrations.
The two parameters complement each other. Adjustment interval governs when the mechanism recalibrates the burn cost against demand. Burn half life governs how quickly an elevated burn decays between registration events inside that cycle. A subnet owner can tune both independently to shape registration cost behavior on netuid 1 or any other subnet.
- Adjustment interval — block window between demand-comparison recalibrations.
- Burn half life — decay horizon easing elevated burn between registrations.
Distinction from Min Burn and Max Burn
Min burn and max burn set the floor and ceiling of the registration burn band. Adjustment interval sets the block window between demand-comparison recalibrations inside that band (Subnet Hyperparameters, Glossary: Burn Cost).
- Min burn / max burn — floor and ceiling of the registration burn band.
- Adjustment interval — block window between recalibrations inside that band.
Distinction from Register
Register names the subnet entry process that places a miner or validator into a UID slot. Adjustment interval names how often the dynamic registration burn is recalibrated against demand (Glossary: Register, Subnet Hyperparameters).
- Register — the subnet entry action claiming a UID slot.
- Adjustment interval — how often the dynamic burn is recalibrated against demand.
Chain Reads for netuid 1
Readers can verify live hyperparameter values for the documented example netuid with
btcli subnet hyperparameters --netuid 1 --network finney
(Subnet Hyperparameters: View hyperparameters).
That read path keeps live hyperparameter claims tied to a parseable netuid.
Per-Subnet Live Value Boundary
Adjustment interval is per-subnet chain state. The block window configured on one netuid governs how often that subnet recalibrates dynamic registration burn against its target rate, but the live interval can differ from reference defaults and from the window on another netuid (Subnet Hyperparameters, Glossary: Burn Cost).
This article’s infobox uses netuid 1 as an example when discussing one subnet at a time on Finney mainnet. That label helps readers anchor examples; it is not proof that every subnet shares the same live adjustment interval (Bittensor Networks).
Adjustment interval governs registration-burn recalibration cadence; Yuma Consensus still converts validator weights into emission shares each tempo on the active subnet (Yuma Consensus).
- Adjustment interval — block window between registration burn recalibrations on a subnet.
- Per-subnet boundary — live value is chain state on one netuid.
Distinction from Yuma Consensus
Adjustment interval is a per-subnet hyperparameter that sets the block window between dynamic registration burn recalibrations. It names registration-pricing cadence on the hyperparameter table, not the settlement step that converts validator weight submissions into emission shares (Subnet Hyperparameters, Glossary: Register).
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 tie adjustment interval to registration burn and per-subnet live values. Burn recalibration timing affects how expensive new UID slots become; Yuma settles evaluation signals from participants who already hold slots—not registration pricing itself (Yuma Consensus: Validator emissions).
Readers should treat adjustment interval as a registration hyperparameter on one netuid, and Yuma as the mechanism that allocates rewards from consensus.
- Adjustment interval — block window between registration burn recalibrations on one subnet.
- Yuma Consensus — epoch-boundary settlement from validator weights to emission shares.
Reader Boundary
Adjustment interval should not be read as a burn cost value, a registration count, or a miner’s
registration status. It names legacy interval-based registration-pricing vocabulary; live burn
economics on current subnets are set through BurnHalfLife and BurnIncreaseMult instead
(Subnet Hyperparameters).