Launch
Launch protection
Opening batch auction, anti-sniper limits, and what the app flags.
Sniper protection is built into the curve contract rather than bolted on afterward. Two mechanisms run back to back at every launch.
1. Opening batch auction (first 30 seconds)
From the moment a token is created, buys are not executed one by one: they are committed to a batch. When the window closes, anyone settles the batch and every commitment is filled at the same clearing price. Being first in the block buys nothing. Full details in Opening batch auction.
2. Anti-sniper window (120 seconds after the batch)
For a window anchored to the end of the batch (so the schedule is known in advance), every buy on the curve must satisfy:
| Limit | Default |
|---|---|
| Max tokens per buy | 0.5% of supply (5,000,000 tokens) |
| Max wallet balance | 1% of supply (10,000,000 tokens) |
| Cooldown between buys from the same wallet | 10 seconds |
Buys that would breach a limit revert (MaxTx, MaxWallet, Cooldown). After the window the limits are lifted. Sells are never limited.
Dev buy disclosure
If the creator buys at launch, that USDG is committed to the opening batch through the factory and recorded in the TokenCreated event. The token page shows the creator's holdings live and flags any later sale from the creator address in the trade feed.
What the app flags
From indexed events the app derives, per token: the creator's share of supply and whether the creator has sold, the top-10 holder share, bond status, LP status, and floor reserve size. These appear as the security strip on the discovery feed and in the security card on the token page.
Roadmap
A bundle/sniper detector (wallets funded from the same source buying in the same block), allowlist rounds, and the equal max-buy of a scheduled fair launch.