Call Workflow
This diagram shows the call execution flow: starting with sudo_set_ck_burn, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.CKBurn, 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
Coldkey swaps have a cost to prevent abuse. This sets that cost.
Use Cases
- Security economics
- Controlling key rotation costs
From Chain Metadata
Sets the childkey burn for a subnet. It is only callable by the root account. The extrinsic will call the Subtensor pallet to set the childkey burn.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | burn | u64 | burn (u64) (RAO -> TAO (/ 10^9)) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Build sudo_set_ck_burn call (typed, named args)
const burn = 0n;
const tx = api.tx.AdminUtils.sudo_set_ck_burn({
burn,
});Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 73
- First Version
- v315
- Current Version
- v411