Screener filters for a focused crypto pair shortlist

Screener filters narrow crypto pairs into a useful shortlist when every condition matches the comparison you want to make. Set the market scope, choose a measurement window, and separate eligibility conditions from ranking. Volume, transaction activity, liquidity, and pair age answer different questions, so combining them needs a clear purpose. Keep the surviving pair identifiers alongside their measurements. That makes the shortlist suitable for closer inspection without confusing a high position with a reason to trade.

A useful pair shortlist applies consistent filters and measurement windows, so differences between rows reflect the markets being compared.

Network, quote asset, and pair scope

A comparable group starts with the network and pair identity, because matching symbols do not establish that rows describe the same market. The quote asset is the asset in which a pair expresses its price. Different quote assets can change the meaning of a price comparison. For pool-based markets, keep the pool or pair address attached to each row. A token can appear through several pools, each with its own activity.


Filter conditions before ranking

A filter decides whether a pair qualifies, while sorting decides where a qualifying pair appears in the list. Keep those jobs separate. A volume floor excludes pairs below the chosen amount; descending volume places larger qualifying values first. Sorting alone does not establish a minimum.

Choose conditions that answer a specific screening question. A liquidity condition concerns available pool assets. A transaction condition concerns recorded trading activity. Price change describes movement over a period. Adding all available fields can obscure the reason a pair belongs on the shortlist, especially when several conditions describe closely related activity.

When conditions must all hold, each additional condition narrows the eligible set or leaves it unchanged. Alternative conditions produce a different result: a pair might qualify through either one. Check how the available filter controls combine conditions before interpreting a broad or unexpectedly narrow result.

Matching the measurement window

Volume comparisons need the same measurement period and denomination, or their apparent differences can come from the settings themselves. Volume measures the amount traded during a period. Transaction count measures recorded trades. Neither number explains the other without more detail about trade sizes.

Matching the measurement window: Volume comparisons need the same measurement period and denomination, or their apparent differences can come from the settings themselves.; Volume measures the amount traded during a period. Transaction count measures recorded trades. Neither number explains the other without more detail about trade sizes.

Open full-size image

A short window emphasizes recent activity, while a longer window includes activity that began earlier. A high longer-window total can coexist with little recent trading. A recent burst can also look small beside activity accumulated over a longer interval. Both readings can be correct.

Keep each field’s period visible in the comparison. Changing a chart interval does not establish that every screening field uses that interval. Likewise, a rolling window and a completed calendar period have different boundaries. If the available field does not support the period you need, it cannot directly answer that screening question.


Why does a filtered list return no pairs?

After the data loads successfully, a filtered list returns no pairs when no available row satisfies the active conditions, including any requirements for populated data. This can reflect the market, conflicting settings, or a restricted starting set. An empty list alone does not distinguish those causes.

Review the conditions together. A minimum above the corresponding maximum makes a range impossible. A network restriction can exclude the intended market before activity filters apply. Requiring substantial trading history can also conflict with a search centered on recently created pairs. These are differences in the query, not evidence that the market has disappeared.

Missing data needs separate treatment from a recorded zero. An absent valuation does not establish a worthless token, and an unavailable activity field does not establish inactivity. Where the required measurement is missing, the pair remains unassessed against that condition. Relaxing the condition changes the question that the shortlist answers.

Liquidity and activity as separate filters

A liquidity floor and a volume floor describe different properties, even when both appear as monetary values in the same row. Liquidity concerns assets available in a pool. Volume accumulates trading over a period. Repeated trading can generate substantial volume without a matching increase in pool assets.

In an automated market maker pool, a trade’s price impact depends on its size relative to the liquidity available for that trade. A displayed liquidity total therefore cannot establish an acceptable execution outcome for every trade size. For this shortlist, liquidity serves as a screening condition; a later quote addresses the intended transaction.

Transaction counts add another perspective on activity. Many small trades and fewer large trades can produce similar volume totals. Repeated transactions can also come from the same participants. Use each measure for the question it answers, without treating a count as proof of independent demand.


Pair age and valuation boundaries

Pair age describes the history of a particular market, so it should not stand in for the age of its underlying token. A new pool can contain an established token. An older pool can have a quiet recent period. Age filters select a market-history range; activity filters describe trading within that history.

Valuation filters require equally precise labels. Market capitalization generally uses circulating supply, while fully diluted valuation uses a broader supply basis. The supply definition matters. Interchanging these fields can move a pair across a chosen boundary even when its displayed token price stays the same.

