AdminFreezeWindow
Storage Plain v320 → currentWindow length at tempo end during which admin operations are frozen.
Explore chainQueried by: subnet ownersvalidatorsdevelopers
The Big Picture
To ensure fair epochs, admin operations (hyperparameter changes) are frozen near tempo boundaries. This storage defines that freeze window length in blocks. Changes attempted during the freeze will fail.
Use Cases
- Plan hyperparameter changes around freeze windows
- Understand when admin operations are blocked
- Build admin tooling aware of freeze periods
From Chain Metadata
Global window (in blocks) at the end of each tempo where admin ops are disallowed
Purpose & Usage
Purpose
Prevent hyperparameter changes near epoch boundaries.
Common Query Patterns
- Single value query
Stored Value
value (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 });
// Query AdminFreezeWindow storage (no keys - plain value)
const result = await api.query
[stringCamelCase("SubtensorModule")]
[stringCamelCase("AdminFreezeWindow")]();
console.log("AdminFreezeWindow:", result.toHuman());Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Plain
- First Version
- v320
- Current Version
- v393