Screener liquidity filters help narrow crypto pair shortlists

Screener liquidity filters help narrow crypto pair shortlists by comparing pool funding alongside trading volume. A useful shortlist separates recent activity from the liquidity available to absorb a proposed trade. Start with comparable pairs, keep the volume window consistent and examine how each pool distributes its liquidity. A large displayed balance does not establish how much can trade near the quoted price. Concentrated liquidity makes that distinction especially relevant because only positions covering the current price provide active liquidity. The comparison becomes more useful when it connects the displayed figures to a quote for the intended trade size.

Last updated:

Choose liquidity or activity as the first filter

Liquidity-first screening prioritizes pool funding, while volume-first screening prioritizes recent trading activity; both approaches need the other measure for context.

Start with pool funding

A minimum liquidity filter excludes pairs below a chosen displayed balance, where that control exists. Its purpose is to reduce the candidate list before examining execution conditions. The threshold reflects the intended comparison rather than a universal boundary between usable and unusable markets. Trade size, pool design and liquidity distribution determine whether a surviving pair deserves closer examination. Sorting by liquidity alone cannot account for those differences.

Start with recent activity

A volume filter identifies pairs with trading activity over the selected period. It can surface an active market whose remaining liquidity is small. Conversely, a well-funded pool may show little recent trading. Keeping both columns visible makes these differences easier to interpret. Neither ordering establishes future demand or an acceptable execution price. They produce different research lists because one starts with a pool balance and the other starts with accumulated trades.

Keep the comparison tied to the same pair

Comparable liquidity figures require an exact pool identity and a clear understanding of the assets that its balance includes.

Preserve the pool identity

A pair record can identify the chain, pool address, base token and quote token separately. Those fields prevent a token-level shortlist from merging distinct markets. The same token can appear in several pools, each with its own reserves. Record the pool identity alongside the liquidity figure so later comparisons concern the same market. A familiar ticker does not resolve which pool supplied the displayed balance.

Keep the valuation basis consistent

A value expressed in a common currency makes differently denominated pools easier to compare. It also introduces sensitivity to the prices used in that conversion. Balances measured in each pool token's units and their converted value answer different questions: one describes quantities, while the other values those quantities. A rising converted balance therefore does not, by itself, establish that someone deposited additional tokens. The quote asset also affects what the pool can actually pay out.

Read volume relative to the liquidity snapshot

Volume divided by liquidity describes reported activity relative to a pool balance, provided both values use the same currency basis.

Read volume relative to the liquidity snapshot: Volume divided by liquidity describes reported activity relative to a pool balance, provided both values use the same currency basis.

View full-size image

Write the relationship as V / L, where V means volume during the selected period and L means liquidity at the observation time. The numerator covers an interval; the denominator describes a snapshot. This mismatch matters when liquidity changes during the interval. A high ratio can accompany frequent trading, declining liquidity or both. It does not reveal unique participation, prove organic demand or show the price impact of a future trade. Compare matching windows and retain the observation time when evaluating several pairs.

Look beneath total liquidity at active depth

In a concentrated liquidity pool, a position supplies active liquidity only while the pool price lies within its selected range. Consequently, total deposited value and liquidity near the current price describe different properties. A narrowly concentrated position can support substantial depth nearby, then stop contributing after the price crosses its boundary. A larger total balance spread differently may produce another execution profile. A quote for the intended amount helps assess this distinction, provided its route corresponds to the pool under review. Quotes that combine several pools describe the combined route. They cannot establish how the shortlisted pool would handle the entire amount by itself.

Retain a candidate only while its quote matches the comparison

In this hypothetical example, a candidate passes a chosen liquidity filter and a matching-window volume filter. The intended trade amount, acceptable price-impact ceiling and resulting quote are assumed inputs. The available quoting configuration supports a quote restricted to the candidate pool.

Request that quote for the intended amount and direction. Assume its estimated price impact falls below the chosen ceiling. The candidate remains on the shortlist for further evaluation because it satisfies both the initial filters and the execution condition.

Independently compare the quote's chain, pool address and token addresses with the recorded candidate. Matching identifiers confirm that the quote concerns the shortlisted market. Retain the quoted amount and observation time with that record. This completes the shortlist check without submitting a swap.

If the quoting configuration instead combines several pools, the same result cannot confirm the candidate's individual depth. Mark its execution check as unresolved until a pool-specific quote is available. A later liquidity change also invalidates the earlier quote as evidence of present execution conditions.

Distinguish changing balances from changing execution conditions

A shortlist needs renewed evaluation when its underlying liquidity changes, even if the pair remains above the initial filter threshold.

Price impact depends on trade size relative to the liquidity available along the trade's price path. Liquidity withdrawals can reduce that depth, while price movement can change which concentrated positions remain active. A converted liquidity value may also change because token prices move. These events require different interpretations, so retain the pool identity and comparison basis when revisiting a candidate.

Sorting by the largest liquidity balance produces a simple ranking. Comparing matched pairs and amount-specific quotes produces a shortlist tied to the trade being considered.

Useful questions about Screener

Does locked liquidity establish that a shortlisted pair has enough depth?

Locked liquidity does not establish adequate depth for a particular trade. A lock concerns withdrawal restrictions on the covered liquidity position, subject to its terms. Execution still depends on the amount, direction and liquidity available at relevant prices. In a concentrated pool, locking a position does not make that position active outside its price range.

Why can a liquidity filter remove every candidate?

A liquidity filter can leave no candidates when none of the covered pairs meets the selected conditions. Other active filters may narrow the intersection further. Check the selected market scope, measurement units and combined conditions before interpreting an empty list as evidence that no liquid market exists.

Should market capitalization determine the minimum liquidity filter?

Market capitalization alone cannot determine an appropriate minimum liquidity filter. It values token supply using a price, while pool liquidity concerns assets available within a particular market. A liquidity-to-market-cap ratio describes their relative scale, but it does not calculate the execution price for a proposed amount.

Can separate pool balances be added when comparing a token's liquidity?

Balances from distinct pools can describe aggregate liquidity only when their valuation basis is consistent and duplicate records are excluded. That aggregate does not establish the depth available through one pool. Accessing liquidity across several pools also requires a route that can actually use those pools for the intended exchange.

Will increasing slippage tolerance compensate for a shallow pool?

Increasing slippage tolerance does not add liquidity or reduce the price impact caused by a trade. For an exact-input swap, it lowers the minimum output you accept relative to the quote. For an exact-output swap, it raises the maximum input you permit. A shallow pool retains its execution constraints even when the transaction settings permit a worse outcome.

Is the same liquidity figure equally informative for buying and selling?

A single liquidity figure does not establish equivalent execution conditions in both directions. Buying and selling consume different reserves and move the pool price in opposite directions. Concentrated liquidity can also differ across the price ranges that each direction crosses. Direction-specific quotes provide a more relevant comparison.