Current Value
64Relevant for: subnet ownersdevelopersanalytics
The Big Picture
Subnets need a minimum number of participants to function properly. This constant sets that floor. Too few UIDs means validators can't properly evaluate performance, emissions are too concentrated, and the subnet isn't providing meaningful decentralization. The minimum ensures subnets have critical mass.
Why This Matters
For subnet owners, you need to attract at least this many participants for proper functionality. For analytics, subnets at minimum size may have concentrated rewards.
Example
With MinAllowedUids of 16, a subnet must have at least 16 registered neurons. If a subnet drops below 16 (e.g., mass deregistration), it may face dissolution or require intervention.
Common Questions
- What happens if UIDs drop below minimum?
- Depends on runtime configuration. The subnet may be protected during immunity or face dissolution if inactive. Pruning is typically disabled below minimum.
- Can a new subnet start with fewer than minimum?
- Usually not. Subnets typically need to meet minimum before becoming active. Check specific subnet creation requirements.
From Chain Metadata
Initial minimum allowed network UIDs
Use Cases
- Subnet requirements
- Pruning limits
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 InitialMinAllowedUids constant
const value = api.consts[stringCamelCase("SubtensorModule")][stringCamelCase("InitialMinAllowedUids")];
console.log("InitialMinAllowedUids:", value.toHuman());Type Information
- Type
- u16
- Byte Size
- 2 bytes
- Encoding
- fixed
- Raw Hex
- 0x4000
Runtime Info
- Pallet
- SubtensorModule
- First Version
- v320
- Latest Version
- v320
- Current Runtime
- v393