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

# sniping

> block-targeted buys

# sniping

snipe wallets fire at specific blocks after token creation. they're independent transactions (not bundled), each targeting a specific slot relative to the creation block.

## why block 1, not block 0

block 0 is for [bundles](/platform/bundles). bundles are atomic — they land in the same jito bundle as token creation, guaranteed same slot. if you want buys in block 0, use a bundle wallet.

sniping starts at block 1 because snipe transactions are independent. they're built and signed before launch, then submitted when the target block arrives. this gives you buys that look like separate actors reacting to a new token — not coordinated bundle activity.

## how it works

```
block 0:  token created (jito bundle with dev buy + bundles)
block 1:  snipe wallet A fires    ← first possible snipe target
block 2:  snipe wallet B fires
block 3:  snipe wallet C fires
```

each snipe wallet has a `block_target`. the system monitors the rpc for the current slot and fires when `current_slot >= create_slot + block_target`.

the transactions are pre-built during launch setup. when the target slot arrives, they're submitted immediately. no delay from transaction building — it's fire-and-forget.

## slot targeting

solana doesn't have traditional "blocks" — it has slots (\~400ms each). when you set `block_target = 1`, the system waits for the next jito leader slot after creation.

jito validators lead \~7% of all slots. the actual slot delta depends on leader scheduling:

* **best case**: target slot is the next jito leader → fires 1-2 slots after creation
* **typical**: 5-50 slots after target, depending on jito leader schedule
* **worst case**: up to \~200 slots if jito leaders are sparse in that range

the system uses jito leader scheduling data to submit at the optimal time.

## config

| param                | what                                   |
| -------------------- | -------------------------------------- |
| **wallet**           | must be `snipe` type                   |
| **buy\_amount\_sol** | sol per snipe                          |
| **block\_target**    | slots after creation (1, 2, 3...)      |
| **slippage\_bps**    | slippage tolerance (default: 500 = 5%) |

## prefunding

snipe wallets are automatically prefunded from the dev wallet before launch, same as bundles. each needs the buy amount + gas reserve.

## usage patterns

* **block 1 snipes** — look like fast reactions to a new token. hardest to distinguish from organic snipers.
* **staggered (block 1, 2, 3)** — simulates multiple people discovering the token at different times
* **heavy block 1** — maximum early accumulation after bundles

## tips

* combine with [bundles](/platform/bundles) in block 0 for maximum block 0+1 coverage
* vary buy amounts across snipe wallets
* 3-5 snipe wallets across blocks 1-3 is a solid setup
* snipe wallets are separate from bundle wallets — use both for different blocks