sudo_set_admin_freeze_window
Call v320 → current #74Sets the admin freeze window duration.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_admin_freeze_window, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.AdminFreezeWindow, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
Used by: subnet owners
The Big Picture
Some admin operations have freeze windows for safety. This controls that duration.
Use Cases
- Governance timing
- Admin operation scheduling
From Chain Metadata
Sets the admin freeze window length (in blocks) at the end of a tempo. Only callable by root.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | window | u16 | window (u16) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- AdminFreezeWindow updated
Side Effects
- Affects admin operation timing
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Build sudo_set_admin_freeze_window call (typed, named args)
const window = 0;
const tx = api.tx.AdminUtils.sudo_set_admin_freeze_window({
window,
});Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 74
- First Version
- v320
- Current Version
- v411