Jito Bundle Landing Reconciliation: From Submission ID to Confirmed Trades
Block Engine receipt proves submission, not atomic landing or economic success.
Jito Bundle Landing Reconciliation: From Submission ID to Confirmed Trades
Block Engine receipt proves submission, not atomic landing or economic success.
Model the failure correctly
Persist bundle ID, ordered signatures, blockhash expiry, tip, target opportunity, region, and expected deltas.
Collect evidence
Combine bundle-status polling with independent signature and landed-block verification.
Build the control path
After a timeout, resolve original signatures and blockhash validity before any replacement attempt.
Handle edge cases
Give replacements a new identity and recalculate quotes, balances, tips, and account locks.
Recovery procedure
After landing, compute actual fees, tip, token deltas, logs, and realized PnL.
Production metrics
Monitor pending age, landed rate by region, invalid reasons, tip-to-profit ratio, and unresolved attempts.
TierZero can help implement or review this architecture through our relevant engineering service.
Primary reference
See the official technical documentation and pin the exact API behavior used by your deployment.
Building this for production?
We turn this architecture into tested, non-custodial software with monitoring, documentation and deployment support.
Related technical guides
How Solana Sniper Bots Work: Jito Bundles, Priority Fees & Anti-Rug
What actually makes a Solana sniper land first — block engines, priority fees, transaction simulation and the rug checks that keep you out of honeypots.
Read articleToken Launch Anti-Bot Measures on Solana and How Bots Adapt
Launchpads increasingly deploy delay pools, fee tiers, and blocklist logic to deter bots. This post catalogs common anti-bot patterns seen on Solana launchpads and the countermeasures sophisticated sniper bots employ.
Read articleOrca Whirlpool Tick Ranges and How Bots Snipe New Positions
Orca's concentrated liquidity Whirlpool pools create predictable initial tick ranges on launch. This post dissects the pool initialization instruction and shows how bots size entries relative to the initial price range.
Read article