sudo_set_tempo
Call v138 → current #30Sets the tempo (epoch length) for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_tempo, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.Tempo, 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
Tempo defines how many blocks make up an epoch. Shorter tempos mean more frequent emissions and updates.
Use Cases
- Adjusting subnet responsiveness
- Tuning emission frequency
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- Tempo updated
Side Effects
- Affects emission frequency and consensus cycles
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_tempo call
const netuid = 1;
const tempo = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_tempo")](
netuid,
tempo
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 30
- First Version
- v138
- Current Version
- v393