IoTeX (IOTX) — the network, measured

Generated 2026-09-02T16:52:42Z from live ClickHouse queries against this estate's ledger. Held inventory: 7,846 observations · 43 distinct series · 8 upstream sources · first row 2026-08-09 17:15:20 · newest row 2026-09-02 16:49:30 · 7,846/7,846 rows carry a verify_url. 37 series refreshed in the last 24h (800 fresh rows). Nothing on this page is cached, estimated, or remembered.

Provenance — where every number comes from

8 source families feed this network's ledger. Every row they wrote carries its own source, as_of and verify_url; this table is the live rollup of that.

30-day history — headline series (daily last-value, live)

One row per series: latest value, a 30-day sparkline of daily last-known values (scaled to the series' own min→max), day count, and window change. Series absent from the 30-day window are omitted from this table, not zero-filled.

Market reference — CoinGecko coin page, as held

Market-data reference rows: price, supply, capitalisation, diluted valuation, and the published change columns including ATH/ATL. These are the coin-page reference's own numbers — the estate does not model, smooth, or forward-fill them. The change columns / rank / ATH-ATL / high-low series start later in the archive than the price rows (each metric's caveat in the full inventory states its own first-held row) and are shown from their first held row. The circulating and total supply rows are different quantities (circulating vs total) and are never netted against each other or against the chain-side contract reads in the token section below — different measurements from different endpoints, shown side by side.

Protocol fees — DefiLlama, as held (1y and all-time windows only)

Protocol-level fees from DefiLlama's public summary API for iotex. The iotex fees adapter exposes no 24h and no 30-day windows (both keys are absent — None — at the origin, verified by live probe during generation) and it exposes no revenue slice (a null revenue adapter means the collector's documented skip rule applies), so only the 1-year and all-time windows are held and published here. There is no revenue section on this page — absence, not zero.

Chain financials — DefiLlama chain-level series, as held

Three chain-level measurements of the IoTeX blockchain itself, each from a different DefiLlama endpoint with its own verify_url: DEX volume across the chain's decentralised exchanges, total chain TVL, and stablecoins circulating on the chain. These are chain aggregates — they are not protocol-level rows and are never merged with any other family on this page.

Network telemetry — first-party reads of the IoTeX Babel RPC, as held

First-party JSON-RPC reads of the network's own public endpoint (babel-api.mainnet.iotex.io) by the estate's iotex_collector.py. The collector also reads a totalSupply series; it has written no such rows into the archive as of generation, so no supply row appears here — absence, not zero; the query reruns at every regeneration.

Token counters — eth.blockscout ERC-20 reads, as held

On-chain counters for the IOTX ERC-20 token contract 0x6fb3e0a217407efff7ca062d46c26e5d60a14d69 on ethereum (the catalog lists IoTeX's chains as base,ethereum): holders, transfers, transactions, gas used, the top holder's balance, and the contract's own totalSupply read. These are cumulative counters published raw — never differenced into rates. The holders/transfer counters describe the bridged ERC-20 contract, not IoTeX-native accounts; the estate holds no IoTeX-native account telemetry.

Dev velocity — GitHub, as held

Raw GitHub API counters for iotexproject — repo-level (iotexproject/iotex-core) and one org-level row (public_repos via api.github.com/orgs/iotexproject, a different measurement from the repo rows; each keeps its own verify_url). Counters are published raw, never differenced into rates.

Full metric inventory — 43 measured series, each with provenance

Every series held for IOTX with rows in the last 30 days: latest value, when it was observed, which source observed it, how many rows we hold, how many of the last 30 days it reported, its comparability grade, and the origin link. "days/30" counts distinct dates with at least one row in the window.

Revision ledger — 0 backward revision(s) recorded for IOTX

Backward revisions are values upstream later replaced for a date we had already archived. The before-value is retained — that retention is the only reason a rewrite is detectable, and it is the part every overwriting vendor discards.

The ledger query ran during generation and returned 0 rows for IOTX. Zero here is the live query result, not a gap — the ledger itself is at /v1/revisions.

Estate grades for IOTX (graded 2026-08-20 13:54:15.000)

Served by /v1/network/IOTX — the same grades a paying agent receives. Scores are the engines' own 0–100 outputs, not ours to smooth. The revenue grade is F and data coverage D, and they are published exactly as computed: the estate holds no protocol-revenue adapter rows for IOTX (DefiLlama's iotex adapter exposes none) and 43 of the estate's measured series — the unflattering parts ship with the flattering ones, unsmoothed.

Verify any cell yourself — the exact commands

No account, no key, no trust required. Commands 1–5 hit the same upstream endpoints our collectors do (the coingecko.com browser coin page 403s plain curl, so the programmatic markets endpoint is given, id iotex); command 6 hits this estate's public API, where every row carries the same source / as_of / verify_url fields. One polite call per endpoint, no hammering.

