atomic-launch

Upload metadata with metadata.js to get an IPFS URI, then run fire-jito.js with FUNDER_SECRET and CREATOR_SECRET set. The funder pays rent and the Jito tip in Tx1 while the creator signs createV2 in Tx2, both landing atomically in one bundle.

fire-jito.js uses a two-transaction Jito bundle with MEV protection and supports a same-bundle dev buy, but costs a tip. fire-atomic-create.js is a single transaction with no Jito tip, where the funder pays fees and the creator only signs.

Bundles often fail when the tip is too low; raise JITO_TIP from the 0.005 default to 0.01-0.02 SOL. If you get a tip-account write-lock error, the hardcoded tip accounts have drifted and must be refreshed from the Jito Block Engine getTipAccounts RPC.

Yes, set DEV_BUY_SOL to a nonzero amount when using fire-jito.js and the dev buy executes in the same atomic bundle as the create. Set it to 0 to skip; the single-transaction launcher does not support this.

The pump.fun create instruction is already near the 1232-byte transaction size limit, so adding a rent transfer and tip in the same transaction exceeds it. That is why the Jito flow splits funding and creation into two transactions within one bundle.