Snipers and launches

Buy new launches that match your filters with a budget and a breaker, backtested on the last days of launches first. Or launch your own token and trade it in one workflow.

Snipers#

A sniper is a workflow triggered by new launches. Every launch that matches its filter gets its own run of the steps, on its bonding curve.

A typical run buys on the curve, rests a take-profit ladder and a stop, then watches for graduation and trades the new pool.

Backtest it first#

backtest_sniper replays a sniper over the last days of real launches before you arm it: what it would have bought, totals, win rate, drawdown, and where the breaker would have tripped. list_launches shows recent launches and whether each would have matched.

Launch your own token#

A project can hold its own token launches, with supply steps, liquidity range rules and staged programs.

1. Define the launch

   The token, its launchpad (Pons, Flap or pump.fun), and the wallets that buy at launch.

2. Preview it

   ftw.trade predicts the token's address, its bonding curve and the pool it graduates into before anything is sent, so later steps can name them.

3. Write the workflow

   A manual workflow with a launch step sends it from the creator wallet ftw.trade holds; the steps after it read its outputs: buy on the curve, watch for graduation, then rest orders on the new pool.

4. Use a launch strategy

   Staged buys, dip buys, take-profit ladders, DCA in a band and counter-trading are ready strategies to run as stages.

On a live Pons launch, the launch book runs the whole workflow at chain speed: arm it, launch, and pause it if you need to.

Many wallets#

Launch desks often trade from many wallets. ftw.trade can:

• warm new wallets: fund each on a staggered schedule and run small round trips so they have history before a launch;
• buy aged wallets from the marketplace, with minimum age and transaction counts;
• fund them privately through Husher, so nothing on chain links them. See Private sends.