Currently the trenches command only supports --launchpad-platform and --type as query-time filters. All risk-related fields (e.g. dev_team_hold_rate, suspected_insider_hold_rate, renowned_count, fresh_wallet_rate, bundler_trader_amount_rate) are only available as response fields, requiring local post-filtering.
Request: Add optional query-time filter parameters for these fields, similar to how trending supports --filter tags. For example:
--max-dev-hold <0-1> # e.g. 0.05 to exclude dev holding >5%
--max-insider-hold <0-1> # suspected insider hold rate
--min-smart-degen <n> # minimum smart degen count
--max-fresh-wallet <0-1> # fresh wallet rate ceiling
--max-bundler-rate <0-1> # bundler trader amount rate ceiling
This would significantly reduce the need for local post-filtering and make the CLI more useful for automated screening pipelines.
Current workaround: Fetch all results and filter locally, which wastes bandwidth and adds latency.
Chain: Affects sol / bsc / base equally.
Currently the
trenchescommand only supports--launchpad-platformand--typeas query-time filters. All risk-related fields (e.g.dev_team_hold_rate,suspected_insider_hold_rate,renowned_count,fresh_wallet_rate,bundler_trader_amount_rate) are only available as response fields, requiring local post-filtering.Request: Add optional query-time filter parameters for these fields, similar to how
trendingsupports--filtertags. For example:This would significantly reduce the need for local post-filtering and make the CLI more useful for automated screening pipelines.
Current workaround: Fetch all results and filter locally, which wastes bandwidth and adds latency.
Chain: Affects sol / bsc / base equally.