Bonds Reset Enabled
Bonds reset enabled is a per-subnet hyperparameter, listed in the documentation as
BondsResetEnabled, that determines whether validator-miner bonds on a subnet can be reset. The
reference describes it as a boolean defaulting to false, set through the
sudo_set_bonds_reset_enabled extrinsic at subnet owner permission
(Subnet Hyperparameters).
What Bonds Are
Validator-miner bonds represent a validator’s accumulated assessment of each miner’s performance over time and serve as the starting point of Yuma Consensus. Each epoch they are updated through an exponential moving average of validator weights and previous bond values, and validator dividends are computed by combining bonds with miner incentives (Glossary: Validator-Miner Bonds, Yuma Consensus).
What It Controls
The flag enables or disables bond resets on a subnet. When it is disabled, which is the default, bonds are not reset and the accumulated history carries forward; when it is enabled, a reset can be triggered so the affected bonds are cleared and rebuilt from scratch (Subnet Hyperparameters, Yuma Consensus).
A reset is not applied automatically each epoch. While the flag is enabled, a reset is invoked
through metadata commitment: the SDK documents get_last_commitment_bonds_reset_block as returning
the last block when bonds reset was triggered by publish_metadata for a neuron on the subnet
(Bittensor SDK: get_last_commitment_bonds_reset_block).
This flag should not be read as the only bond-clearing condition. Validator documentation also states that when a validator permit is lost, the neuron’s associated consensus bonds are deleted; that permit-loss path is separate from an owner-enabled reset workflow (Validating in Bittensor, Glossary: Validator Permit).
Why It Matters
Because bonds are the starting point of Yuma Consensus and feed validator dividends, clearing them changes which accumulated history counts toward rewards on the subnet. Enabling resets lets affected bonds rebuild from a clean state, while leaving the flag off keeps the existing bond history intact (Glossary: Validator-Miner Bonds, Yuma Consensus).
The YC3 documentation notes that bond reset functionality is available for subnets that need it, framing it as an optional tool rather than standard behavior, consistent with the default-off setting (Yuma Consensus 3).
Scope of a Reset
The protocol tracks resets by subnet and hotkey. The SDK’s get_last_bonds_reset lookup is keyed by
netuid and hotkey, so a reset clears the bonds associated with the affected hotkey on that subnet
rather than being a single network-wide wipe of every bond
(Bittensor SDK: get_last_bonds_reset).
Documented Type, Default, and Setter
The Subnet Hyperparameters
reference lists BondsResetEnabled as a Bool defaulting to false. It is changed through the
sudo_set_bonds_reset_enabled extrinsic, exposed in tooling as
btcli sudo set --param bonds_reset_enabled, and the reference marks the permission required to set
it as subnet owner. A change emits the BondsResetToggled on-chain event
(Subnet Hyperparameters).
Because each subnet carries its own value as per-netuid state, the flag on one netuid can differ from the documented default and from another subnet’s value (Subnet Hyperparameters).
Reading the Live Value for netuid 1
Bonds reset enabled is per-subnet chain state, so any live claim is tied to a specific netuid. For
the documented example netuid 1 on Finney mainnet, readers can verify the live flag with
btcli subnet hyperparameters --netuid 1 --network finney, which prints that subnet’s
hyperparameter table including this Boolean row
(Subnet Hyperparameters: View hyperparameters).
The infobox uses netuid 1 only as an example label; other subnets expose their own values
(Bittensor Networks).
Distinction from Bonds Moving Average
Bonds moving average sets the smoothing window for how bonds accumulate each epoch. Bonds reset enabled decides whether that accumulated bond can be cleared, so one shapes the ongoing update and the other governs wiping it (Subnet Hyperparameters).
- Bonds moving average — smoothing window for ongoing bond updates.
- Bonds reset enabled — whether accumulated bonds can be reset.
Distinction from Bonds Penalty
Bonds penalty subtracts from weights that exceed consensus. Bonds reset enabled does not penalize a weight value; it governs whether the bonds for an affected hotkey are cleared (Subnet Hyperparameters).
- Bonds penalty — magnitude subtracted for exceeding consensus.
- Bonds reset enabled — whether a hotkey’s bonds can be cleared.