Analytics methodology
Where every figure in the TokenLabs IOTA validator analytics comes from, how it is computed and how often it is updated.
Back to analytics
Data sources
- On-chain state
- Validators, stake, voting power, protocol version and epochs are read from the public IOTA mainnet node and indexer (iotax_getLatestIotaSystemStateV2 and iotax_getEpochs).
- History since genesis
- Every closed epoch, from 0, is stored once: network economy and one row per validator. Nothing is recomputed backwards.
- Country and provider
- Each validator's node hostname is resolved and its IP is looked up in the public registry of network blocks (ASN). Only the country and provider are stored, never the IP.
Metrics
- Stake
- IOTA delegated to the validator's pool at the close of the last epoch.
- Voting power (VPower)
- The validator's weight in consensus according to the protocol, in %. The next epoch's value is shown: share of committee stake capped at 10 % per validator, with the surplus spread among the rest.
- APY
- Annual yield estimated by the network for the validator's pool in the current epoch.
- 1/3 and 2/3 thresholds
- Sorted by voting power, the line shows how many validators hold strictly more than 1/3 (they can halt the network) and more than 2/3 (they can finalize blocks).
- Nakamoto coefficient
- The minimum number of operators holding strictly more than 1/3 of voting power (nodes of the same operator count as one). Higher means more decentralized.
- HHI
- Herfindahl-Hirschman index of stake: the sum of the squared shares of each operator, from 0 to 10,000. Lower means more evenly spread.
- Gini
- Stake inequality between operators, from 0 (all equal) to 1 (all in one).
- Issuance and burn
- IOTA issued as staking rewards and IOTA burnt as gas in each epoch; net issuance is the difference.
- Average TPS
- The epoch's transactions divided by that epoch's duration in seconds (from its start to its close).
Update frequency
- Validator list
- Every 2 minutes on the page; the server caches the response for 60 seconds.
- Per-epoch history
- Every hour the last closed epoch is added (an epoch lasts about 24 hours).
- Country and provider
- Once a day.
Limitations
- A single vantage point
- Node performance figures are measured from our infrastructure; other nodes may see slightly different values.
- Third-party data
- Country and provider depend on public registries that can lag, and a node behind a proxy shows the proxy's provider.
Frequently asked questions
Are the TokenLabs analytics free?
Yes. Every figure and its CSV download is free and needs no sign-up or wallet.
What does the IOTA Nakamoto coefficient mean?
It is the minimum number of validators that together hold more than a third of voting power. The higher it is, the harder it is for a few to halt the network.
How often is the data updated?
The validator list every 2 minutes and the per-epoch history every hour, as each epoch closes.
Are validator IPs stored?
No. Only the country and network provider of each node are stored.