sudo_set_adjustment_interval
Call v138 → current #8Sets the difficulty adjustment interval for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_adjustment_interval, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.AdjustmentInterval, 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
Controls how often the subnet recalculates registration difficulty based on demand. Shorter intervals mean faster adaptation.
Use Cases
- Tuning difficulty responsiveness
- Smoothing registration curves
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- AdjustmentInterval updated
Side Effects
- Changes how often difficulty recalculates
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_adjustment_interval call
const netuid = 1;
const adjustment_interval = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_adjustment_interval")](
netuid,
adjustment_interval
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 8
- First Version
- v138
- Current Version
- v393