Bundled Supply: When a Launch Was Bought in One Block

On a new launch the holder count is the first number anyone looks at, and it is the easiest one to manufacture. Bundling is how it is done: a deployer funds a set of wallets before launch and buys through all of them in the same block the token goes live. Sixty seconds later the chart shows two hundred holders. The reality is one person holding two hundred addresses.

What bundled actually means

A bundle is a group of transactions submitted so that they land in the same block, in an order the sender chose. On chains with a public mempool that is arranged through a block builder. Robinhood Chain has no public mempool, which changes the route but not the outcome – a deployer can still send the buys back to back in the same block as the deployment, and a sequencer producing blocks every hundred milliseconds gives nobody else time to arrive first.

The technical route is not the point. The point is that supply which arrived in the opening block, from wallets funded by the same source, is not demand. It is inventory that has been distributed across addresses.

Why it survives a holder chart

Every check people run on a new token is a check on concentration. Top ten holders, percentage held by the largest wallet, number of unique addresses – bundling is designed to pass all three. Split a third of supply across two hundred wallets and no single one looks alarming, the top ten is unremarkable, and the holder count reads healthy.

How to see it in five minutes

1. Open the contract on Blockscout Explorer and sort transactions oldest first. The deployment is transaction one; read what lands in that block and the next one.
2. Count the buys in those two blocks and add up what share of supply they took. That total is the bundle, whatever the wallets are called.
3. Run the token through Bubblemaps. It clusters addresses that share a funding source, which is the part a holder chart will never show you.
4. Check the launchpad's own mechanics. PONS and hood.fun publish what is sold on the curve and what the deployer keeps, so an unexplained block-one position has to come from somewhere else.
5. Watch whether the cluster has moved since. A bundle that is still sitting is a position; a bundle already distributing is your counterparty.

What the share means

Bundling is not automatically a scam

A deployer buying their own token at launch is not fraud, and on several launchpads it is disclosed. Teams bundle to stop snipers taking the entire opening float, which is a real problem with a real cost. The question worth asking is not whether a bundle exists but whether it was disclosed, how large it is, and whether it has started moving.

The dishonest version is the one presented as organic demand – a holder count in the marketing, a chart that went vertical in the first minute, and no mention that one wallet paid for all of it.

What to do with the number

• Treat bundled supply as float that can arrive at any price, and size as though it will.
• Set your exit against the cluster's cost basis, not against a round number – they are in profit long before you are.
• Re-check after a move. A bundle that stayed still through a 3x is a different signal from one that sold into it.
• If the share is above 30% and undisclosed, the honest read is that the chart is someone's plan rather than a market.

None of this tells you the token will fail. Plenty of bundled launches run for weeks. It tells you who is on the other side of your trade, which is the one thing the holder count was hiding.