Tokens processed in the epoch
Tokens a subnet's workers processed in one settlement epoch, as the operator's signed record sums them (Engy SN53:
tokens_total over its miners). Workers with hotkeys only: the operator's own clusters are not in it, so a lower bound of the subnet's traffic. One row per settled epoch, at the UTC hour the epoch starts (granularity 1h), covering the epoch's whole length (epoch_hours), not that hour: spreading it over days is the derive step's work. Only epochs the operator finalized and signed with its published key (sha256 of the result equals the signed digest) are stored.Definition
At a glance
- Key
epoch_tokens- Unit
- Tokens
- Aggregation
- SumA flow: weekly and monthly values add up the daily values in the period.
- Can be negative
- NoNegative values are treated as data errors and held back by the range check.
Sources
Where it comes from
Datasets that write this metric. When several sources provide it, each chart states which one it uses.
| Dataset | Source |
|---|---|
Engy settled epochs (operator-signed)engy.epochs | Engy |
Usage
Dashboards using it
No published dashboard uses this metric yet.
Time buckets, partial periods and restatements follow the site-wide conventions.