# 1) The network's own Babel JSON-RPC — keyless, as of 2026-09-02T16:52:42Z:
#    (chain head height) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}' "https://babel-api.mainnet.iotex.io"
#    (gas price, wei -> the held gas_price_gwei is this / 1e9) curl -s -X POST -H "Content-Type: application/json" --data-binary '{"jsonrpc":"2.0","id":1,"method":"eth_gasPrice","params":[]}' "https://babel-api.mainnet.iotex.io"
# 2) Protocol fees (DefiLlama public API — note total24h prints None: the iotex adapter has no 24h window):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/summary/fees/iotex" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total1y', d.get('total1y')); print('totalAllTime', d.get('totalAllTime')); print('total24h', d.get('total24h'), ('<- None: the iotex adapter publishes no 24h window'))"
# 2b) Chain DEX volume (DefiLlama overview/dexs):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/overview/dexs/iotex" | python3 -c "import json,sys; d=json.load(sys.stdin); print('total24h', d.get('total24h')); print('total30d', d.get('total30d'))"
# 2c) Chain TVL (DefiLlama v2/chains):
curl -s -H "User-Agent: kairos-check" "https://api.llama.fi/v2/chains" | python3 -c "import json,sys; print([c for c in json.load(sys.stdin) if c.get('name')=='IoTeX'][:1])"
# 2d) Stablecoins on IoTeX (stablecoins.llama.fi):
curl -s -H "User-Agent: kairos-check" "https://stablecoins.llama.fi/stablecoinchains" | python3 -c "import json,sys; print([c for c in json.load(sys.stdin) if c.get('name')=='IoTeX'][:1])"
# 3) Market reference (CoinGecko public API — the coingecko.com browser
#    coin page 403s plain curl, so the programmatic endpoint is given):
# CoinGecko public markets API (the endpoint family our collector
# reads for the price/supply/cap rows) — the coingecko.com browser
# coin page 403s plain curl, so the programmatic endpoint is given
# (id: iotex):
curl -s "https://api.coingecko.com/api/v3/coins/markets?vs_currency=usd&ids=iotex" | python3 -m json.tool
# 3b) Human-view check of the verify_url target (the browser coin page 403s plain curl — that is the documented 403, the programmatic command above is the verification path):
curl -s -o /dev/null -w "%{http_code}\n" "https://www.coingecko.com/en/coins/iotex"
# 4) Token counters, ERC-20 contract on eth.blockscout:
curl -s -H "User-Agent: kairos-check" "https://eth.blockscout.com/api/v2/tokens/0x6fb3e0a217407efff7ca062d46c26e5d60a14d69" | python3 -m json.tool | head -20
# 5) Dev velocity, repo-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/repos/iotexproject/iotex-core" | python3 -m json.tool | head -20
# 5b) Dev velocity, org-level (GitHub public API):
curl -s -H "User-Agent: kairos-check" "https://api.github.com/orgs/iotexproject" | python3 -c "import json,sys; print('public_repos', json.load(sys.stdin).get('public_repos'))"
# 6) This estate's public API row for IOTX:
curl -s "https://kairossignal.com/v1/network/IOTX" | python3 -m json.tool | head -60

Method & honesty notes. All counts are queries against the live ledger at generation time, not restamped copy — this page is regenerated by gen_deep_dive_iotx.py and the hourly claim_drift_check.py run grades its claims against the live API like every other published surface. Comparability grades come from the served canonical-metric system via its own resolver: total_supply maps to token_supply_total and block_height to chain_height (both question-verified). The remaining series are IOTX-native market/telemetry metrics with no cross-network concept; grading them would be fabrication, so they are labelled "iotx-native (unmapped)". The DefiLlama iotex fees adapter publishes only total1y and totalAllTime — its 24h/30-day keys read None at the origin and there is no revenue adapter, so those windows are absent from this page by upstream shape, not by omission (probe-verified this run), and the fee rows start 2026-08-23 in our archive — shown from first held row, never back-filled. The chain financials (DEX volume, chain TVL, stablecoins) are chain-level aggregates from three separate DefiLlama endpoints, each with its own verify_url, never merged with the protocol-fee slice or with each other. The CoinGecko circulating and total supply rows are different quantities (circulating vs total) and are never netted; the ERC-20 contract's totalSupply (blockscout) is a third, chain-side measurement of the bridged token contract, shown side by side and never reconciled into one number. The Babel RPC series (block height, gas price) are the estate's own first-party reads of the network's public endpoint; the collector's totalSupply series has written no rows as of generation, so none is shown — absence, not zero. GitHub rows mix repo-level and org-level counters; both are labelled with their own provenance and never combined. The estate grades are published exactly as the engines served them, unflattering parts included; revenue F and data coverage D are the engines' own outputs, not derived from any series on this page. Where a section has no data, it is absent — we do not publish zeros for gaps. Upstream probes run serially by this generator immediately before rendering: DefiLlama fees API (iotex) HTTP 200; DefiLlama dexs API (iotex) HTTP 200; DefiLlama v2/chains API HTTP 200; DefiLlama stablecoinchains API HTTP 200; CoinGecko markets API (iotex) HTTP 200; GitHub iotexproject/iotex-core HTTP 200; GitHub orgs/iotexproject HTTP 200; IoTeX Babel RPC (eth_blockNumber POST) HTTP 200; estate /v1/network/IOTX HTTP 200.