DexBrief

Methodology

How symbols are selected, scored, and refreshed across DexBrief.

How DexBrief chooses tokens

  1. Collect candidates from public market feeds, DEX discovery routes, trending lists, and exchange or social signals.
  2. Apply market gates first: volume, market cap, liquidity, transaction activity, source count, and recency. A huge 24h percentage move by itself is not enough.
  3. Use contract and pair addresses to separate real high-activity markets from duplicate names, copycats, and low-liquidity lookalikes.
  4. Check search results for authority saturation and obvious name collisions before spending generation time.
  5. Create or refresh pages gradually, then keep important live values fresh when visitors load the page.

Ranking signals

Search and trending surfaces prioritize practical legitimacy: contract match, exact ticker/name match, 24h volume, market cap, liquidity, transaction count, source breadth, and recent update time. This is why a real $40M market should outrank a tiny copycat with a bigger percentage move.

Data limitations

For small tokens, a tracked DEX pool can represent most visible liquidity. For top assets, one route is only a route, not total global liquidity. Prices and venue data can differ across sources, so DexBrief favors fresh public data and labels route context instead of pretending every exchange order book is represented.

Public sources

Sources can include DexScreener, CoinGecko, CoinPaprika, CoinLore, exchange market feeds, chain explorers, public social pages, search result checks, and project-provided resource links. Availability varies by token and chain.

Refresh policy

Important price, market-cap, volume, and route values are designed to refresh from live or short-cache data. More static fields, like basic project descriptions and resource links, refresh during page regeneration or scheduled idle updates.