sudo_set_liquid_alpha_enabled
Call v156 → current #50Enables or disables liquid alpha on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_liquid_alpha_enabled, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.LiquidAlphaOn, 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
Liquid alpha allows alpha tokens to be traded. Enables DeFi-style operations with subnet tokens.
Use Cases
- Enabling alpha liquidity features
- Subnet token mechanics
From Chain Metadata
Enables or disables Liquid Alpha 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
Storage Modified
Postconditions
- LiquidAlphaEnabled flag updated
Side Effects
- Changes how alpha tokens work 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_liquid_alpha_enabled call
const netuid = 1;
const enabled = true;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_liquid_alpha_enabled")](
netuid,
enabled
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 50
- First Version
- v156
- Current Version
- v393