Three flags, one exemption, one rulebook
Method
Backed uses only fields from the CoinMarketCap Pro API, with no tunable weights. Every holding lands in exactly one bucket: flagged, exempt, or not flagged. The flags never overlap: a holding is unverified, thin, or above circulating supply, in that order. Not flagged means these checks found nothing. It does not mean the value is verified.
- 1
Unverified supply
circulating_supply is 0, or the token is not returned by quotes/latest
CoinMarketCap withholds a circulating supply and market cap when it has not verified a token's supply. The reserve total still counts these tokens at full price. Backed flags the whole holding as an evidence gap. It does not say the token is worthless.
- 2
Above circulating supply
balance held > circulating_supply
The disclosed holding is larger than CoinMarketCap's circulating-supply figure. The two datasets can differ in scope or timing: locked or treasury supply, other chains, or delayed balances can all produce this. Backed flags only the part above circulating supply, as a discrepancy. Ownership cannot be inferred from it.
- 3
Thin market
num_market_pairs <= 2; a missing count is unknown, not thin
The reserve value is balance times price. When a token trades on two pairs or fewer, that price comes from a very small market. The pair count is a proxy, not a depth measurement: market depth is not available on the Basic plan.
- 4
Exempt, not evaluated
tags stablecoin, wrapped-tokens, liquid-staking-derivatives, rehypothecated-crypto
Stablecoins and wrapped or staked tokens get their value from redemption, which market data cannot test, and their CoinMarketCap supply is often counted on one chain only. They skip checks 2 and 3 and are shown as exempt, never as passing. They are still flagged by check 1.
Open interest
open_interest_usd divided by reported reserves. Open interest is not a liability and wallet disclosures cover different things, so the ratio is shown beside the result, never subtracted. CoinMarketCap reports open interest of exactly zero for some exchanges with billions in derivatives volume; Backed treats zero as no data.
What the source covers
- CoinMarketCap lists only wallets holding at least $100,000, so smaller wallets are not counted.
- Balances may be delayed, and reserve rows carry no timestamp, so balances and prices are not from one moment.
- Exchanges supply the wallet data. CoinMarketCap states that it does not verify it.
- 18 exchanges listed as reporting return no wallets and are not scored.
- Duplicate rows are dropped. 7 wallet-token pairs came back with different balances or prices; the larger balance, then the higher price, is kept and counted.
What this is not
- Not a solvency or backing test. The reserve data has no liabilities.
- Not an ownership ledger. A supply discrepancy does not say whose tokens they are.
- Not a rating. Backed does not rank exchanges as safe or unsafe.
- Not an audit. Wallets and balances are taken from CoinMarketCap as returned, not checked on-chain.
Pipeline and checks on it
/v1/exchange/maplists 978 active exchanges. The run stops if the list hits the page limit./v1/exchange/info, 100 exchanges per call, finds the 89 marked as publishing proof-of-reserves./v1/exchange/assetsreturns wallets for 71 of them. Any failed request stops the run, so a partial set is never published. Negative or non-finite numbers stop it too.- Exact duplicate rows are dropped. EVM addresses are matched without regard to case; other address formats are case-sensitive and kept as returned. When one wallet and token come back with two balances, the larger is kept and the conflict is counted.
/v2/cryptocurrency/quotes/latest, 100 tokens per call, adds supply, market pairs, volume and tags for every held token./v5/exchange/derivatives/listadds open interest, and/v5/derivatives/liquidations/exchange/list/latestshows which exchanges appear in CoinMarketCap's latest liquidation list. The list leaves out exchanges without an integrated feed and those with no recent liquidations, so absence is not evidence of either. Open interest reported as exactly 0 is kept in the inputs but gives no ratio.
The current snapshot ran from 2026-09-30 21:31 UTC to 2026-09-30 21:34 UTC with 111 calls and 111 credits on the free Basic plan, method checks-v6. data/inputs.json keeps every wallet row exactly as CoinMarketCap returned it, plus the supply, market, open-interest and liquidation fields the checks read; its SHA-256 is recorded in the snapshot. npm run replay rebuilds data/snapshot.json from it offline and fails unless every field matches exactly. Replay proves the figures follow from those inputs. It cannot prove the inputs are what CoinMarketCap served, or re-derive which exchanges report reserves; npm run verify, run with your own key, checks a sample against the live API.