sudo_set_min_allowed_uids
Call v320 → current #79Sets the minimum number of UIDs required on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_min_allowed_uids, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MinAllowedUids, 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
Sets a floor for subnet size. The subnet won't deregister neurons below this count.
Use Cases
- Guaranteeing minimum subnet size
- Stability requirements
From Chain Metadata
The extrinsic sets the minimum allowed UIDs for a subnet. It is only callable by the root account.
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
- Value <= current count and <= max_allowed_uids
Effects
Storage Modified
Postconditions
- MinAllowedUids updated
Side Effects
- Subnet cannot shrink below this size
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_min_allowed_uids call
const netuid = 1;
const min_allowed_uids = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_min_allowed_uids")](
netuid,
min_allowed_uids
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 79
- First Version
- v320
- Current Version
- v393