Snipe protection

A launch is most vulnerable in its first moments. A bot watching for new curves can buy the opening before anyone else has seen it, then sell into the people who arrive a minute later.

Every Hanok launch therefore opens with a tax on buys that makes being first unprofitable and disappears within seconds.

Schedule

The tax starts at 99% of the ETH spent when trading opens and halves every second for a 10-second window, then drops to zero.

Seconds after open	Snipe tax
0	99% (capped so the buyer still nets ≥ 1%)
1	49.5%
2	24.75%
3	12.4%
5	3.1%
10+	0%

The tax is capped so that platform fee + creator tax + snipe tax never exceeds 99%, so a buyer always receives something.

Where it goes

Snipe tax is not burned. It is credited to the creator, so the value a sniper gives up flows to the launch rather than out of it.

Exemptions

The launching wallet and the creator fee recipient are exempt automatically. A creator can also name up to 32 additional wallets at launch (for a team bundling its opening buys). Exemptions are fixed at creation and cannot be added later.

The creator's optional first buy executes inside the launch transaction and is never taxed.

Scheduled launches

A creator can set a trading start time up to 7 days ahead. The snipe window starts at that time, not at deployment, so an announced launch is protected exactly like an instant one.

For integrators

Read currentSnipeTaxBps(recipient) on the curve, or simply use quoteBuy(quoteIn, recipient) which already applies it. It is keyed on the wallet that receives the tokens. See trading and quotes.