BLOG · 1 Sept 2026 · 6 MIN
What a token bundler actually does
A bundler is a tool that creates a token and takes the opening position across several wallets in one coordinated sequence, rather than one wallet at a time. The word gets used loosely, so it is worth separating the mechanics from the folklore.
The problem bundling solves
A launch is at its most fragile in the first seconds. The supply sits at its cheapest, nobody has traded yet, and whoever moves first sets the tone for everyone who arrives later. If a team wants a position in its own token, it has to take it during that window or pay considerably more afterwards.
Doing it from a single wallet has two problems. On a bonding curve, one large order pays a worse average price than several smaller ones — that is arithmetic, not opinion. And a treasury sitting on one key is one compromised key away from being gone.
What the tool actually does
A bundler generates the wallets, funds them from a single source, creates the token, and sends the opening buys as one batch. The useful part is not the buying itself — anyone can send a transaction — but the coordination: every buy is prepared before the launch is sent, so nothing waits on the network in the middle.
- Generates a set of wallets and keeps their keys
- Splits funds from one wallet across the set
- Creates the token with its metadata and terms
- Sends the opening buys as a single coordinated batch
- Tracks each wallet's position afterwards, and sells on demand
What it does not do
A bundler cannot guarantee it goes first. On chains where transactions are ordered by arrival rather than by fee, no amount of money buys a better position in the queue, and the ordering inside a single block belongs to the sequencer.
It also does not create demand. A coordinated opening buys a position; it does not make anyone else want the token. Every honest description of the tool stops there.
Where the protocol meets you halfway
Some launchpads treat bundling as an attack and try to stop it. Others treat it as a normal thing a team does and give it a documented path. pons is the second kind: a creator names team wallets when the token is created, and those addresses are exempt from the opening tax that everyone else pays.
That distinction matters more than it sounds. Using a documented parameter is a different activity from working around a protection, and it is the difference between a tool that keeps working and one that breaks on the next contract upgrade.
The longer version, with the numbers this article refers to.
Keep reading
6 min read
The pons snipe tax window is three seconds, not five
The documentation says five seconds. The deployed contract returns three. Here is how to read the real value, and why the difference decides whether a bundle lands inside the window.
5 min read
The exemption list: 32 addresses, fixed at creation
pons lets a creator name up to 32 addresses that the opening tax does not apply to. The list is fixed when the token is created and can never be extended.
6 min read
Why one large buy costs more than several small ones
On a constant-product curve, a single large order pays a worse average price than the same amount split into pieces. The arithmetic, and where it stops being true.