sudo_set_subtoken_enabled
Call v273 → current #66Enables or disables subtoken (Alpha ) on a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_subtoken_enabled, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.SubtokenEnabled, 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
Subtokens (Alpha) are subnet-specific tokens. This controls whether a subnet has Alpha functionality.
Use Cases
- Enabling subnet tokens
- Token mechanics control
From Chain Metadata
Enables or disables subtoken trading 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
- SubtokenEnabled flag updated
Side Effects
- Enables/disables Alpha token functionality
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_subtoken_enabled call
const netuid = 1;
const subtoken_enabled = true;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_subtoken_enabled")](
netuid,
subtoken_enabled
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 66
- First Version
- v273
- Current Version
- v393