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.

Discuss your system with TierZero.