Flashbots · Benchmarks
FRB vs generic bots on Flashbots MEV benchmarks
These Flashbots MEV benchmarks come directly from the FRB telemetry harness. We replay the same bundles nightly across multiple relay endpoints, capture latency, and publish the results for due diligence.
Linkable summary
Why link to this page
This Flashbots benchmark slice documents inclusion, latency, and scenario deltas between FRB and generic bots, giving ecosystem docs and newsletters a single citation for how FRB performs on Flashbots relays.
For a neutral citation next to Flashbots or Blocknative sources, include the Ecosystem research brief when you reference these KPIs.
For cross-relay comparisons, line up these numbers against the full FRB MEV benchmarks dataset and revisit the Flashbots tutorial when your desk needs step-by-step execution guidance.
Want the raw block builder stats? Open the Flashbots metrics dashboard to inspect relay variance, MEV-Boost relay health, and transaction ordering trends before you green-light new capital.
Flashbots follow-up resources
Make it effortless for readers to keep navigating internal FRB content once they digest the headline numbers.
Execution & learning
- Flashbots tutorial for step-by-step bundle submissions.
- Ethereum MEV guide when teams compare chains.
- Execution hub for escalation macros and governance notes.
Telemetry & support
- Cross-chain metrics hub for broader context.
- MEV gas calculator when budgeting for Flashbots lanes.
- Support & SLA if a relay escalation needs human help.
How to read these Flashbots benchmarks
Median inclusion reflects how reliably FRB’s maximal extractable value strategies land when routed through a trusted block builder. Latency shows the round-trip time from node client to relay, and gas-per-tx captures the spend after refunds. Use all three before tweaking budgets.
- Match the inclusion row to your Ops Pulse widget—variance greater than 8 pts means dive into logs.
- Track latency per POP to decide when to rotate block builders or MEV-Boost relays.
- Use gas/tx to explain why private bundles often outperform public PGAs on transaction fee revenue.
What these numbers mean for MEV trading
Flashbots remains the most predictable lane for backruns and protection bundles. FRB’s retry logic keeps inclusion high even when gas spikes, which protects users from toxic MEV and stabilizes transaction ordering for high-value wallets. When latency creeps above 180 ms, the odds of a bundle missing the target block increase dramatically.
Scenario deltas also highlight why structured guardrails beat ad-hoc scripts: budget caps plus relay rotation ensure maximal extractable value does not come at the cost of runaway risk.
Limitations & common pitfalls
- These KPIs assume at least two MEV-Boost relays configured; single-relay setups can skew variance.
- Latency readings exclude public RPC overhead—run the WSS latency test to confirm your region.
- Scenario rows use curated templates; update the dataset whenever you change contract logic or block builder lists.
Always rerun the dataset after new relay releases so long-term performance trends remain trustworthy.
Median inclusion
±4% window · 24h rolling
Avg latency
Frankfurt/Singapore POPs
Gas / tx
Private bundles avoid PGA blowups
Scenario comparison
| Scenario | FRB | Generic bot | Notes |
|---|---|---|---|
| Backrun (ETH/USDT, 2 tx) | 94% | 81% | FRB auto-switches relays after 2 failed slots. |
| Sandwich guard (stable pair) | 89% | 72% | Budget caps + slot pacing reduce reverts. |
| Protection bundle (retail wallet) | 95% | 76% | FRB signs the protection bundle and routes via Protect RPC fallback. |
| Private auction (high congestion) | 88% | 64% | FRB throttles gas escalation to keep ROI positive. |
How the data is produced
Flashbots metrics stem from nightly harness runs. FRB replays bundle templates across multiple regions, tags each attempt with relay, latency, gas settings, and refund status, then stores them in the `/metrics` dataset. We discard any run where a relay outage skews more than 5% from baseline.
- Latency numbers include p50/p95 per region so you can pick the right POP.
- Scenario deltas are relative to a generic bot replay with the same inputs.
- All rows include a `run_id`—reference it in your memo to keep auditors satisfied.
Need to replicate? Follow the Knowledge Base article “Telemetry harness replay” and compare your hashes.
Download raw data
Grab the JSON export and plug it into your Looker dashboards or investor memo.
See it live
Open `/app/dashboard`, pair one node client, and watch the Flashbots gauges update in real time.
Launch dashboardHow to apply the Flashbots metrics
- Use the 92% median inclusion as your baseline—if live dashboards dip below 80%, rotate relays and review logs.
- Map latency medians to your WSS rotation policy; >180 ms should trigger failover.
- Share the scenario table in procurement decks to prove FRB’s guardrails vs generic bots.
Briefing checklist
When presenting Flashbots performance to stakeholders, keep the narrative tight: baseline (92%), current live metric, variance, action taken. Paste this checklist into your Knowledge Base entry so every update feels consistent.
- Include screenshots of Ops Pulse gauges with timestamps.
- List any relay escalations or support tickets you opened.
- State whether numbers came from simulation or live capital.
How to use these Flashbots MEV benchmarks
When you submit a change request or investment memo, embed this Flashbots benchmark snapshot. Stakeholders want to see median inclusion, latency, and the delta between FRB and generic bots.
- Quote the 92% inclusion baseline and note how far your live route deviates.
- Attach scenario rows that match your strategy (backrun, protection, private auction).
- Link to the metrics JSON plus Ops Pulse screenshots so reviewers can recreate the analysis.
Point readers toward the next click
Help teams stay inside ai-frb.com after they study the Flashbots metrics by giving them an explicit set of follow-up links.
- Install guide for desks that want to reproduce these Flashbots runs on new machines.
- Pricing overview so procurement can pair the benchmarks with the right subscription.
- Docs quick start to standardize verification, SHA-256 checks, and node pairing.
- Support & SLA when relays or block builders need escalation.
FAQ
What inclusion rates can I expect with FRB + Flashbots?
Our nightly simulations show a 92% median inclusion (±4%). Private relay rotation and retry logic keep the window tight even during gas spikes.
How do you measure these KPIs?
We replay the same bundles across FRB builds and capture latency/inclusion via the dashboard telemetry harness. Raw JSON is available on /metrics.
Can I plug these numbers into my client pitch?
Yes. Download the JSON export and cite the dataset in your memo. Each row includes timestamped measurements.
Put these Flashbots MEV benchmarks to work: compare tooling on the MEV Bot Comparison, brief teammates via the Flashbots tutorial, and install FRB wherever you need consistent telemetry.
Close the loop by downloading the signed installer, sharing the MEV 101 hub or MEV strategies guide with stakeholders, and routing budgets toward Ethereum MEV or other chain landers once the Flashbots data gives you confidence.