Some launches are markets. Others are choreography with a chart attached. The Bundle Checker exists to tell you which one you are looking at before you commit size, by flagging coordinated buys that land in the same block.
The four-transaction rule
The Bundle Checker flags coordinated buys where four or more transactions land in the same block. Blocks are short, and independent buyers arriving in the same one is ordinary at four or more only when something is organising them.
It also filters wallets that do not show a consistent bundling pattern, which is the part that keeps the signal usable. Without that filter you would flag every coincidence and learn nothing.
The output is a bundle percentage: how much of the buying looks coordinated rather than independent.
| Block | Txns | Wallets | Verdict |
|---|---|---|---|
| #284,119,402 | 7 | 7 | Bundled |
| #284,119,403 | 2 | 2 | Clean |
| #284,119,411 | 5 | 4 | Bundled |
| #284,119,418 | 1 | 1 | Clean |
What a high bundle % implies
A coordinated launch usually means a group accumulated cheaply and simultaneously, and the chart you are reading was produced rather than discovered. That group's supply has to be sold somewhere, and it will not be sold to each other.
It does not mean the token cannot trade. Plenty of bundled launches run, and some run hard. It means your assumptions about who is on the other side should change, and your position size and time horizon should change with them.
The mistake is treating it as a verdict instead of a read. The number tells you about intent, not about the next candle.
The number tells you about intent, not about the next candle.
Use it as a filter, not just a check
Bundle % is one of the fourteen Pulse filters, alongside dev holding %, snipers %, insiders % and top 10 holders %. That means you can screen coordinated launches out before they ever reach your shortlist rather than checking them one by one.
This is the difference between a tool you use when you remember and a tool that shapes what you see. Set the threshold once and the feed enforces it for you.
Keep the checker itself for the launches you have decided to look at closely, where you want the block-level detail rather than a single aggregate number.
- Screen with bundle % in Pulse filters
- Inspect with the Bundle Checker before sizing
- Confirm with Trader Scan once trading begins
Reading it with the rest of the stack
Bundle % answers how the buying arrived. Dev holding %, snipers % and insiders % answer how the supply was allocated. Trader Scan answers what the holders have done since, wallet by wallet, including realized PnL and holding duration.
Those three reads rarely disagree. A launch with high bundle %, concentrated dev holding and a book full of short-duration flippers is describing itself clearly.
When they do disagree, that is information too. Coordinated early buying that has since been replaced by long-duration accumulators is a different market than it was at launch.
| Wallet | Bought | Sold | Balance | Realized PnL | Held |
|---|---|---|---|---|---|
| 7Fq…k9P | 412 SOL | 0 | 18.2M | +0 | 6h 12m |
| 9Az…m2C | 88 SOL | 310 SOL | 0 | +222 SOL | 41m |
| Ge4…t7X | 26 SOL | 24 SOL | 0.4M | -2 SOL | 3m |
| Bn1…q4L | 155 SOL | 40 SOL | 9.1M | +61 SOL | 2d 4h |
| Kd8…w1V | 12 SOL | 0 | 1.2M | +0 | 18h |
Where it matters most
Migrations. A token running up its bonding curve on coordinated buys is a token whose migration is much more likely to be an exit event than a beginning, and migration is exactly where traders commit size fastest.
Check bundle % on anything in Final Stretch before arming Sniper Buy. If it is high, either skip it or pair the entry with Sniper Sell so an unwinding migration is not your problem to solve manually.
The whole point of the tool is that it takes one click and it happens before the money moves.
What it is not
It is not a fraud detector, and it does not tell you a token will fail. Coordination is not always malicious and organic launches are not always safe.
It also does not replace liquidity checks. A perfectly clean launch with no liquidity is still a position you cannot exit, and exit safety should always be the first filter you set.
Treat it as one column in a read that includes supply distribution, wallet behaviour and the market you actually have to trade out of.