sudo_set_subnet_owner_hotkey
Call v252 → current #64Sets the hotkey that receives subnet owner emissions .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_subnet_owner_hotkey, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.SubnetOwnerHotkey, 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
Subnet owners earn a cut of emissions. This controls which hotkey receives those emissions.
Use Cases
- Changing owner receiving address
- Ownership transitions
From Chain Metadata
Change the SubnetOwnerHotkey for a given subnet.
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
- Valid hotkey
Effects
Storage Modified
Postconditions
- Subnet owner hotkey updated
Side Effects
- Owner emissions go to new hotkey
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_subnet_owner_hotkey call
const netuid = 1;
const hotkey = "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY";
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_subnet_owner_hotkey")](
netuid,
hotkey
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 64
- First Version
- v252
- Current Version
- v393