About RugSnap

How a token gets snapped

A scheduled job runs every few minutes. It reads the watchlist, calls the public DexScreener endpoint for each address, picks the deepest pool as the reference, and writes one snapshot row: market cap, price, liquidity, 24h volume, 24h change, transaction count. Nothing is smoothed, back-filled or estimated. If a call fails, the run is logged as a failure and no row is written for that token.

This is a polling cycle, not a stream. The gap between the timestamp on a card and the current market can be several minutes, which is why every card carries its own "last snapped" time.

How stamps are decided

• · FLAGGED — liquidity under $30,000, or 24h volume above 25x liquidity, or no tradeable pool found.
• · VERIFIED — pool older than 90 days, liquidity above $250,000, 24h move inside ±40%.
• · WATCHING — everything else.

The rule that produced a stamp is printed on the token's own page. The desk can override a stamp by hand for an edge case, and when that happens the override and its note are shown publicly. A stamp is a description of measurable pool conditions. It is not a recommendation of any kind.

How case files get chosen

Case files cover full projects, not just memecoins. A project earns a file when there is enough public material to check: documentation, on-chain activity, named or traceable contributors, a token distribution that can be read. Each file states what was verified, what could not be verified, and where the writeup lands.

No case file is generated. There is no model writing them and no model editing them. Sponsored placements and affiliate links, where they exist, are labelled on the page itself.