Backrun vs Sandwich: When to Use Each Strategy

Overview

Pros/cons of backrun vs sandwich, with decision cues and safeguards.

TL;DR

• Prefer backrun on liquid, trusted pools.
• Sandwiching raises ethical/compliance concerns; disable by default.
• Always simulate and cap slippage.

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

• Backrun: follow a large swap moving price toward your direction; reference tx hash.
• Sandwich: often blocked; avoid unless policies allow and risks addressed.

Checklist

• [ ] Liquidity depth sufficient
• [ ] Router allowlist
• [ ] Slippage <= threshold

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 agent to scan mempools and submit private bundles with custody preserved.
→ Try FRB or watch the 2‑min demo on the homepage.