FlowNormExponent
Storage Plain v334 → v411 Changed in v411Normalization exponent for TAO flow calculations.
Explore chainQueried by: developersanalytics
The Big Picture
The flow normalization exponent (p) affects how TAO flow values are scaled. Part of the economic formula determining subnet weight based on flow dynamics.
Use Cases
- Understand flow normalization
- Research subnet economics
From Chain Metadata
ITEM --> Flow Normalization Exponent (p)
Purpose & Usage
Purpose
Control flow normalization in subnet economics.
Common Query Patterns
- Single value query
Stored Value
value (FixedU128)
Decoding the value
FixedU128 (Q64.64 fixed-point)FixedU128 encodes as Q64.64: raw bits divided by 2^64 gives the rational. Magnitude > 0 means non-zero.
const fraction = Number(value as bigint) / 2 ** 64;Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Query FlowNormExponent storage (no keys - plain value)
const result = await api.query.SubtensorModule.FlowNormExponent.getValue();
console.log("FlowNormExponent:", result);Version History
v334 block 6,811,690 Added
v353–v360 · runtime versions skipped on chain (never deployed)
v361 block 7,063,679 Internal re-bind
v363–v364 · runtime versions skipped on chain (never deployed)
v365 block 7,135,419 Internal re-bind
v386–v390 · runtime versions skipped on chain (never deployed)
v391 block 7,782,857 Internal re-bind
v394–v400 · runtime versions skipped on chain (never deployed)
v401 block 8,036,576 Internal re-bind
v403–v410 · runtime versions skipped on chain (never deployed)
v411 block 8,283,784 Internal re-bind Current
Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Plain
- First Version
- v334
- Current Version
- v411