DissolveNetworkScheduled

Event Re-added v195 → v212, v216 → v247, v252 → v265, v273 → v277, v290 → v315, v320 → v326, v334 → v367, v372 → v377, v385 → current #78

Emitted when network dissolution is scheduled for future execution.

View events on chain
Useful for: subnet ownersminersvalidatorsstakersanalytics

The Big Picture

Subnet dissolution isn't instant - it's scheduled in advance. This gives participants time to exit gracefully, move their operations elsewhere, and unstake before the subnet dies. The delay period protects miners, validators, and stakers from sudden 'rug pulls' by subnet owners. This event is the advance notice that a shutdown is coming.

Why This Matters

If a subnet you're operating on is scheduled for dissolution, you need to know NOW, not when it's already dead. This event gives you lead time to: unstake Alpha before rates might change, find new subnets to operate on, and generally prepare for the end.

Example Scenario

You're mining on subnet 47. The owner decides to shut it down. DissolveNetworkScheduled fires with netuid 47 and execution block 2,000,000 (one week away). You have a week to unstake, move your miner to another subnet, and adjust your infrastructure before subnet 47 ceases to exist.

Common Questions

Can dissolution be cancelled?
Potentially, if the subnet owner changes their mind before the execution block. Check if your runtime supports cancellation of scheduled dissolutions.
What happens to my stake when the subnet dissolves?
Alpha positions are typically converted/returned based on dissolution rules. Check the specific dissolution mechanics - it's better to exit proactively than rely on automatic handling.
How much notice do I get?
Check DissolveNetworkScheduleDuration for the minimum delay. It's designed to give meaningful time to prepare - usually days to weeks, not hours.

Use Cases

  • Get advance warning when a subnet will shut down
  • Plan exit strategy from dying subnets
  • Track subnet lifecycle and scheduled dissolutions
  • Build subnet health monitoring dashboards

How to Use This Event

  • → Monitor subnets you participate in for dissolution schedules
  • → Build countdown timers for scheduled dissolutions
  • → Alert users when their subnets are scheduled to close

From Chain Metadata

A dissolve network extrinsic scheduled.

Triggers

Preconditions

  • Caller is subnet owner
  • Subnet exists and is active

Effects

Postconditions

  • Dissolution scheduled after delay period

Side Effects

  • Gives participants time to exit subnet

Event Data

#NameTypeDescription
0
account
AccountId Account account address (hex -> SS58)
1
netuid
u16 Subnet/network identifier (0-65535)
2
execution_block
u32 execution_block (u32)

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

Version History

v195 block 3,791,350 3 args
v216 block 4,510,996 3 args
v252 block 5,163,656 3 args
v273 block 5,659,032 3 args
v290 block 5,947,548 3 args
v320 block 6,523,566 3 args
v334 block 6,811,690 3 args
v372 block 7,430,358 3 args
v385 block 7,782,670 3 args Current

Runtime Info

View Source
Pallet Index
7
Event Index
78
First Version
v195
Current Version
v393
Back to SubtensorModule Events