"Landed" vs. "Confirmed": Reading Your Launch Status Correctly

Watch a launch go through and the log settles on one of a few different outcomes. They look similar at a glance — all of them mean "something didn't go the way you wanted" — but they're not the same failure, and knowing which one you're looking at changes what actually happened to your funds.

Landed successfully

The bundle made it into a block and every instruction inside it executed without error. Token created, wallets bought. This is the only outcome where funds actually moved as intended.

Landed but failed on-chain

The bundle made it into a block, but something inside it reverted — the instructions ran, and the network rejected them. This is a meaningfully different situation from not landing at all: a transaction that reaches this state and fails still pays network fees, even though nothing it was trying to do actually happened. No tokens change hands, but the attempt wasn't free.

Not confirmed within time budget

The bundle was never seen landing at all, inside our checking window. This is the outcome that looks the most like a hard failure and often isn't one — Jito doesn't error out a bundle that doesn't get picked up, it just goes nowhere, silently. Wallet balances in this state are usually untouched, since nothing executed.

Why the distinction matters for what you do next

"Landed but failed" means the attempt is over and cost something small in fees — worth checking what specifically reverted before trying again with the same configuration. "Not confirmed" means the attempt may still resolve, or may simply never have been picked up — worth checking wallet balances before assuming anything was spent, since in most cases nothing was.

You'll see all three phrased exactly this way in the log on the Launch page's final step, along with the same status breakdown per snipe wallet if you're running a snipe wave alongside the bundle.