How to Interpret Top-10 Holder Concentration Without Misreading LP and Burn Addresses

The simplest calculation sums balances of the ten largest on-chain addresses and divides by total token supply. Some dashboards exclude burn addresses, liquidity pools, contracts, or team wallets. Others divide by a third party's circulating-supply estimate. These methods answer different questions and should not share one unlabeled percentage.

Publish the snapshot block or Solana slot, supply source, included addresses, and denominator. Show the raw top-10 share first. If you calculate an adjusted share, define every exclusion and recompute both numerator and denominator consistently. Removing a burn balance from the numerator while leaving it in the denominator understates the remaining holders' share.

An automated market maker pool holds token inventory used for swaps. Its balance can place the pool among the largest holders, but it is not equivalent to one wallet freely holding the same amount. Economic control over that inventory depends on pool rules and on who controls the associated LP tokens or concentrated-liquidity positions.

Verify a pool through the exchange factory or program, its paired asset, and reserve state. Do not rely solely on an explorer label. Then inspect LP token supply, position ownership, locks, burns, timelocks, and migrator or administrative permissions. Excluding the pool from holder concentration can clarify wallet distribution, but the pool and liquidity control should still appear in a separate section.

On EVM chains, common dead addresses include the zero address and widely used `dead` destinations. Tokens sent there are generally treated as removed from circulation because no ordinary private key controls them. Yet a contract may implement unusual accounting, blacklisting, rebasing, or minting behavior, so the address label alone is not a proof about total future supply.

On Solana, burning through the token program reduces both the token account balance and mint supply. Sending tokens to an arbitrary wallet that nobody claims to control is not the same protocol action. Confirm a burn instruction and current mint supply rather than inferring a burn from a memorable address or project statement.

Bridge vaults lock canonical tokens while representations circulate on another network. Exchange and custodian wallets can aggregate balances for many customers. Treasuries, vesting contracts, staking contracts, distributors, and governance timelocks may represent known allocations with different release conditions. Contract source, transaction flows, official disclosures, and verified labels can support classification, but labels can be stale or incorrect.

Also consider address clustering. Related funding, synchronized transfers, shared deposit patterns, or a common controller contract can suggest links, but heuristics should be labeled as such. Conversely, one exchange address does not mean the exchange owns every token economically. Separate address-level facts from claims about beneficial ownership.

• Pool: verify factory or program and inspect liquidity-position control.
• Burn: confirm protocol behavior and denominator treatment.
• Bridge or custodian: identify liabilities or backing represented by the balance.
• Treasury or vesting: inspect controllers, schedules, and upgradeability.

Snapshots miss rapid transfers and do not reveal private agreements, compromised keys, derivatives, lending collateral, or beneficial owners. Account models also differ. On Solana, one owner can control several token accounts, so rankings should aggregate by owner where the analytical goal is wallet control. Program-owned accounts require additional classification rather than naive aggregation.

Circulating-supply figures from data providers follow published methodologies and can differ from on-chain total supply. Concentration says nothing by itself about execution liquidity, authority permissions, contract behavior, or future distribution. Present it as a reproducible distribution measure with explicit assumptions, not as a standalone conclusion.