Skip to content

Data & methodology

Where every number on Equivance comes from, how listings are chosen, and what the data cannot tell you.

Token verification

The registry lists 388 tokens from 6 issuers on 4 chains, last verified Oct 16, 2026. A token is listed only when both conditions hold:

  • Published address. The exact contract or mint address appears in the issuer’s own documentation, API, or official token list. Addresses found only through search APIs or third-party aggregators are not listed.
  • Real liquidity. DEX Screener reports at least $1,000 of liquidity in pools where that exact token is the base asset, on the same chain.

Identity is always the pair (chain, address). Tokens that share a ticker but sit at a different address are not the listed asset. Different issuers’ tokens for the same stock share a canonical key so they can be compared, but they remain separate listings with separate prices, liquidity, and rights.

In-app buying is enabled for a token only after a real CrossFund Protocol quote was returned for it at verification time and liquidity met the threshold. Each purchase still requires a fresh live quote.

Data sources

  • Jupiter (Solana): token-level USD price, liquidity, 5-minute to 24-hour volume and swap counts, holder counts, 24-hour candles, and wallet holdings. Requested directly from your browser.
  • DEX Screener (all chains): every pool for a token, with pool price, liquidity, volume, and swaps. Used for pool detail everywhere and for token-level figures on EVM chains.
  • Uniswap (EVM): 24-hour token price history and pool pages, requested directly from your browser.
  • GeckoTerminal: the interactive chart on asset pages (embedded), recent swaps, and EVM price history when Uniswap and Codex do not return a series.
  • Codex (optional, EVM): token-level 24-hour price history, averaged by Codex across a token’s top pools. Used when the operator configures a server-side key; the key is never sent to the browser.
  • CrossFund Protocol: swap quotes and transaction routes for purchases.
  • Public RPC nodes: EVM wallet balances, transaction submission, and confirmation; Solana fee estimates and confirmation.

Prices and aggregation

A token usually trades in several pools. Equivance distinguishes token-level figures, which describe all eligible markets for the token together, from pool-level figures, which describe one pool.

Eligible pools

A pool is eligible when it is on the token’s chain and the token is the pool’s base asset (so the reported price is the token’s price, not its inverse). Pools are deduplicated by address before anything is added up.

Solana

Token-level price, liquidity, volume, and swap counts are Jupiter’s own aggregates for the mint. Jupiter also reports a reference price for the underlying stock; Equivance shows it separately and never uses it as the token’s price.

EVM chains

Liquidity, 24-hour volume, and 24-hour swaps are summed across deduplicated eligible pools from DEX Screener. Price and price changes come from the deepest eligible pool — the one with the most USD liquidity — because a liquidity-weighted average across shallow pools is easily distorted by stale or thin markets.

If no eligible pool exists, the token is shown with no price. No other token or pool is ever substituted.

Charts and history

  • The asset-page chart is GeckoTerminal’s interactive embed for the deepest eligible pool. Ranges, candle sizes, and indicators are handled inside the embed.
  • The 24-hour trend in listings uses 15-minute closes: Jupiter candles on Solana. On EVM chains, Uniswap token history is used first, then Codex when a key is configured, otherwise pool candles.
  • GeckoTerminal’s public API allows roughly 10 requests per minute, so Equivance queues those requests (at most 8 per minute per browser) and loads trends only for rows on screen.
  • When no history is available, the interface says so instead of drawing a line.

Freshness and caching

Market data is fetched from the providers when you open or refresh a view. Reusable responses are stored in your browser’s IndexedDB with the time they were fetched; there is no Equivance server-side market-data cache. Identical requests made at the same time are combined into one.

  • Market data is reused for 2 min, labelled stale after 10 min, and discarded after 168 h.
  • 24-hour trends are reused for 5 min; recent swaps for 1 min.
  • Each panel states whether its data was fetched in this session or restored from your device, and how old it is. The refresh control always fetches from the provider.
  • Wallet balances are never cached; they are read live and kept in memory only.

Quotes and buying

  • Payment tokens appear only when CrossFund Protocol lists them for the asset’s chain; every amount is confirmed by a live quote.
  • Quotes show expected output, minimum received, slippage tolerance, route, and fees as reported. Quotes older than 30 seconds must be refreshed before signing.
  • CrossFund Protocol does not report price impact. Equivance shows the route’s effective price against the latest market price, labelled “Price vs. market”; it includes route fees.
  • Requests to CrossFund Protocol pass through a same-origin relay because CrossFund Protocol does not accept browser requests directly. The relay forwards three operations unchanged and caches nothing.
  • A purchase is shown as confirmed only after the network reports the transaction confirmed (Solana) or a successful receipt (EVM). Otherwise it is shown as submitted, declined, or failed. Cross-chain purchases are not offered.

Wallet holdings

  • Solana holdings come from Jupiter’s holdings API for the connected address, as reported by Jupiter.
  • EVM holdings are read with one multicall per chain for listed tokens only, through public RPC nodes.
  • Only tokens in the registry are shown. If a balance cannot be read, it is reported as unavailable rather than zero.

Known limitations

  • Public APIs can rate-limit or block requests. Affected panels show an error and a retry option; nothing is estimated in their place.
  • DEX Screener returns at most about 30 pools per token, so token-level EVM liquidity can be understated for very widely traded tokens.
  • Liquidity counts only pools where the token is the base asset; pools that quote other tokens in this token are not included.
  • On-chain prices can diverge from the underlying security’s exchange price, especially outside market hours.
  • Some issuers’ legal documentation could not be fully verified; those statements are marked “Not confirmed”.