StartCallDelaySet
Event v372 → current #58Emitted when start call delay is changed.
View events on chainUseful for: subnet ownersdevelopersanalytics
The Big Picture
Some operations have built-in delays before they take effect - a safety measure that gives participants time to react. The start call delay controls how long certain operations wait before executing. Changes affect timing-sensitive workflows and coordination.
Why This Matters
If operations you trigger have delays, this parameter affects when they actually happen. Changes to the delay affect your planning and timing. Longer delays mean more waiting; shorter delays mean faster execution.
Example Scenario
Certain governance operations had 1-hour delays. To speed up execution, the delay is reduced to 30 minutes. StartCallDelaySet fires. Operations now take effect 30 minutes after initiation instead of 1 hour.
Common Questions
- What operations are affected by this delay?
- Depends on implementation. Typically governance, scheduled operations, or time-sensitive actions. Check which specific calls use this delay parameter.
- Can the delay be zero?
- Potentially, but rare. Some delays exist for security reasons - instant execution might be risky. Check if there's a minimum enforced delay.
- Does this affect already-scheduled operations?
- Usually not - they use the delay from when they were scheduled. New operations use the updated delay.
Use Cases
- Track operational timing configuration
- Plan operations around delay requirements
- Monitor network configuration changes
- Build timing-aware automation tools
How to Use This Event
- → Monitor delay changes affecting your operations
- → Track timing configuration evolution
- → Build delay-aware automation
From Chain Metadata
the start call delay is set.
Triggers
Emitted by
Preconditions
- Caller has admin/sudo privileges
Effects
Storage Modified
Postconditions
- StartCallDelay updated
Side Effects
- Affects timing of start operations
Event Data
| # | Name | Type | Description |
|---|---|---|---|
| 0 | arg0 | u64 | Event field #0 (u64) |
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 StartCallDelaySet events
api.query.system.events((events) => {
events
.filter(({ event }) =>
event.section === stringCamelCase("SubtensorModule") &&
event.method === "StartCallDelaySet"
)
.forEach(({ event }) => {
console.log("StartCallDelaySet:", event.data.toHuman());
});
});Runtime Info
View Source- Pallet Index
- 7
- Event Index
- 58
- First Version
- v372
- Current Version
- v393