MinAllowedUidsSet

Event Re-added v320 → v326, v334 → v367, v372 → v377, v385 → current #109

Emitted when minimum allowed UIDs is changed.

Useful for: subnet ownersvalidatorsminersanalytics

The Big Picture

Subnets need a minimum number of participants to function properly. MinAllowedUids sets this floor - the subnet can't shrink below this size. This ensures there are always enough miners and validators for meaningful consensus. Too few participants makes the subnet non-functional.

Why This Matters

If a subnet shrinks toward MinAllowedUids, it's approaching critical mass. Below this threshold, the subnet might malfunction or have governance issues. As a participant, knowing the minimum helps you evaluate subnet health and stability.

Example Scenario

A subnet had MinAllowedUids of 8. To ensure more robust consensus, they increase it to 16. MinAllowedUidsSet fires. The subnet now requires at least 16 active neurons. If it drops below 16, registration might be restricted or special measures taken.

Common Questions

What happens if the subnet is below minimum?: Depends on implementation. Could restrict further departures, trigger special registrations, or flag the subnet as unhealthy. Subnets generally try to stay above minimum.
Does this affect max UIDs?: No, min and max are independent. A subnet could have MinAllowedUids of 16 and MaxAllowedUids of 256 - the allowed range is 16-256.
What's a typical MinAllowedUids?: Small numbers like 8-32 are common. The minimum needs to support functional consensus without setting the bar so high that new subnets can't launch.

Use Cases

Track minimum subnet size requirements
Understand subnet viability thresholds
Monitor subnet configuration policies
Build subnet health dashboards

How to Use This Event

→ Monitor minimum size requirements across subnets
→ Track changes affecting subnet viability
→ Build subnet health monitoring tools

From Chain Metadata

The minimum allowed UIDs for a subnet have been set.

Triggers

Preconditions

Caller has admin/sudo privileges

Effects

Postconditions

MinAllowedUids updated

Side Effects

Sets minimum subnet size

Event Data

#	Name	Type	Description
0	arg0	u16	Event field #0 (u16)
1	arg1	u16	Event field #1 (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 MinAllowedUidsSet events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "MinAllowedUidsSet"
    )
    .forEach(({ event }) => {
      console.log("MinAllowedUidsSet:", event.data.toHuman());
    });
});

Version History

Version:

v320 block 6,523,566 2 args

v334 block 6,811,690 2 args

v372 block 7,430,358 2 args

v385 block 7,782,670 2 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 109
First Version: v320
Current Version: v393

Back to SubtensorModule Events