sudo_set_subnet_limit
Call Re-added v138 → v306, v320 → current #37Sets the maximum number of subnets allowed on the network.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_subnet_limit, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.SubnetLimit, 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
Limits total subnets to prevent unbounded growth. New subnets may need to compete to join.
Use Cases
- Network capacity planning
- Resource management
From Chain Metadata
The extrinsic sets the subnet limit for the network. It is only callable by the root account. The extrinsic will call the Subtensor pallet to set the subnet limit.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | max_subnets | u16 | max_subnets (u16) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
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_subnet_limit call
const max_subnets = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_subnet_limit")](
max_subnets
);Version History
v138 block 1,907,363 1 args
v320 block 6,523,566 1 args Current
Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 37
- First Version
- v138
- Current Version
- v393