New Tokens Adjusted for Holder Concentration

Choose one finalized block or slot at a standardized token age, such as 7 complete days after first permissionless trading. Retrieve every balance and total supply at that state. The raw denominator is minted supply less provably burned supply, where burn means an irrecoverable address or a chain-native burn operation under a stated rule. The adjusted denominator is raw supply minus balances held by excluded infrastructure categories. Report both denominators in native units and the reconciliation difference.

Circulating supply is not whatever an aggregator currently displays. Team vesting, treasury, bridge custody, and exchange omnibus balances may be economically relevant even when they do not circulate freely. Therefore provide at least two views: ownership-inclusive concentration, excluding only provable burns and technical pool custody, and market-float concentration, additionally excluding disclosed locked allocations. Never switch denominators between tokens without labeling the view.

Classify addresses using deterministic onchain evidence first: verified AMM pool contracts, token vault derivations, bridge escrow contracts, burn addresses, vesting contracts, staking vaults, and protocol-owned treasuries. Provider labels from Birdeye, CoinGecko, explorers, or security APIs can supplement this evidence but need source, retrieval time, and confidence. Exchange and custodian addresses should remain included in the ownership-inclusive view because one omnibus balance may represent many users, but excluding it would also hide a real custody dependency.

Compute top-1, top-5, top-10, and top-20 shares over eligible addresses, plus a Herfindahl-Hirschman style sum of squared holder shares. Publish the address count above a minimum economically meaningful balance threshold, with that threshold stated in token units or timestamped USD value. Sorting must occur after exclusions and denominator selection. Contract-associated wallets controlled by the same entity should be grouped only when attribution evidence is strong, with grouped and ungrouped results both retained.

For liquidity pools, exclude the pool vault from holder ownership metrics but separately report the share of supply deposited into eligible liquidity. A pool address represents pooled inventory, not a conventional owner, yet its liquidity-provider tokens may themselves be concentrated. If LP ownership is available, report it as a separate control dimension rather than assigning underlying tokens directly to LP holders without modeling their claims.

Exclude zero balances, provable burns, duplicate account representations, and technical accounts that cannot independently transfer the balance. Do not automatically exclude creator, deployer, treasury, vesting, market-maker, exchange, or bridge addresses. Their balances can affect control or market availability and belong in one or more clearly named views. Reflection, rebasing, elastic supply, confidential balances, and cross-chain canonical supply require token-specific handling and may make comparable scoring unavailable.

Sybil splitting makes holder counts easy to manipulate, while omnibus custody can make concentration look larger than beneficial ownership. Address labels can be stale or wrong. Smart contracts can delegate control, and multisignature ownership can change without a token transfer. Publish the share assigned to known infrastructure, known entities, unlabeled contracts, and unknown externally owned accounts. A wide unknown share means the adjusted result has wider uncertainty, not that unknown holders are independent.

For every token record the first trading block or slot, target age, snapshot block or slot, chain timestamp, balance index completion time, total-supply query time, label retrieval times, provider retrieval times, and analysis version. All balances and supply must refer to the same chain state. If archival state is unavailable and index completion crosses blocks, mark the snapshot asynchronous and quantify the observed block range.

Coinatio's live table supplies current examples, but live holder distributions can change with every transfer and label update. GoPlus and Honeypot.is can contribute contract and holder annotations on supported networks, while MetaMask security documentation explains user-facing transaction and token safety concepts. None supplies complete beneficial ownership. The output should be read as concentration among observed onchain accounts under declared adjustments, not as a definitive map of people or coordinated control.