Skip to content

Methodology and sources

Where every number comes from, and how far to trust it.

Data sources

SourceUsed for
CoinGeckoPrices, market caps, exchange and treasury data
BinanceFunding rates, open interest, liquidations
BybitDerivatives cross-check
OKXDerivatives cross-check
DefiLlamaTVL, stablecoins, staking yields
Alternative.meFear & Greed Index
mempool.spaceBitcoin fee estimates
ethereum-lists / chainid.networkEVM network parameters

Market data provided by CoinGecko. All sources are used through their public APIs within the published free-tier limits.

How data reaches the page

  1. At build time. Every page is generated with real values already in the HTML, so it has content before any script runs and works with JavaScript disabled.
  2. In your browser. Every data page then re-fetches from the same public APIs directly. No proxy server sits in between, which means nothing here can silently alter a number, and the figures stay current between site updates.
  3. With a second source. Market prices try CoinGecko first and fall back to Coinpaprika. CoinGecko's public API rate-limits by IP address and its rate-limit responses carry no CORS headers, so a browser reports the limit as a connection failure — the fallback makes that invisible to you.
  4. On failure. If a source is unreachable the page keeps the build-time values and the status indicator turns amber. A red indicator means live updating failed entirely. Nothing is ever shown as current when it is not.

The one page that does not update live

Staking yields come from a DefiLlama endpoint that returns roughly 11 MB covering every pool it tracks. Downloading that to render one table would be unreasonable, so that page shows a build-time snapshot with its date on it. Pool APYs move on a daily cycle, which makes a snapshot defensible there in a way it would not be for prices.

Figures maintained by hand

Three datasets have no free API and are maintained manually. Each shows its own verification date on the page.

Exchange fees, KYC and country availabilityChecked 2026-09-14
Network RPC endpoints and chain IDsChecked 2026-09-14
Testnet faucet listChecked 2026-09-14

Token contract addresses

These are not typed from memory or copied from other sites. Every address is verified on-chain by calling symbol() and decimals() on the contract through that network's public node; any address whose on-chain symbol does not match is rejected and never published. The current set was verified on 2026-09-14.

Calculations

Known limitations