Benchmarks · Flashbots · Polygon
MEV benchmark measurement methodology
Use this framework to measure inclusion, latency, fees, and net outcomes across Ethereum, Polygon, and BNB without treating simulations or illustrative UI as production evidence.
Linkable summary
Why the method matters
A valid comparison pins inputs and environment, separates relay acceptance from on-chain inclusion, and retains timestamped raw evidence plus limitations.
For a neutral comparison against Flashbots and Blocknative data, share the Ecosystem research brief along with these tables.
Need the freshest snapshot? Reload the live MEV benchmarks feed before you export the numbers to your deck.
Quick links for telemetry deep-dives
Jump straight into the chain or tooling page that matches the question you are answering. Each resource below keeps stakeholders inside the FRB site so your internal links reinforce authority.
Chain-specific benchmarks
- Flashbots relay metrics for Ethereum bundle coverage.
- Polygon telemetry snapshot when latency drives the narrative.
- BNB private relay stats to brief desks deploying on BSC.
Execution aides
- Chain MEV hub for playbooks that pair with these metrics.
- WSS latency test when you need to validate endpoint health.
- MEV strategies guide to translate numbers into actions.
How to read these MEV benchmarks
The tables define what to measure, not a universal FRB result. Use identical inputs and report medians, tail latency, fees, failures, and final chain status before deciding whether to scale.
- "FRB (AI Agent)" columns reflect policy-safe guard rails plus private bundle routing.
- "Generic bots" simulate unguarded scripts so you can show stakeholders the opportunity cost.
- Retain a local raw export and run ID so analysts can recreate the comparison.
Flashbots inclusion (median)
Measure final inclusion per environment
Polygon relay latency
FRB auto-pins to healthiest WSS endpoints
Gas / tx (weighted)
Private bundles avoid PGA bidding wars
Headline KPIs vs generic bots
| Metric | FRB (AI Agent) | Generic bots | Notes |
|---|---|---|---|
| Median inclusion rate (Flashbots/Mainnet) | Measure locally | Use the same sample | Record relay, builder, target block, fee cap, sample size, and final inclusion. |
| Polygon private bundle inclusion | Measure locally | Use the same sample | Run identical submissions per endpoint and report confirmed inclusion separately from relay acceptance. |
| Latency (node → relay) | Record p50/p95 | Record p50/p95 | Pin region, node client, endpoint, transport, and test window before comparing. |
| Gas / confirmed transaction | Calculate per run | Calculate per run | Include priority fees, failed attempts, refunds, and native-token/USD conversion source. |
| Net outcome | No preset return | No preset return | Report realized outcomes after all fees; simulations are not production returns. |
Relay & builder benchmarks
These are the inputs we feed into the dashboard "Health" gauges.
Record relay acceptance and on-chain inclusion as separate events.
Document endpoint, region, builder coverage, and fallback behavior.
Document the active provider and congestion conditions for every run.
Label experimental paths and do not combine them with production samples.
Related resources
Keep these MEV benchmarks anchored with chain-specific telemetry and execution playbooks when briefing stakeholders.
- Flashbots MEV benchmarks for Ethereum relay comparisons.
- Polygon MEV benchmarks to track latency and bundling behavior.
- BNB MEV benchmarks covering Eden, BSC Protect, and SUAVE lanes.
- Pair the numbers with the Chain MEV hub for execution strategy context.
Methodology & data hygiene
Every benchmark should come from a repeatable harness. Replay identical inputs, record release, environment, relay, latency, fees, simulation/live status, target block, and final outcome. Document changes on /releases.
- Record p50/p95 latency by region, endpoint, transport, and test window.
- Include priority fees, failed attempts, refunds, and conversion source in cost figures.
- Store timestamps, run IDs, release version, and raw log hashes for internal reruns.
Validate by repeating the same test and explaining material drift instead of relying on a published universal baseline.
Run a local measurement
Start with the WSS latency test and keep your local raw export with the analysis.
Open latency testSee it in the dashboard
Metrics refresh live inside `/app/dashboard`. Connect your wallet, pair one node client, and watch the gauges update in real time.
Launch dashboardHow to use these MEV benchmarks in your workflow
Before a route graduates from simulation to production, attach the latest MEV benchmarks (Flashbots, Polygon, BNB) to your change request. Show how your FRB MEV bot compares to generic bots, highlight the pending transactions you modeled, and document the refund guard rails you expect.
- Use only your measured inclusion and latency results in pitch decks or compliance memos.
- Link to specific chain detail pages (Polygon, BNB, Flashbots) when you need to drill down.
- Export your local dataset for quants so they can replicate the results.
How to apply these numbers
- Use inclusion deltas only when both tools ran with identical inputs and environment.
- Feed your measured p95 into WSS rotation policy and document the alert threshold.
- Cross-reference per-chain benchmarks (e.g., BNB metrics, Flashbots metrics) when tuning gas caps.
Remember: these are simulated yet reproducible snapshots. Always rerun on your own stack before committing changes.
For board decks, attach your raw export, method, sample size, dates, limitations, and reviewer-approved commentary.
Route traffic toward deeper internal docs
Readers skimming benchmarks often need a next click. Surface the right FRB destinations so they stay on ai-frb.com longer and keep the story cohesive.
- Support & SLA when someone spots an anomaly and wants human confirmation.
- FRB Knowledge Base entries that walk through reproducing these MEV benchmarks on your own stack.
- Docs quick start so a fresh desk can install the agent that powers this telemetry.
- Pricing overview to convert interest into a funded deployment immediately.
Need to act on these MEV benchmarks? Share them with stakeholders via the MEV Bot Comparison, rerun the MEV Gas Calculator, and install FRB on additional desks so every playbook benefits from the same telemetry.
Ready to turn MEV benchmarks across chains into action? Download FRB, refresh your foundation in the MEV 101 hub, and share the MEV strategies guide so every stakeholder understands how you protect users from toxic MEV.
For deeper drill-downs, pivot into the chain landers: Ethereum MEV, Polygon MEV, and BNB Chain MEV so you always match the benchmarks to the route you are about to launch.