Min Allowed Weights
Min allowed weights is a per-subnet hyperparameter that sets the minimum number of weights a validator must include when it sets weights on a subnet. Official documentation describes it as the minimum number of weights for a validator to set when setting weights.
References: Subnet Hyperparameters
What It Controls
The hyperparameter is a floor on the size of a validator’s weight submission. When a validator submits weights, the number of entries it assigns must meet this minimum. It does not say how a validator should score miners; it only sets how few weights a valid submission may contain.
Reference: Subnet Hyperparameters
Default and Setting
The documentation lists min allowed weights as a u16 value with a default of 1, and marks it as
owner-settable, so a subnet owner can raise it for their subnet. A value above one means a single
weight submission must cover more than one target. The value in force is per-subnet chain state and
can differ from the default.
Reference: Subnet Hyperparameters
Subnet Context
Min allowed weights is one of the subnet hyperparameters, the on-chain state variables that configure a single subnet, for example netuid 1. Because each subnet sets its own hyperparameters, the minimum can differ from one subnet to another, and it applies to weight submissions on that subnet.
Reference: Subnet Hyperparameters
Why It Matters
The minimum interacts with how validator weights feed Yuma Consensus. Weights are the validator inputs that get aggregated into a consensus result, and a higher minimum requires each validator’s submission to spread across more targets rather than concentrate on a single one. The hyperparameter constrains the form of valid weight input without dictating the scores themselves.
References: Subnet Hyperparameters, Yuma Consensus
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For min allowed weights, that sequence changes how readers should interpret validator weight-spread examples.
In localnet, min-allowed-weights hyperparameters can be tested in an isolated environment. Localnet weight submissions do not represent production consensus inputs.
On testnet, validator weight rules can be exercised in a shared non-production network. Testnet minimums are separate from mainnet subnet state.
On mainnet, min allowed weights is a live per-subnet hyperparameter on production subnets. Observed minimums depend on the selected subnet’s on-chain hyperparameter state (Subnet Hyperparameters).
The Bittensor Networks reference separates mainnet, testnet, and localnet. A min-allowed-weights example from one environment should not be read as representing production weight rules in another environment.
Relationship to Yuma Consensus
Min Allowed Weights and Yuma Consensus describe related parts of Bittensor’s incentive system. Yuma Consensus is the on-chain process that aggregates validator weight signals within a subnet into miner incentives and validator dividends, applying consensus clipping, bonding, and emission calculation (Yuma Consensus).
For readers, min Allowed Weights names a specific part of that incentive picture, while Yuma Consensus names the consensus process that turns validator weights into the resulting incentives and dividends.
Reader Boundary
This page defines the concept at a high level. It does not report the min-allowed-weights value set on any particular subnet or any validator’s current weight submission. Those are live chain state and should be checked for the relevant netuid. The default of 1 is the documented value, and the setting is owner-controlled per subnet.
Reference: Subnet Hyperparameters
The Weight Vector Lists Targets and Scores
The Glossary: Weight Vector describes a validator’s submission as a list of miner targets paired with evaluation scores. Min allowed weights sets how many entries that list must contain, not how those scores should be chosen or ranked.
That form rule sits upstream of Yuma Consensus. Consensus aggregates the submitted vectors into a result, while the minimum count hyperparameter decides whether a submission is structurally valid before that aggregation begins (Subnet Hyperparameters).
References: Glossary: Weight Vector, Subnet Hyperparameters
Activity Cutoff Times Validator Submissions
Subnet hyperparameters include an activity cutoff measured in blocks within each epoch. Official documentation states that a validator who does not submit validator weights within the first activity-cutoff blocks of the epoch cannot participate in the current epoch.
Min allowed weights and activity cutoff therefore govern different parts of the same submission. The minimum count rule shapes how many targets a valid vector must include, while the cutoff rule shapes how early in the epoch that vector must arrive.
References: Subnet Hyperparameters, Glossary: Epoch
Clipping Acts on Weight Values Not Entry Count
Yuma Consensus documentation describes consensus clipping as trimming weights that depart from the stake-weighted agreement point. That defense concerns how extreme individual scores are, which is separate from the min allowed weights floor on how many entries a submission must include.
A validator can meet the count minimum and still see inflated values clipped if they outlie the broader agreement. The hyperparameter constrains submission breadth; clipping constrains how far any included score can depart from consensus (Understanding Incentive Mechanisms).
References: Yuma Consensus, Understanding Incentive Mechanisms