DissolveNetworkScheduleDurationSet

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

Emitted when dissolve network schedule duration is changed.

View events on chain

Useful for: subnet ownersvalidatorsminersstakersanalytics

The Big Picture

When a subnet owner schedules dissolution, it doesn't happen immediately - there's a waiting period. This parameter controls that duration, giving participants time to exit before the subnet dies. Longer durations mean more notice; shorter durations mean faster dissolution but less preparation time.

Why This Matters

When a subnet you're on schedules dissolution, this duration is your warning window. Longer durations give you more time to unstake, move operations, and prepare. Changes affect how much notice you'll get for future dissolutions.

Example Scenario

Dissolution notice was 3 days. To give participants more preparation time, it's extended to 7 days. DissolveNetworkScheduleDurationSet fires. Future subnet dissolutions now require 7 days notice instead of 3 - more time for participants to exit gracefully.

Common Questions

Does this affect already-scheduled dissolutions?: Usually not - they use the duration from when scheduled. New dissolution schedules use the updated duration.
Can a subnet owner cancel a scheduled dissolution?: Potentially, during the waiting period. Check if cancellation is supported. If so, the duration is also the cancellation window.
What's a typical dissolution duration?: Usually days to weeks - long enough for meaningful preparation. Check the current value for your network's specific duration.

Use Cases

Track dissolution notice period requirements
Plan responses to scheduled dissolutions
Monitor subnet lifecycle policies
Build dissolution countdown tools

How to Use This Event

→ Monitor dissolution duration for exit planning
→ Track network lifecycle policies
→ Build dissolution countdown and alert tools

From Chain Metadata

The duration of dissolve network has been set

Triggers

Emitted by

dissolve_network schedule_dissolve_network

Preconditions

Caller has admin/sudo privileges

May fail with

NetworkDoesNotExist SubNetworkDoesNotExist RootNetworkDoesNotExist NetworkExist HotKeyNotRegisteredInNetwork EmissionValuesDoesNotMatchNetworks DidNotPassConnectedNetworkRequirement NetworkTxRateLimitExceeded IncorrectNetworkVersionKey AllNetworksInImmunity CanNotSetRootNetworkWeights

Effects

Storage Modified

ColdkeySwapScheduled NetworksAdded SubnetOwner TotalNetworks

Postconditions

Duration for network dissolution schedule updated

Side Effects

Affects how long before scheduled dissolutions execute

Event Data

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

Version History

Version:

v195 block 3,791,350 1 args

v216 block 4,510,996 1 args

v252 block 5,163,656 1 args

v273 block 5,659,032 1 args

v290 block 5,947,548 1 args

v320 block 6,523,566 1 args

v334 block 6,811,690 1 args

v372 block 7,430,358 1 args

v385 block 7,782,670 1 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 81
First Version: v195
Current Version: v393

Back to SubtensorModule Events