sudo_set_max_difficulty
Call v138 → current #5Sets the maximum POW difficulty for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_max_difficulty, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MaxDifficulty, 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
Sets a ceiling for POW registration difficulty. Prevents difficulty from becoming prohibitively high during demand spikes.
Use Cases
- Preventing runaway difficulty
- Capping registration barriers
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
- Value >= min_difficulty
Effects
Storage Modified
Postconditions
- MaxDifficulty updated for subnet
Side Effects
- Registration difficulty cannot exceed this ceiling
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_max_difficulty call
const netuid = 1;
const max_difficulty = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_max_difficulty")](
netuid,
max_difficulty
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 5
- First Version
- v138
- Current Version
- v393