AdminFreezeWindowSet

Event v320 → current #42

Emitted when admin freeze window is changed.

Useful for: subnet ownersdevelopersanalyticsvalidators

The Big Picture

Admin freeze windows are periods during which certain administrative actions are blocked - a decentralization measure that limits when admins can intervene. This parameter controls the freeze window duration. Longer windows mean more time without admin intervention; shorter windows mean admins can act more frequently.

Why This Matters

Admin freeze windows affect when administrative actions can occur. If you're waiting for an admin action, or planning around admin capabilities, understanding the freeze window helps you set realistic expectations.

Example Scenario

Admin freeze window was 24 hours. To increase decentralization, it's extended to 72 hours. AdminFreezeWindowSet fires. Admins now can't intervene for 72-hour periods instead of 24. The network operates more autonomously.

Common Questions

What actions are frozen during the freeze window?: Typically sensitive admin operations - parameter changes, emergency interventions, etc. Critical security actions might be exempt. Check specific freeze window rules.
Why have freeze windows at all?: Decentralization and trust. Freeze windows limit admin power, ensuring the network can operate without constant admin intervention. It's a governance constraint.
When does the freeze window apply?: Check the freeze window schedule. It might be continuous, periodic, or triggered by certain events. The specific timing depends on implementation.

Use Cases

Track admin action freeze periods
Plan administrative operations around freeze windows
Monitor governance timing policies
Build admin scheduling tools

How to Use This Event

→ Monitor freeze window changes
→ Track governance policy evolution
→ Build admin action scheduling tools

From Chain Metadata

setting the admin freeze window length (last N blocks of tempo)

Triggers

Preconditions

Caller has admin/sudo privileges

Effects

Postconditions

AdminFreezeWindow updated

Side Effects

Affects when admin actions are frozen

Event Data

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

Runtime Info

View Source

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

Back to SubtensorModule Events