SubnetLimit
Storage Re-added Plain v133 → v411 · 1× re-addedMaximum number of subnets allowed on the network.
Explore chainThe Big Picture
The network has limited subnet slots. This cap ensures manageable network size. When full, new subnets can only replace dissolved ones.
Use Cases
- Check if subnet creation is possible
- Monitor network capacity
- Plan subnet launches
From Chain Metadata
========================== ==== Staking Counters ==== ========================== The Subtensor [`TotalIssuance`] represents the total issuance of tokens on the Bittensor network. It is comprised of three parts: The total amount of issued tokens, tracked in the TotalIssuance of the Balances pallet The total amount of tokens staked in the system, tracked in [`TotalStake`] The total amount of tokens locked up for subnet reg, tracked in [`TotalSubnetLocked`] attained by iterating over subnet lock. Eventually, Bittensor should migrate to using Holds afterwhich time we will not require this separate accounting. ITEM ( maximum_number_of_networks )
Purpose & Usage
Purpose
Cap total subnet count for resource management.
Common Query Patterns
- Single value query
Stored Value
maximum_number_of_networks (u16)
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Query SubnetLimit storage (no keys - plain value)
const result = await api.query.SubtensorModule.SubnetLimit.getValue();
console.log("SubnetLimit:", result);Version History
Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Plain
- First Version
- v133
- Current Version
- v411