Bubblemaps: a visible connection is not proof of common ownership

The short answer

Bubblemaps V2 is a visual holder and transfer-analysis tool. Its default map shows a token's top 250 current holders as bubbles sized by holdings, with links for detected onchain transfers. It can reveal direct clusters, add intermediary Magic Nodes, surface timing-based Time Nodes, rewind distribution with Time Travel, and include manually imported addresses.

Bubble size, bubble rank, and link each answer a different question

A bubble represents a current holder in the selected map, its size reflects that address's token balance, and its rank reflects the holder list. A link means two displayed addresses have transferred assets between them under the active filters. Bubblemaps V2 can show transfers involving other tokens and, in some cases, cross-chain activity.

A link does not say who controlled either address, whether the transfer was payment, exchange withdrawal, market making, vesting, an OTC deal, or self-funding, or whether it happened before the token existed. Click the link, inspect asset, direction, amount, dates, and transaction hashes, then test alternative explanations in explorers.

The default graph is intentionally incomplete

The standard map is limited to top holders. Contracts and exchange addresses can be hidden by default, and high-volume “Supernodes” have restricted transfer details or omitted links to control computation. Smaller holders, emptied intermediary wallets, undiscovered labels, custodial ledgers, bridges, mixers, and unsupported activity can sit outside the visible graph.

Reveal hidden nodes, inspect the address list, and export the map before calculating concentration. Exclude known pools, lockers, burns, programs, and exchange omnibus accounts only with evidence, and preserve both raw and adjusted percentages. A tidy graph may mean the relevant relationship is outside the default scope.

Magic Nodes expand the graph through intermediaries

Magic Nodes add addresses beyond the current top holders when those intermediaries connect visible holders—for example, a common gas funder, deposit address, or wallet that distributed its entire token balance and now holds zero. This can recover a pattern hidden by a present-day holder list.

The additional path still proves only the displayed transfers. A shared gas source could be an exchange, faucet, relayer, launch service, employer, or controller. Record every hop, service label, timing, value, and later behavior before merging balances into one entity. Use the explorer workflowto verify the underlying transactions.

Time Travel separates launch distribution from today's holders

Current distribution can hide early allocations after insiders sell, disperse, or move tokens. Time Travel reconstructs earlier top-holder maps, while the date picker and price chart help compare launch and later states. This is most useful when examining vesting, market-maker inventory, influencer allocations, snipers, and distribution waves.

Save at least three snapshots: launch or earliest available, the event under review, and current. Compare balances, cluster percentages, new and missing addresses, and transfer paths. Historical top-holder scope is still not every wallet, and historical labels can incorporate later knowledge; preserve the map's computation time and filters.

Check the map timestamp before calling a cluster current

Bubblemaps says V2 maps are refreshed within the previous six hours, with possible additional delay for new launches. Six hours is material in a fast market. A cluster percentage can change through trades, transfers, burns, liquidity movements, or supply updates before the map recomputes.

Record the displayed map time and compare the listed balances with current explorer token accounts. Use a permalink to preserve filters, enabled Magic or Time Nodes, date, and manually added addresses. A screenshot without configuration and timestamp is weak evidence.

A defensible cluster workflow

1. Resolve the token. Match chain and contract, then record map time, historical date, holder limit, and hidden-node state.
2. Classify the largest bubbles. Identify pools, lockers, burns, programs, exchanges, team, treasury, and unknowns without guessing.
3. Inspect each material link. Save asset, direction, value, date, transaction, and whether it predates launch.
4. Expand carefully. Enable Magic Nodes, inspect Time Nodes, and manually add relevant addresses while documenting why.
5. Compare time states. Rebuild launch, event, and current distribution rather than reading one snapshot.
6. State confidence and alternatives. Separate direct evidence, platform inference, your hypothesis, and plausible non-common-control explanations.

What belongs in the journal

Record chain and contract, map URL and computation time, historical date, top-holder limit, hidden nodes, transfer filters, manually added addresses, Magic and Time Node state, bubble ranks and balances, cluster percentage, every material transfer hash, service labels, alternative explanations, and confidence level. Keep the export with the written conclusion.

Primary sources