Bundled supply: many holder addresses can still be one position
Atomic launch buys, pre-funded fresh wallets, and later dispersal can make concentrated inventory look distributed. Reconstruct acquisition, funding, transfers, and exits before using holder count as evidence of independent ownership.
The short answer
Bundled supply is token inventory acquired or distributed through coordinated transactions or wallets so one economic position appears across many addresses. The coordination may use an atomic transaction bundle, several separately landed launch buys, one buyer that disperses tokens afterward, or a common funder that prepares many wallets in advance.
A bundle is an execution mechanism, not proof of fraud or common beneficial ownership. Jito bundles can contain up to five signed transactions that execute sequentially and atomically. The signatures may belong to different wallets. Funding, preparation, transfer, consolidation, and exit evidence are still needed to support an entity claim.
Separate the acquisition and distribution patterns
- Atomic launch acquisition: several signed buys land in a defined order as one all-or-nothing bundle.
- Parallel fresh-wallet buys: wallets funded in advance use similar construction and buy within the first slots without proven atomicity.
- Buy then disperse: one early address acquires inventory and transfers it through one or more layers of holders.
- Pre-launch allocation: supply is transferred or claimable before public execution and later appears as ordinary holder distribution.
- Hybrid structure: bundled buys, transfers, exchange deposits, and independent holders become mixed in the same visible holder set.
Preserve the pattern name. Calling every linked distribution a “bundle” obscures whether the evidence shows atomic execution, common funding, direct transfers, or only similar timing.
Rebuild the launch before reading today's holder list
Resolve the exact mint, curve or pool, first executable event, launch signature, and migration if applicable. Collect the earliest acquisitions with slot, transaction position where available, signer, fee payer, quote spent, tokens received, priority and tip evidence, failed attempts, and post-transaction balance.
Use the sniper-bot launch window to distinguish public execution speed from privileged preparation. The bundled supply question begins after that: which early positions were economically connected, how much did they control, and where did the tokens go?
Bundle evidence has a specific scope
A verified atomic bundle supports ordered coordination of the included signed transactions. It does not automatically reveal who requested the bundle, who beneficially owned every signer, whether the token team was involved, or whether the resulting supply was later sold together.
Record the tool's detection method and confidence. Same-slot execution is weaker than verified bundle membership, and an explorer label can be an inference. Read the atomic-execution guide for what bundle ordering and all-or-nothing behavior actually prove.
Build an entity hypothesis from independent links
Trace pre-launch SOL or quote funding, common upstream funders, account creation, fee payment, transaction construction, repeated sizes, token transfers, shared counterparties, later gas top-ups, consolidation, and exchange deposits. Stronger conclusions combine several link types across time.
Common routers, exchanges, RPC patterns, launchpad templates, popular funders, and same-slot public bots create false links. Apply the entity-inference ladder and label every connection as observed, supported inference, or unknown.
Calculate raw and entity-adjusted concentration
First classify pools, curves, burns, lockers, exchanges, program accounts, treasury, vesting, known team addresses, and unknown holders. Choose a denominator: total supply, circulating supply under an explicit rule, or supply available at a defined launch event. Then calculate top-holder concentration without clustering.
Recalculate under each supported entity grouping and show the difference. Avoid a single “bundled percentage” unless the tool's denominator, launch window, transfer treatment, excluded accounts, and clustering rules are disclosed. A range with confidence levels is more honest than false precision.
Follow the inventory through the exit
Track sells, transfers, liquidity provision, burns, bridges, deposits, and remaining balances for every candidate wallet. Compare timing, route, size, priority, and recipient. Coordinated exits, common settlement, or proceeds consolidation strengthen the common-control hypothesis and reveal who supplied exit liquidity.
Measure realized quote proceeds, remaining token overhang, and remaining inventory relative to current executable depth. The intended-size depth workflow turns a supply percentage into an estimate of market pressure.
Coordination is not automatically deceptive
A disclosed treasury, market maker, launch partner, vesting allocation, multisig, or coordinated community buy can place related wallets near the launch. Compare the onchain structure with published allocation, lock, mandate, identities, and sale restrictions. Verify the disclosure rather than assuming it excuses or condemns the activity.
Research datasets can use bundle-level features to detect high-risk launches, but model labels remain triage. They do not replace the transaction-level proof needed for a claim about one token or person.
A bundled-supply reconstruction workflow
- Fix the launch event. Save mint, curve or pool, executable signature, slot, migration, and the early-buyer window.
- Collect acquisition evidence. Record ordering, signers, fee payers, quote cost, token amount, priority, tip, and verified bundle membership.
- Trace funding and distribution. Follow pre-funding, transfers, dispersal layers, top-ups, and consolidation without skipping service labels.
- Build confidence-weighted entities. Combine independent link types and preserve competing explanations for every merged wallet.
- Recalculate supply and outcomes. Show raw and adjusted concentration, inherited cost basis, sells, proceeds, and remaining overhang.
- Write the narrow conclusion. Separate atomic coordination, likely common control, undisclosed concentration, and proven team attribution.
What belongs in the journal
Record launch event and window, early signatures and order, bundle detection method, signers and fee payers, quote cost and acquired tokens, funding sources, distribution paths, every entity link and confidence, excluded service and pool accounts, raw and adjusted concentration with denominator, inherited cost basis, sells and proceeds, remaining overhang, disclosure comparisons, alternative explanations, and the narrowest supported attribution.
Primary sources
Count controllers, not just addresses
Distribution is a flow history, not a holder screenshot.
Carry launch acquisition, funding evidence, and cost basis through every transfer so address dispersion cannot erase economic concentration.
Open the journal