Use a valuation field only for the comparison that its calculation supports. A lower token price does not necessarily mean a smaller valuation because supply also enters the calculation. When the necessary supply estimate or valuation is unavailable, leave that comparison unresolved rather than assigning a substitute value.

A shared volume test for two candidate pairs

In this hypothetical example, two candidate pairs share a selected network, quote asset, and measurement window. Both satisfy the other screening conditions. Their volume readings and the chosen volume floor are hypothetical inputs.

The first pair’s measured volume exceeds that floor. The second pair’s volume falls below it. Both measurements use the same denomination, so the comparison does not mix token quantities with monetary values.

Apply the same minimum-volume condition to both candidates. The first pair qualifies for the shortlist, and the second does not. Their price changes do not alter this particular decision.

Confirm the result by matching the surviving row’s pair address and period to its displayed volume. The shortlist now contains only the first candidate from this comparison.

The durable rule is that measured volume must meet the selected floor. The volume reading changes with market activity, and the floor remains a chosen setting. Neither value becomes a universal screening threshold.

Reading a sorted shortlist

Descending volume ranks qualifying pairs by recorded trading volume for the selected period. Trending rankings incorporate signals beyond trading volume. A trending position therefore answers a different question from a volume rank. Keep the sort field attached to the shortlist so its order remains interpretable. A prominent row does not necessarily have the largest value in another column, and equal displayed values can conceal differences that rounding hides.

Why do matching pairs change after a refresh?

Matching pairs change after a refresh because market measurements can cross filter boundaries while the selected conditions remain unchanged. New trades enter an activity window. Older trades leave a rolling window. Prices and pool balances can also change.

A pair close to a cutoff can move in and out of the list without a settings error. Sorting can change its position even while it continues to qualify. These changes describe different events: losing eligibility removes a row, while a changed rank moves it among the survivors.

Record the observation time when a particular shortlist matters. A later result answers the same query using later data. It need not reproduce the earlier membership or order.


Choosing which pair deserves closer inspection

Choose a surviving pair for inspection based on the reason you shortlisted it. A pair shortlisted for recent activity needs examination of that activity; a pair selected for a longer history needs a different comparison.

A narrow result does not automatically mean a useful result. Excessive conditions can exclude relevant markets, while weak conditions leave too much unrelated activity. Judge the screen by whether each surviving row supports the intended comparison, not by how impressive its figures look.

The shortlist identifies markets that meet stated conditions at an observed time. Choosing a transaction requires additional information about the particular token, pool, and executable quote.

Questions and answers about Screener

Can I filter public pair data without connecting a wallet?

Yes, you can read and filter public pair data without connecting a wallet or granting permission to spend wallet assets. Reading pair measurements and choosing screening conditions are data operations. A wallet signature or token approval concerns a separate action, so it is not evidence that a filter has run or that a shortlist is valid.

Does adding a column also create a filter?

Displaying a column and applying a filter are separate settings. A column exposes a measurement for comparison; a filter requires that measurement to satisfy a condition. Showing transaction counts, for instance, does not establish a transaction minimum. Look at the active conditions when assessing why a row qualifies.

How can I keep several pools from crowding out other tokens?

Group qualifying rows by network and token address when the intended shortlist is about tokens rather than individual pools. Keep the pool records within each group so their measurements remain distinct. Choosing one representative pool requires a consistent criterion; adding together unrelated measurements can change the comparison.

Are saved screening settings the same as saved results?

Saved screening settings describe a query, while saved results preserve the rows observed when that query ran. If a tool supports saving either one, establish which it retains. Reusing stored conditions can produce different pairs because the underlying market data changes.

Which details matter when transferring filters between tools?

Match field definitions, units, time boundaries, and market coverage before treating filters in different tools as equivalent. Identical labels can conceal different calculations or eligible markets. Missing-value handling also matters: a tool that excludes incomplete rows can produce a narrower list under otherwise similar conditions.

What does a buy-to-sell transaction ratio leave out?

A ratio based on transaction counts leaves out the amounts traded in those transactions. More buys than sells does not establish greater buy volume, and repeated trades do not establish more distinct participants. If the sell count is zero, the ordinary division-based ratio has no finite value.

Could rounded values explain a pair that appears outside my filter?

Rounding can make a displayed value appear equal to a cutoff even when its underlying value differs. Whether this explains a particular row depends on the precision used by the filter. Check available precision and whether the condition includes its boundary before concluding that the filter failed.

Updated on