sudo_set_tao_flow_smoothing_factor
Call v334 → current #83Sets the TAO flow smoothing factor.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_tao_flow_smoothing_factor, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.FlowEmaSmoothingFactor, 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
Controls how quickly TAO flows respond to changes. Higher values mean smoother transitions.
Use Cases
- Smoothing TAO flows
- Reducing flow volatility
From Chain Metadata
Sets TAO flow smoothing factor (alpha)
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | smoothing_factor | u64 | smoothing_factor (u64) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- TaoFlowSmoothingFactor updated
Side Effects
- Affects flow smoothing
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_smoothing_factor call
const smoothing_factor = 0;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_tao_flow_smoothing_factor")](
smoothing_factor
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 83
- First Version
- v334
- Current Version
- v393