People treat a Pump.fun sniper like a latency toy. Faster gRPC, fatter Jito tip, more endpoints. That is how you lose slower.
The thing that actually decides the trade is this:
The create transaction is already the full buy template. If you wait for a second read of the curve, you are not sniping. You are auctioning leftovers after the atomic bundle.
What the chain actually does
A launch is create / create_v2 on 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P. Bonding curve PDA is deterministic:
bonding_curve = PDA(["bonding-curve", mint])
CreateEvent already carries mint, creator, quote mint, mayhem/cashback flags, virtual reserves. A serious buyer never calls getAccountInfo between detect and send. They patch a pre-built buy / buy_v2 at fixed byte offsets and fire.
Creators know this. In 2026 the default defense is a Jito bundle: create + creator buy + N wallet buys as one atomic envelope. Nothing inserts between those instructions. Your earliest legal slot is after that envelope. “Block 0 snipe” against a bundled launch is a slogan. You are block 0 of the remainder.
Virtual reserves start around 30 SOL / ~1.073B tokens. Real tokens sold on the curve are the usual ~800M-class slice. Price is the product, plus 1.25% on every fill (0.30% creator + 0.95% protocol on the curve). You pay that on the way in and on the way out.
Why people miss
- They listen to the wrong layer.
logsSubscribe and third-party “new coin” APIs are late. Some feeds still drop tx v1 creates. Shred / Geyser sees the create bytes in the first shred of the segment, not after the block is cooked. If your detector is HTTP, the bundle already landed.
- The instruction layout moved and their tx never simulates.
Pump is not a stable ABI. buy vs buy_v2 (27 accounts). Creator vault. Volume accumulators. Fee program. The 2026-04-28 trailing fee-recipient account. USDC-paired curves that reject SOL. A bot that still sends the 2025 account list fails 100% of the time and still burns priority fees. Misses look like “RPC is slow.” They are InstructionError.
- They quote a curve that no longer exists.
By the time a Telegram bot paints the mint, the bundle already lifted virtual SOL. Your 5% slippage is a coin flip against 16 bundled wallets. Simulation used empty reserves. Execution used post-bundle reserves. SlippageExceeded. You paid the tip anyway.
- ATA + compute.
First buy must create the ATA. That extra ix + account data size limit is why “it worked on paper” dies in the slot.
Why people lose after they “win”
Landing a fill is not a PnL.
Graduation is rare (often <1%). Most snipes are inventory in a token that dies at 3% of the curve.
The other side of your bid is the same desks. They exit into you.
Jito tip + priority + 1.25% × 2 + the Telegram bot’s 0.5–1% is a tax on attempts, including fails.
You sized like you were first. You were tenth through the same product. Tokens per SOL collapsed; your average is already mid-curve.
Speed without an exit that does not share the entry cluster is just a faster donation.
How I figured it out
Not from a vendor blog. From the txs that landed versus the ones that did not.
Diff a bundled launch against a naked create. Same program, same slot shape. One has create then N buys in one Jito bundle. The other is create-only. Every “I was first” fill I logged sat after the first pattern. Once you see that, racing Yellowstone against a bundle is a category error.
Replay failed signatures. The error was almost never “lost the race.” It was missing creatorvault, wrong fee recipient after Apr 28, stale buy instead of buyv2, or maxsolcost computed on pre-bundle reserves.
Time the path. Detect timestamp (shred 0) vs signed send vs landed slot. Code after the event was microseconds. The hole was: RPC fetch of the curve, ATA rent check, fresh blockhash wait. Remove those and you still lose to atomic order, not to 2 ms of RTT.
Watch net SOL on the curve, not volume. Wash and snipes both print volume. Only one moves realsolreserves from new wallets. When volume spiked and unique funders did not, the “snipe” was circular. Exit liquidity was a ghost.
The important technical object is not the sniper. It is the create transaction as a closed set of accounts. Decode that set, pre-sign against it, and treat a Jito create+buy envelope as a filled book. Everything else is paying Solana to learn the same lesson again.
Telegram: https://t.me/C00LBB
Site: https://coolbb.site
Top comments (0)