sudo_set_tao_flow_normalization_exponent
Call v334 → current #82Sets the TAO flow normalization exponent.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_tao_flow_normalization_exponent, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.FlowNormExponent, 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
Normalization exponent affects how TAO flows are distributed across the network.
Use Cases
- Flow distribution tuning
- Balancing TAO flows
From Chain Metadata
Sets TAO flow normalization exponent (p)
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | exponent | FixedU128 | exponent (FixedU128) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- TaoFlowNormalizationExponent updated
Side Effects
- Affects flow normalization calculations
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_tao_flow_normalization_exponent call
const exponent = 0 as any /* FixedU128 */;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_tao_flow_normalization_exponent")](
exponent
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 82
- First Version
- v334
- Current Version
- v393