atomic

Use the fire-jito.js script via npm run launch. It builds a two-transaction Jito bundle where the funder pays rent and the Jito tip in Tx1 and the creator signs createV2 in Tx2, so both land atomically or neither does.

Run collect-jito.js via npm run collect. It combines collectCoinCreatorFee and a drain to your DESTINATION wallet in a single transaction, so funds never rest in a leaked or shared creator wallet between transactions.

The most common causes are stale hardcoded tip accounts, a tip below the auction-clearing price, or an expired blockhash. Run npm run check-tip-accounts to refresh the tip list and raise JITO_TIP to 0.01-0.02 SOL in busy markets.

Yes. Use buy-jito.js via npm run buy, which routes the purchase through the Jupiter aggregator inside a Jito bundle. Jupiter abstracts the account list, so pump-sdk instruction drift does not break the buy.

Move funds immediately to a fresh wallet using rescue-tokens.js or consolidate.js, which bundle the drain atomically so sweepers cannot insert between steps. Then burn the wallet, since sweepers will re-drain any future deposits.

SOL-paired coins keep working on V1 instructions, while USDC-paired coins require V2 builders that accept a quote_mint argument. The docs/v2-usdc-rollout reference covers event layouts, discriminators, and migration recipes.