Pons's 32-Wallet Snipe-Tax Exemption List, Explained

What the exemption list actually does

Every Pons launch opens with a snipe tax: any buy that isn't on the launch's exemption list pays it during the launch window, on top of the curve's normal fee. A wallet on the exemption list skips that tax entirely for its buy inside the same atomic transaction as the launch.

This is the mechanism a Pons bundle actually relies on. The exemption list isn't a UI convenience - it's an array of addresses passed directly into the same on-chain call that creates the token, verified against Pons's own integration docs and against a real, successful launchAndBuy transaction traced on Blockscout (0x7e6d465829959be1c4768f1dbf4de8b1ae3777e92cb1943ef8de12e7e5a0e857) before we trusted the call shape for real transactions.

Why the cap sits at exactly 32 wallets

The Pons factory itself enforces a hard limit of 32 addresses on the exemption list - a call with more simply reverts. This isn't a bundler-imposed limit; it's baked into the deployed contract, so no bundler, including TokenBundle, can bypass it.

In practice, that means a single Pons launch can cover at most 32 other wallets buying tax-free, on top of the deployer's own atomic buy inside the launch call itself - 33 tax-free positions in total from one launch transaction.

The list is set once, and can't be changed after

The exemption list is an argument to the launch call, not a setting you can revisit. There's no add-exemption-after-launch function in the interface Pons exposes for this - once the launch transaction lands, that list is permanent for that token.

That has a direct planning consequence: you decide your wallet count and addresses before you launch, not after. If you're two wallets short of what you wanted, there's no follow-up transaction that fixes it - the next buyer in is just a normal, taxed buyer.

What happens to a wallet that isn't on the list

• It pays the launch-window snipe tax on its buy, in addition to the curve's ordinary fee.
• The tax decays over the launch window Pons documents in its own integration guide - if you want to confirm the practical decay on a specific real launch rather than take any single source's word for it, TokenBundle's Pons bundle checker lets you inspect a token's actual on-chain state directly.
• Once the window closes, every buyer - exempted or not - pays the same ongoing curve fee and creator tax.

FAQ

• Can I add more wallets to the exemption list after launch? No - it's fixed inside the original launch transaction and can't be edited afterward.
• What happens if I try to exempt more than 32 wallets? The launch call reverts - the factory enforces the 32-wallet cap itself.
• Does the dev wallet count toward the 32? No - the deployer's own atomic buy inside launchAndBuy is separate from the 32-wallet exemption list, so 32 exemptions plus the dev buy is 33 tax-free positions total.
• Is the exemption list public before launch? It's part of the launch transaction's calldata, so it becomes visible on-chain the moment the launch lands - not before.