sudo_set_min_burn
Call v138 → current #22Sets the minimum burn amount for registration on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_min_burn, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MinBurn, 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
Even when demand is low, burn registration costs at least this much. Prevents trivial slot acquisition.
Use Cases
- Setting registration cost floor
- Preventing spam during low-demand periods
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
Effects
Storage Modified
Postconditions
- MinBurn updated
Side Effects
- Burn registration cannot cost less than this
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_burn call
const netuid = 1;
const min_burn = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_min_burn")](
netuid,
min_burn
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 22
- First Version
- v138
- Current Version
- v393