Overview

A clear guide to Flashbots bundles and private MEV execution with custody preserved.

TL;DR

• Private bundles reduce exposure, frontrun risk, and PGA waste.
• Always simulate; reference triggering tx for backruns.
• Monitor inclusion and handle failures gracefully.

Key points

• Clear definitions and when this topic matters for MEV practitioners.
• Step-by-step guidance you can apply inside FRB today.
• Risk notes and guardrails (no profitability guarantees).

Walkthrough

1. Setup — ensure reliable RPC/WSS endpoints and time-sync.
2. Configuration — start with simulation/canary, set slippage and budget caps.
3. Execution — prefer private bundles when available; monitor inclusion and adjust.
4. Review — log outcomes, tweak filters, and iterate conservatively.

Example

• Disable sandwich by default; prefer backrun on trusted pools.
• Use MEV‑Share or a private relay to deliver bundles.

Checklist

• [ ] Simulation success
• [ ] Correct triggering tx reference (for backrun)
• [ ] Slippage caps set
• [ ] Relay reachable; fallback configured

Risk & compliance

MEV is experimental and high-risk. Slippage, inclusion uncertainty and reorgs can cause losses. You are responsible for legality in your jurisdiction.

Next steps

Use the FRB bot to scan mempools and submit private bundles with custody preserved.
→ Try FRB or watch the 2‑min demo on the homepage.