SubnetTaoInEmission
Storage Map Poll per block v233 → v411TAO amount emitted into each subnet on the LAST block .
Explore chainQueried by: analyticsdevelopers
The Big Picture
TAO flows into subnets via emissions. This tracks the per-block rate of TAO entering each subnet from the emission system. To compute period totals, integrate across blocks.
Use Cases
- Track emission rates
- Research subnet economics
- Build emission dashboards
From Chain Metadata
MAP ( netuid ) --> tao_in_emission | Returns the amount of tao emitted into this subent on the last block.
Purpose & Usage
Purpose
Track per-block TAO inflow from emissions. Value is overwritten every block — represents the most recent block emission, not a cumulative total.
Common Query Patterns
- Query by netuid
- Subscribe per-block for inflow tracking
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | netuid | u16 | netuid (u16, hashed key component) |
Stored Value
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 SubnetTaoInEmission storage
const netuid = 1;
const result = await api.query.SubtensorModule.SubnetTaoInEmission.getValue(netuid);
console.log("SubnetTaoInEmission:", result);Version History
v233 block 4,920,350 Added
v278–v289 · runtime versions skipped on chain (never deployed)
v290 block 5,947,548 Internal re-bind
v353–v360 · runtime versions skipped on chain (never deployed)
v361 block 7,063,679 Internal re-bind Current
Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Map
- First Version
- v233
- Current Version
- v411
- Update Pattern
- overwritten-at-event (every block (on_initialize))