sudo_set_yuma3_enabled
Call v273 → current #69Enables or disables Yuma3 consensus on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_yuma3_enabled, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: Yuma3EnableToggled and modifies storage: SubtensorModule.Yuma3On, 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
Yuma3 is an updated consensus mechanism. This toggle allows subnets to opt into the new version.
Use Cases
- Enabling new consensus features
- Subnet upgrades
From Chain Metadata
Enables or disables Yuma3 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
Effects
Events Emitted
Storage Modified
Postconditions
- Yuma3Enabled flag updated
- Yuma3EnableToggled event emitted
Side Effects
- Changes consensus mechanism used on subnet
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_yuma3_enabled call
const netuid = 1;
const enabled = true;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_yuma3_enabled")](
netuid,
enabled
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 69
- First Version
- v273
- Current Version
- v393