Access
The response states when its snapshot was generated. Read that timestamp rather than treating the board as a live feed.
Filtering and flags
Pools with very little liquidity can show large percentage moves and volume. Otto handles them in two stages:- Tokens below the hard liquidity floor, or above the hard volume-to-liquidity ceiling, are excluded.
- Thin or unusual rows that remain are shown with flags.
screenFloors. They can change, so the response is the source for the exact values used on that read.
Read the raw
volToLiqRatio and liquidity alongside the percentage move. High turnover can be organic or manufactured; the ratio alone does not decide which.
Social-signal limits
A symbol can collide with a major asset, a tokenized-equity ticker, or a one-character cashtag. In those cases the board setskolSymbolAmbiguous: true and withholds token-level attribution rather than counting the wrong conversation.
Social rows pass a deterministic screen for wallet solicitations, giveaway and airdrop lures, whitelist or mint promotions, direct-message schemes, and participation farms. Rows that match are removed before ranking, and coverage reports how many rows the screen and recency window removed.
If the social source is unavailable, the board can return a volume-ranked screened view without mention counts or quotes. If narrative sentiment is unavailable, the summary remains empty. Check coverage before interpreting a sparse block.
Sources are GeckoTerminal for pools and market data, CoinGecko for the chain registry, and Otto’s social-data provider for trusted-voice rows. Generated sentiment, where present, is secondary to the returned market and coverage fields.