sudo_set_alpha_values
Call v156 → current #51Sets the alpha low and high values for a subnet .
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_alpha_values, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.AlphaValues, 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
Alpha values control aspects of how subnet-specific tokens (Alpha) behave and are valued.
Use Cases
- Tuning alpha token economics
- Adjusting subnet token curves
From Chain Metadata
Sets values for liquid alpha
Input Parameters
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root or subnet owner
- Subnet exists
- alpha_low < alpha_high
Effects
Storage Modified
Postconditions
- AlphaLow and AlphaHigh updated
Side Effects
- Affects alpha token mechanics
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_alpha_values call
const netuid = 1;
const alpha_low = 0;
const alpha_high = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_alpha_values")](
netuid,
alpha_low,
alpha_high
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 51
- First Version
- v156
- Current Version
- v393