RegistrationAllowed

Event Re-added v121 → v122, v123 → v127, v133 → v148, v149 → v165, v195 → v219, v233 → v247, v252 → v265, v273 → v277, v290 → v315, v320 → current #48

Emitted when registration is enabled or disabled for a subnet .

View events on chain

Useful for: minersvalidatorssubnet ownersanalyticsdevelopers

The Big Picture

Subnet owners can open or close registration entirely. Closed registration means no new neurons can join (the subnet is 'private' or 'full by design'). Open registration allows anyone who can pay burn/PoW. This event signals policy changes that affect your ability to join a subnet.

Why This Matters

You can't join a subnet with closed registration no matter how much you're willing to pay. This event tells you when the door opens or closes. Watch for openings on desirable subnets - they might be brief windows of opportunity.

Example Scenario

Subnet 12 was private during development (registration disabled). It's ready for public launch. RegistrationAllowed fires with netuid 12 and allowed=true. Registration is now open! This is your chance to join - be ready with burn or PoW.

Common Questions

Can I register during 'disabled' if I have special access?: Only if you're admin or have bulk registration privileges. Normal users cannot bypass disabled registration.
What's the difference between disabled registration and a full subnet?: Disabled means nobody can register, even if there's space. Full means registration works but you must beat an existing neuron to take their slot.
How do I know if registration is currently allowed?: Check the subnet's RegistrationAllowed storage value. Or try registering - you'll get a clear error if it's disabled.

Use Cases

Track when subnets open or close registration
Plan registration timing for new subnets
Monitor subnet access policies
Build subnet opportunity tracking tools

How to Use This Event

→ Monitor subnets you want to join for registration windows
→ Track registration policy changes across the network
→ Build alerts for registration openings on desired subnets

From Chain Metadata

registration is allowed/disallowed for a subnet.

Triggers

Preconditions

Caller has admin/sudo privileges

Effects

Postconditions

Registration enabled/disabled for subnet

Side Effects

If disabled, new neurons cannot register

Event Data

#	Name	Type	Description
0	arg0	u16	Event field #0 (u16)
1	arg1	bool	Event field #1 (bool)

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 RegistrationAllowed events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "RegistrationAllowed"
    )
    .forEach(({ event }) => {
      console.log("RegistrationAllowed:", event.data.toHuman());
    });
});

Version History

Version:

v121 block 518,345 2 args

v123 block 720,235 2 args

v133 block 1,404,224 2 args

v149 block 3,014,339 2 args

v195 block 3,791,350 2 args

v233 block 4,920,350 2 args

v252 block 5,163,656 2 args

v273 block 5,659,032 2 args

v290 block 5,947,548 2 args

v320 block 6,523,566 2 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 48
First Version: v121
Current Version: v393

Back to SubtensorModule Events