SubnetLimit

Storage Re-added Plain v133 → v247, v320 → current

Maximum number of subnets allowed on the network.

Queried by: subnet ownersdevelopersanalytics

The 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.

Purpose & Usage

Purpose

Cap total subnet count for resource management.

Common Query Patterns

Single value query

Part of: Subnet Management

Stored Value

u16

value (u16)

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 });

// Query SubnetLimit storage (no keys - plain value)
const result = await api.query
  [stringCamelCase("SubtensorModule")]
  [stringCamelCase("SubnetLimit")]();
console.log("SubnetLimit:", result.toHuman());

Version History

Version:

v133 block 1,404,224 Added

v320 block 6,523,566 Re-added Current

Runtime Info

View Source

Pallet: SubtensorModule
Storage Kind: Plain
First Version: v133
Current Version: v393

Back to SubtensorModule Storage