sudo_set_mechanism_emission_split
Call v320 → current #77Sets how emissions are split between mechanisms on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_mechanism_emission_split, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.MechanismEmissionSplit, 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
For subnets with multiple mechanisms, controls how emissions are divided between them.
Use Cases
- Multi-mechanism emission tuning
- Balancing mechanism incentives
From Chain Metadata
Sets the emission split between mechanisms in a 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
Effects
Storage Modified
Postconditions
- MechanismEmissionSplit updated
Side Effects
- Changes emission distribution across mechanisms
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_mechanism_emission_split call
const netuid = 1;
const maybe_split = 0 as any /* Option */;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_mechanism_emission_split")](
netuid,
maybe_split
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 77
- First Version
- v320
- Current Version
- v393