Anti-Snipe
Protection is defined before launch, then ends.
BLOCK 0 ━━━━━━━━━━━━━━ BLOCK 20 │ BLOCK 21 → ∞
└──────── protected ────────┘ unprotectedAnti-snipe has three parameters, all frozen at launch.
| Parameter | Meaning | Cap |
|---|---|---|
| duration | how many blocks after launch the rule applies | 200 blocks |
| max buy | launch tokens that may leave the pool per block | ≥ 0.01% of supply |
| extra fee | additional quote-side fee inside the window | 3.00% |
The cap is per block, not per address
The trade-off is real and worth stating: a sniper can consume the whole block's quota themselves. What they cannot do is consume it cheaply — the price rises as they buy, and they pay the extra fee on top for the length of the window.
A buy that would push the block's cumulative token outflow past the cap reverts with AntiSnipeCapExceeded, reporting both the attempted total and the cap.
Where the extra fee goes
To the creator's fee recipients, on their configured splits. That is a product decision rather than an accident: the creator chose the rule, so the proceeds are labelled as theirs everywhere in the interface and in the manifest instead of being quietly absorbed by the protocol.
It ends
At launchBlock + duration the window closes and both the cap and the extra fee stop applying. There is no function to extend it, no owner override, and no way to re-arm it. The interface draws the protection as a cover that simply stops.
TAPEZERO is an independent protocol and is not affiliated with Robinhood, Uniswap or Chainlink. The contracts are unaudited. Nothing here is investment advice.