sudo_set_tao_flow_cutoff
Call v334 → current #81Sets the TAO flow cutoff parameter.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with sudo_set_tao_flow_cutoff, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch and modifies storage: SubtensorModule.TaoFlowCutoff, 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 TAO flow mechanics between subnets and the main chain.
Use Cases
- Flow mechanics tuning
- Network economics
From Chain Metadata
Sets TAO flow cutoff value (A)
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | flow_cutoff | FixedI128 | flow_cutoff (FixedI128) |
Permissions
Origin
Root
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller is root account
Effects
Storage Modified
Postconditions
- TaoFlowCutoff updated
Side Effects
- Affects TAO flow 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_cutoff call
const flow_cutoff = 0 as any /* FixedI128 */;
const call = api.tx[stringCamelCase("AdminUtils")][stringCamelCase("sudo_set_tao_flow_cutoff")](
flow_cutoff
);Runtime Info
View Source- Pallet Index
- 19
- Call Index
- 81
- First Version
- v334
- Current Version
- v393