SubnetLimitSet

Event Re-added v134 → v135, v136 → v141, v142 → v148, v149 → v165, v195 → v219, v233 → v247, v320 → v326, v334 → v367, v372 → current #60

Emitted when the maximum number of subnets is changed.

View events on chain

Useful for: subnet ownersdevelopersanalyticsvalidators

The Big Picture

The network has a maximum number of subnets it supports. This limit affects ecosystem growth - once full, no new subnets can be created until existing ones are dissolved. Increasing the limit opens doors for new subnet creators; decreasing it (if possible) constrains expansion.

Why This Matters

If you're planning to create a subnet, the limit matters. At capacity, you'd need to wait for a subnet to dissolve. Changes to the limit affect the entire ecosystem's growth trajectory and the scarcity of subnet slots.

Example Scenario

The network was full at 32 subnets. To allow ecosystem growth, they increase the limit to 64. SubnetLimitSet fires. 32 new subnet slots open up. If you've been waiting to create a subnet, now's your chance - reduced competition for slots.

Common Questions

What happens if the limit decreases below current count?: Existing subnets are typically safe (grandfathered). But no new subnets can be created until the count drops below the new limit through dissolution.
Why limit subnets at all?: Resource constraints (chain storage, processing), economic considerations (emission dilution), and quality control. Unlimited subnets could degrade the network.
How do I know if slots are available?: Compare current subnet count (TotalNetworks) to SubnetLimit. If count < limit, slots available. Track both to anticipate opportunities.

Use Cases

Track network-wide subnet capacity
Plan subnet creation opportunities
Monitor network expansion policies
Build subnet opportunity tracking tools

How to Use This Event

→ Track subnet limit for expansion opportunities
→ Monitor network growth policies
→ Build subnet availability forecasting

From Chain Metadata

the maximum number of subnets is set

Triggers

Preconditions

Caller has admin/sudo privileges

Effects

Postconditions

SubnetLimit updated

Side Effects

Affects ability to create new subnets

Event Data

#	Name	Type	Description
0	arg0	u16	Event field #0 (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 });

// Subscribe to SubnetLimitSet events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "SubnetLimitSet"
    )
    .forEach(({ event }) => {
      console.log("SubnetLimitSet:", event.data.toHuman());
    });
});

Version History

Version:

v134 block 1,455,498 1 args

v136 block 1,756,781 1 args

v142 block 2,543,779 1 args

v149 block 3,014,339 1 args

v195 block 3,791,350 1 args

v233 block 4,920,350 1 args

v320 block 6,523,566 1 args

v334 block 6,811,690 1 args

v372 block 7,430,358 1 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 60
First Version: v134
Current Version: v393

Back to SubtensorModule Events