
Overview
How to scan mempools in real time, tune filters, and think about inclusion probability.
TL;DR
- Low‑latency WSS + selective filters = better signal/noise.
 - Avoid over‑filtering that kills recall.
 - Monitor inclusion vs false positives.
 
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
- Setup — ensure reliable RPC/WSS endpoints and time-sync.
 - Configuration — start with simulation/canary, set slippage and budget caps.
 - Execution — prefer private bundles when available; monitor inclusion and adjust.
 - Review — log outcomes, tweak filters, and iterate conservatively.
 
Example
- Filter: pool whitelist + min notional + router allowlist.
 - Measure: median arrival delta vs peers; inclusion %.
 
Checklist
- [ ] WSS < 150ms median
 - [ ] Backpressure handling enabled
 - [ ] Filter recall validated on sample blocks
 
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.
Related
Further reading & tools
Comments
Adding a “pitfalls” section was a nice touch.
Great primer on private bundles and risks.
Benchmarks vs public PGA would be amazing.
Would love a follow-up on simulation best practices.
Can you add guidance for BNB-specific routing?
Would love a video walkthrough for setup.
The TL;DR makes it easy to share with teammates.
This helped me fix my inclusion issues last week.
The checklist was super helpful—please add a section on reorgs.