sudo_set_start_call_delay
Call v372 → current #85Sets the delay before certain operations can start.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_start_call_delay, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.StartCallDelay, 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 operations have a mandatory delay before they take effect. This controls that delay.
Use Cases
- Operation scheduling
- Safety delays
From Chain Metadata
Sets the delay before a subnet can call start
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | delay | u64 | delay (u64) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- StartCallDelay updated
Side Effects
- Affects operation timing
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 });
// Build sudo_set_start_call_delay call
const delay = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_start_call_delay")](
delay
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 85
- First Version
- v372
- Current Version
- v393