atomic-sniper-launch

Set DEV_BUY_SOL alongside the standard launch environment variables and run npm run launch. The fire-jito.js script places the createV2 instruction and your buy in one Jito bundle, so both execute atomically or neither does.

Tip size depends on launch visibility: 0.005 SOL for stealth launches, 0.01 for small community announcements, 0.02 for public Twitter posts, and 0.05+ for pre-announced fair launches. Snipers run automated tip escalation, so underbidding means their bundle lands first.

A 1 SOL dev buy is the standard visible-but-not-aggressive position. Below 0.5 SOL signals minimal commitment, while anything above 5 SOL is often read by the market as a pump-and-dump precursor and warrants a deliberate decision.

Run npx tsx tools/check-bundle-status.ts with your bundle UUID, then inspect the mint's trades on Solscan sorted by time. A non-creator buy in the same slot as your create transaction means a sniper paid a higher tip and landed first.

Skip it when you want a pure launch with no creator pre-buy, when the creator wallet should not appear as a holder, or when you want plausible deniability about dev-buying. Use atomic-launch with DEV_BUY_SOL=0 or a separate buy from a different wallet instead.

The inner transaction fails when DEV_BUY_SOL exceeds the funder's balance minus the Jito tip and rent. Over-provision the funder wallet by at least 0.05 SOL beyond the buy amount, tip, and rent combined.