sudo_set_max_allowed_validators
Call v138 → current #25Sets the maximum number of validators allowed on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_max_allowed_validators, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MaxAllowedValidators, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
Used by: subnet owners
The Big Picture
Not all neurons are validators. This caps how many can participate in consensus on this subnet.
Use Cases
- Controlling validator count
- Balancing decentralization vs efficiency
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
- Value <= max_allowed_uids
Effects
Storage Modified
Postconditions
- MaxAllowedValidators updated
Side Effects
- Affects how many neurons can be validators
Code Examples
import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";
const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });
// Build sudo_set_max_allowed_validators call
const netuid = 1;
const max_allowed_validators = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_max_allowed_validators")](
netuid,
max_allowed_validators
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 25
- First Version
- v138
- Current Version
- v393