sudo_set_max_allowed_uids
Call v138 → current #15Sets the maximum number of UIDs (neurons) allowed on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_max_allowed_uids, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MaxAllowedUids, 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
Controls subnet size. Larger subnets have more competition; smaller ones are more exclusive.
Use Cases
- Scaling subnet capacity
- Resource management
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
- Value >= current neuron count
Effects
Storage Modified
Postconditions
- MaxAllowedUids updated
Side Effects
- Affects subnet capacity
- May trigger deregistration if reduced below current count
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_uids call
const netuid = 1;
const max_allowed_uids = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_max_allowed_uids")](
netuid,
max_allowed_uids
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 15
- First Version
- v138
- Current Version
- v393