BLOG · 5 Sept 2026 · 5 MIN
The exemption list: 32 addresses, fixed at creation
When a token is created on pons, the creator can name additional addresses that the opening snipe tax does not apply to. The protocol documentation describes this as being for a team bundling its opening buys across several wallets. There is a hard ceiling of 32, and the list cannot be added to afterwards.
Why this exists at all
The tax is aimed at outside bots, not at the team launching the token. Without an exemption a creator would be taxed out of their own opening, which serves nobody. The launching address and the creator fee recipient are exempt automatically; the named list covers everyone else on the team.
Fixed means fixed
The list is written at creation and there is no function to extend it. Not a policy — the capability does not exist in the contract. A wallet you did not name cannot be added later, however good the reason.
The practical rule that follows: name every wallet you might ever want, whether or not it buys on the first day. An address on the list that never trades costs nothing. An address you wish you had listed costs the full tax for the rest of the window, and there is no fixing it.
Thirty-two, and not thirty-three
Pass more than 32 addresses and the launch reverts with ExemptionListTooLong. The transaction fails outright rather than trimming the list quietly, which is the right behaviour: a silently truncated list would mean wallets paying tax for reasons nobody could see.
What it buys you
Exempt wallets pay zero while the window is open. In a measured run, an outside buyer at that same moment still owed 618 basis points — a little over six percent of their spend. That gap is the entire practical advantage of the mechanism, and it only exists while the window is open.
Which is the point worth sitting with: an exemption without speed is worth nothing, because by the time a slow bundle arrives the tax has decayed for everyone anyway.
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.
6 min read
How many wallets should a bundle use?
Between 5 and 32 wallets, and the right number depends on position size, gas overhead and how much dispersion you actually need. The trade-offs, with numbers.
6 min read
What a token bundler actually does
A bundler creates a token and buys its opening supply from several wallets in one coordinated move. Here is what that means mechanically, and what it does not mean.