Jito Bundles

Sandwich attacks are a real risk on Solana when swaps are broadcast through standard public submission paths. This guide explains the risk and why many teams recommend bundle-based submission for sensitive order flow.

The Problem

When you submit a swap through standard public submission paths, searchers can react to that order flow:

• Sandwich attack — Buy before your swap (frontrun), then sell after (backrun), profiting from the price impact you created
• Frontrun — Detect your pending swap and execute the same trade ahead of you

This typically costs users 0.1-1% of their swap value.

Why Teams Use Bundles

1. Lower public exposure — bundle-based submission can reduce how broadly a transaction is exposed before execution
2. Cleaner submission path — dedicated submission flows can be more robust than relying on one public RPC endpoint
3. Atomic execution — the transaction either executes as-is or fails entirely
4. Less custom plumbing — many teams prefer a hosted sending surface instead of wiring bundle submission themselves

Practical Guidance

• If you care about sandwich risk, avoid relying only on standard public submission paths
• Consider bundles where they fit your flow and venue support
• If you want a simpler integration, Venum's transaction sending endpoints can handle the submission step for you, but they are not a guarantee against MEV or failed landing