Liquid Alpha Enabled
Liquid alpha enabled is the per-subnet switch that turns on the liquid alpha feature, named
LiquidAlphaEnabled in the
Subnet Hyperparameters reference.
It is a boolean, owned by the subnet owner, and defaults to false.
What It Decides
The alpha value controls how quickly validator-miner bonds smooth over time. This toggle decides which kind of alpha a subnet uses: when it is off, the subnet relies on a single fixed alpha for that smoothing; when it is on, the alpha is allowed to vary across a range instead of staying constant (Subnet Hyperparameters).
With the feature on, the alpha low
and alpha high values become the
lower and upper bounds of that range, and where a given validator-miner pair lands inside it depends
on their consensus alignment, shaped by alpha_sigmoid_steepness
(Subnet Hyperparameters).
When the feature is off, that single fixed alpha is not a separate setting. Documentation describes
the subnet-wide smoothing factor as derived from BondsMovingAverage—one minus the scaled
bonds-moving-average value—rather than from the alpha low and alpha high bounds. A higher
BondsMovingAverage therefore produces a smaller disabled-path alpha, which slows bond-history
updates subnet-wide until the toggle is turned on
(Subnet Hyperparameters: BondsMovingAverage,
Subnet Hyperparameters: LiquidAlphaEnabled,
Consensus-based Weights,
Yuma Consensus: Bonding mechanics).
When It Matters
A common misconception is that setting alpha low and alpha high alone changes how a subnet smooths bonds. Those bounds describe a range that is only consulted when liquid alpha is enabled. Because the toggle defaults to false, a subnet that has tuned its alpha bounds but never enabled the feature is still using a single fixed alpha, and the bounds sit inert until the switch is turned on (Subnet Hyperparameters).
This is why the toggle is worth checking before reasoning about a subnet’s bond behavior. On netuid
1, for instance, the active value lives among the subnet’s hyperparameters keyed by that netuid, so
reading netuid 1’s liquid_alpha_enabled tells you whether its alpha low and alpha high bounds are
actually in force or merely configured. When the toggle is false, the next read for bond-smoothing
behavior is BondsMovingAverage on that netuid rather than the alpha bounds
(Subnet Hyperparameters: View hyperparameters,
Subnet Hyperparameters: BondsMovingAverage,
Subnet Hyperparameters).
Why It Is a Toggle
Keeping liquid alpha behind an explicit per-subnet switch lets each subnet opt into consensus-driven smoothing only when its owner wants that responsiveness, while subnets that prefer predictable, constant smoothing simply leave it off. Since it is owner-settable per netuid, one subnet enabling the feature does not change how any other subnet smooths its bonds (Subnet Hyperparameters).
Documented Setter
The hyperparameter reference lists the btcli setter as
btcli sudo set --param liquid_alpha_enabled and the underlying setter extrinsic as
sudo_set_liquid_alpha_enabled, with subnet-owner permission required. That means the switch is
changed per subnet rather than by editing alpha low or alpha high directly
(Subnet Hyperparameters: LiquidAlphaEnabled).
Distinction from Alpha High and Alpha Low
The toggle and the bounds answer different questions. Liquid alpha enabled decides whether a varying alpha is used at all, while alpha high and alpha low only define the range it varies within once the feature is on (Subnet Hyperparameters).
- Liquid alpha enabled — whether the alpha varies at all.
- Alpha high / alpha low — the upper and lower bounds it varies between.
Distinction from Yuma Version
Liquid alpha enabled does not choose the Yuma Consensus version. The Yuma version flag selects whether a subnet runs the v2 or v3 consensus path, while liquid alpha enabled controls whether alignment-varying bond smoothing is active inside the path that supports it. The current documentation describes liquid-alpha smoothing as applying on the v3 bonding path rather than as a replacement for enabling Yuma v3 (Subnet Hyperparameters, How Yuma Consensus 3 Makes Bittensor More Fair).
- Liquid alpha enabled — toggles variable bond-smoothing alpha.
- Yuma version — selects whether the subnet runs Yuma Consensus v2 or v3.
Distinction from Liquid Alpha
Liquid alpha enabled is the per-subnet toggle that turns the feature on or off. Liquid alpha names the consensus-aligned bond-smoothing behavior that varies per validator-miner pair between alpha low and alpha high when the toggle is true (Subnet Hyperparameters: LiquidAlphaEnabled, Consensus-based Weights).
- Liquid alpha enabled — whether variable bond-smoothing alpha is active on the subnet.
- Liquid alpha — the per-pair bounded smoothing behavior when the toggle is on.
Distinction from Bonds Moving Average
When liquid alpha is disabled, bond smoothing follows the subnet-wide alpha derived from bonds moving average rather than the alpha low and alpha high bounds. Liquid alpha enabled decides whether that alternate per-pair path is active at all (Subnet Hyperparameters: BondsMovingAverage, Yuma Consensus: Bonding mechanics).
- Liquid alpha enabled — whether consensus-driven per-pair smoothing is active.
- Bonds moving average — hyperparameter that sets the fixed smoothing path when the toggle is off.
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 toggle and bound claims tied to a parseable netuid on the selected subnet (Bittensor Networks).
Reader Boundary
Liquid alpha enabled should not be read as liquid alpha itself, as alpha low or alpha high, or as the live smoothing alpha a subnet applies each epoch. It names the per-netuid toggle that selects variable per-pair bond smoothing versus the bonds-moving-average path. The boolean is readable through subnet hyperparameters on a selected netuid; alpha bounds and the resulting smoothing alpha are separate reads (Subnet Hyperparameters: LiquidAlphaEnabled, Subnet Hyperparameters: View hyperparameters, Consensus-based Weights).