sudo_set_min_difficulty
Call v138 → current #4Sets the minimum POW difficulty for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_min_difficulty, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MinDifficulty, 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 floor for POW registration difficulty. Even if registration demand is low, difficulty won't drop below this.
Use Cases
- Preventing difficulty from dropping too low
- Maintaining minimum security guarantees
Input Parameters
Permissions
Origin
Root
Required Role
Requirements
- Caller is root or subnet owner
- Subnet exists
- Value <= max_difficulty
Effects
Storage Modified
Postconditions
- MinDifficulty updated for subnet
Side Effects
- Registration difficulty cannot go below this floor
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_min_difficulty call
const netuid = 1;
const min_difficulty = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_min_difficulty")](
netuid,
min_difficulty
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 4
- First Version
- v138
- Current Version
- v393