NetworkRateLimit
Storage Plain v133 → currentBlocks between allowed subnet creations.
Explore chainQueried by: subnet ownersdevelopersanalytics
The Big Picture
The network can't absorb unlimited subnets at once. NetworkRateLimit enforces pacing - after a subnet is created, the network waits this many blocks before allowing another. Ensures orderly network expansion.
Why This Matters
Want to create a subnet? Check when the last one was created. You must wait NetworkRateLimit blocks from NetworkLastRegistered before creating another.
Example Scenario
Query NetworkRateLimit() returns 7200 blocks (~4 hours). After someone creates a subnet, everyone must wait 4 hours before the next creation is allowed.
Common Questions
- Why limit creation rate?
- Network stability. Too many new subnets at once could overwhelm resources and make discovery chaotic. Pacing ensures orderly growth.
- Does this affect all subnet creators?
- Yes, it's network-wide. One person creating a subnet affects everyone's ability to create for the rate limit period.
Use Cases
- Check when next subnet creation is allowed
- Plan subnet launch timing
- Research network growth controls
- Build subnet creation timing tools
- Understand network expansion dynamics
Purpose & Usage
Purpose
Rate limit new subnet creation - prevents rapid network flooding.
Common Query Patterns
- Single value query
- Plan subnet creation timing
- Understand network pacing
Stored Value
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 NetworkRateLimit storage (no keys - plain value)
const result = await api.query
[stringCamelCase("SubtensorModule")]
[stringCamelCase("NetworkRateLimit")]();
console.log("NetworkRateLimit:", result.toHuman());Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Plain
- First Version
- v133
- Current Version
- v393