ThemeFontsMountReady
SEND
DocsPricingFeaturesComparisonsHelpSign inRequest access →

SEND / Docs

Launch Sniping

How a launch snipe is configured in the project wizard, the wallet limits it imposes, and how it executes on-chain.

← DocsTrading8 min readUpdated August 10, 2026

Sniping is a Launch Setting, Not an Order

A snipe on SEND is not something you place against an arbitrary token. It is the execution strategy for your own project's launch, chosen in the project creation wizard on the Strategy step and fired when you press Launch Token.

Because everything was configured on the project, the launch request itself carries no parameters at all -- the platform, the dev wallet, the allocation, and the wallet roster are all read from what you saved. There is no way to change them at launch time.

Bundling is not available. The Bundling strategy card is disabled and labelled "Coming soon", and the services behind it are empty shells with no implementation. Sniping is the only selectable strategy, and it makes no atomicity guarantee: snipe transactions are submitted in parallel, not as one all-or-nothing unit.

What You Configure

The knobs that shape a snipe all live in the create-project wizard:

  • Platform -- all four are launchable: pump.fun and BonkFun launch onto a bonding curve, while Raydium (CPMM) and Meteora (DLMM) launch straight into an AMM pool
  • Dev wallet -- creates the token, and is deliberately excluded from the buy transactions
  • Dev buy percentage -- 0 to 10% of supply in 0.1% steps, defaulting to 0. Bonding-curve platforms only; AMM launches skip this step
  • Allocation percentage -- the share of supply your snipe wallets buy, defaulting to 50%
  • Participating wallets -- how many wallets buy, up to a hard maximum of 250

The Wallet Math You Will Hit

No single wallet may take more than 0.8% of supply, so your allocation dictates a minimum wallet count: the minimum is the allocation divided by 0.8, rounded up. A 50% allocation therefore needs at least 63 wallets.

Bonding-curve platforms add a second limit. Only part of the supply is buyable on the curve -- 79.31% on pump.fun, 73.2521% on BonkFun. Allocating above that cap splits the launch into two phases: pre-graduation buys on the curve, and post-graduation buys on the DEX.

On a split allocation each phase is wallet-ceiled independently, so the true minimum can be one wallet higher than the flat division suggests. The wizard computes the real figure for you -- provision to what it asks for, not to your own arithmetic.

How the Snipe Executes

On pump.fun and BonkFun every leg of the launch is signed against a single blockhash up front and laid out on an absolute timed schedule, one wave roughly every 400 milliseconds.

Wave 0 carries the create-token transaction, the dev buy, and the decoy buys together -- 7 transactions with 5 decoys, 17 with 15. The snipe buys go out in a later wave, chosen so it sits beyond the roughly 2.2-second window in which an observer could react to the launch.

Ordering within a slot is bought with a strictly descending priority-fee ladder: the create transaction at 60,000, the dev buy at 50,000, decoy buys at 40,000, decoy sells at 35,000, and the snipe buys at 30,000 and below. That ordering is what keeps the token created before anything tries to buy it.

If a leg stalls, it is resubmitted as the exact same retained bytes. The signature is unchanged, so Solana de-duplicates it and it can land at most once. Re-signing against a fresh blockhash would risk executing a launch leg twice, so SEND never does it.

Decoys and the Exposure Gate

A snipe launch includes 5 to 15 decoy wallets. Each is a pair of transactions -- a buy, and a sell that is pre-signed but withheld from wave 0 so it cannot land in the same slot as its own buy. The withheld sells are released later in response to observed external buys. The first decoy is the exception: it buys a dust position and has no sell transaction at all.

Before every buy wave after the first, an external-exposure gate weighs how much of the supply outside buyers are currently holding. Wave 0 is structurally ungated -- it carries the create transaction and is away before any measurement window exists. From the next wave on, outside holdings above the threshold -- roughly 1.76% of total supply by default -- withhold that wave, and the withheld wave's pre-signed decoy sells are discarded with it so no sell is ever submitted for a decoy that never bought.

Decoy count, tranche sizing, and the exposure threshold are operator-tuned settings, not user settings. They are described here so the on-chain behaviour of your launch is not a surprise, but they do not appear in the wizard.

Mint Addresses

Every suffix-branded platform claims its mint keypair from a pre-ground vanity pool, each from its own category -- pump.fun and BonkFun both do -- so the token address carries that platform's branded suffix. Raydium and Meteora launches get a freshly generated random keypair instead, because no branded suffix exists for those platforms.

If a vanity pool is drained, the launch fails with an error. SEND never silently falls back to an unbranded mint under a suffix-branded platform.

A launch is irreversible. The token is created, the dev buy and every snipe buy are signed and scheduled before the first transaction goes out, and there is no cancel once Launch Token is pressed. Confirm the wallet roster and funding before you fire.
←Previous
Market Orders
→Next
API Authentication
Was this article helpful?

SEND

Execution infrastructure for Solana. Coordinated execution across thousands of wallets, with a footprint that reads as thousands of strangers.

TwitterDiscordGitHub

Product

FeaturesPricingComparisonsChangelogDocumentation

Company

AboutAmbassador ProgramContact

Legal

PrivacyTerms

Support

Help CenterDiscordTwitter

© SEND 2026 — All rights reserved

Powered by ChainKit