Yuma3 Enabled
Yuma3 enabled is the per-subnet toggle that selects which version of the consensus mechanism a
subnet runs. The
Subnet Hyperparameters reference
documents it as YumaVersion: a boolean that defaults to false, is settable by the subnet owner,
and “toggles the consensus mechanism used by the subnet between Yuma Consensus v2 and v3.” Its
setter extrinsic is sudo_set_yuma3_enabled
(Subnet Hyperparameters).
What It Switches
Yuma Consensus computes validator and miner emissions and maintains the validator-miner bonds that reward validators for aligning with consensus. This toggle chooses between two versions of that mechanism: with it off the subnet stays on Yuma Consensus v2, and with it on the subnet uses Yuma Consensus 3 (YC3), which the migration guide describes as improving validator fairness, bond mechanics, and precision (Subnet Hyperparameters, YC3 Migration Guide).
When It Matters
A common misconception is that subnets move to YC3 automatically. They do not: the migration guide states a subnet keeps functioning under the previous version until its owner explicitly enables YC3, so the upgrade is opt-in per subnet rather than a network-wide change (YC3 Migration Guide).
The toggle also relates to liquid alpha. The migration guide notes YC3 works with liquid alpha only when liquid alpha is itself enabled and the required consensus values and activity are present, so enabling liquid alpha is not a substitute for moving to YC3 (YC3 Migration Guide).
A Per-Subnet Setting
Because YumaVersion is a subnet hyperparameter, each subnet carries its own value, and one subnet
switching versions does not change any other subnet
(Subnet Hyperparameters). For a
given subnet such as netuid 1, the value is part of that subnet’s hyperparameters and is read from
there rather than from a single global flag, which is why two subnets can run different consensus
versions at the same time
(Subnet Hyperparameters).
Distinction from Liquid Alpha Enabled
The two toggles are related but separate. Yuma3 enabled selects the consensus version, while liquid alpha enabled controls whether the alpha used in bond smoothing varies across its configured range (Subnet Hyperparameters, Consensus-based Weights).
- Yuma3 enabled — which Yuma Consensus version (v2 or v3) the subnet uses.
- Liquid alpha enabled — whether the bond-smoothing alpha varies across its range.