> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperpad.fun/llms.txt
> Use this file to discover all available pages before exploring further.

# Anti-snipe

> Cap the bots in the opening blocks — without the power to honeypot.

Snipers love a fresh pool: bundle the first block, grab a huge bag, dump on your buyers. HyperPad's
anti-snipe guard lets you throttle that — a **per-wallet cap for a short window** right after trading
opens.

## What you set

| Field                  | Meaning                                                            |
| ---------------------- | ------------------------------------------------------------------ |
| `antiSnipeBlocks`      | How many blocks the cap stays active after trading opens (0 = off) |
| `maxWalletDuringGuard` | The per-wallet token cap during that window (0 = off)              |

Set either to a non-zero value and the guard turns on.

## How it works

<Steps>
  <Step title="Trading starts closed">
    The token can't be transferred between regular wallets until your sale settles and the LP is
    seeded — so no one can trade ahead of your buyers.
  </Step>

  <Step title="The cap bites pool buys">
    For `antiSnipeBlocks` blocks after trading opens, any transfer **to a fresh wallet** (a market buy
    out of the pool) is capped at `maxWalletDuringGuard`. The sale, your team wallet, the LP adapter,
    the factory, and the claim vault are all **exempt** — so claims and liquidity are never blocked.
  </Step>

  <Step title="The cap expires">
    Once the window passes, the token transfers freely with no restrictions. It's a speed bump, not a
    permanent tax.
  </Step>
</Steps>

## You can't honeypot with it

<Warning>
  The guard can throttle but it **can't trap**. When the guard is on, the form sets a
  `tradingAutoOpenAt` backstop (default: sale end + 7 days). After that timestamp, **anyone** can call
  `forceOpenTrading()` — so even if something goes wrong with settlement, trading can always be opened
  permissionlessly. There's no "trading disabled forever" state for a project to abuse.
</Warning>