Benchmarks · Flashbots · Polygon
FRB MEV benchmarks across simulated routes
Every dashboard build ships with the same telemetry harness. We run nightly simulations across Ethereum, Polygon, and BNB to keep tabs on inclusion, latency, and gas overhead. These MEV benchmarks across chains show how FRB helps protect users from toxic MEV while keeping pending transactions predictable—use the public snapshot whenever someone asks “why FRB?”.
Linkable summary
Why this dataset matters
The FRB MEV benchmarks page publishes reproducible inclusion, latency, and gas-per-transaction metrics for Flashbots, Polygon, and BNB along with raw JSON downloads so researchers can cite hard numbers when linking to ai-frb.com.
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
These metrics show how an FRB MEV trading assistant compares to generic bots: transaction ordering, MEV extraction rate, and refund behavior. Use the median plus variance columns to decide whether a route is safe to scale. If latency or inclusion slips, jump into Ops Pulse and correlate the dip with block builder incidents or mempool congestion.
- “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.
- Dataset schema (below) links to raw JSON so analysts can recreate the comparison.
Flashbots inclusion (median)
vs 78.4% for generic bots
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) | 92.1% | 78.4% | Simulated bundles with identical gas caps, Nov 2025 window. |
| Polygon private bundle inclusion | 87.3% | 69.8% | FRB routes auto-rotate WSS endpoints and retry late slots. |
| Average latency (node → relay) | 148 ms | 226 ms | Node clients auto-pin to healthiest WSS, fallback on jitter >60 ms. |
| Gas / tx (weighted avg.) | $1.84 | $2.73 | Flashbots-only execution avoids public PGA bidding wars. |
| Day-one PnL ramp per $100 funded | $14.20 | $6.70 | Based on sandboxed contracts with identical budgets and risk guards. |
Relay & builder benchmarks
These are the inputs we feed into the dashboard “Health” gauges.
Default path for Ethereum backruns and protection routes.
Best results when paired with FRB latency monitor + compact mode.
Still beta—FRB throttles bundle submissions when congestion spikes.
Great for collaborative order-flow; FRB tags these as “research” routes.
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 stems from a repeatable telemetry harness. We replay identical bundles on multiple FRB releases, log relay selected, latency, refund behavior, and whether the attempt was simulation or live. Runs that deviate beyond tolerance trigger an investigation and a public note on/releases.
- Latency samples include p50/p95 readings from Frankfurt, Singapore, and Virginia POPs.
- Gas-per-tx figures already incorporate refunded slots so finance sees true cost.
- Dataset rows ship with timestamps and hash references so you can rerun the job internally.
Want to validate? Pull the JSON, match the run ID to your own telemetry export, and flag any drift greater than 5%—we’ll help reproduce it.
Download the raw dataset
Need to plug these figures into your own pitch deck? Grab the JSON export straight from the telemetry job.
See 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.
- Quote the inclusion/latency table in pitch decks or compliance memos.
- Link to specific chain detail pages (Polygon, BNB, Flashbots) when you need to drill down.
- Export the dataset JSON for quants so they can replicate the results externally.
How to apply these numbers
- Use inclusion deltas when pitching FRB vs legacy bots—cite the dataset and link to this page.
- Feed latency targets into your WSS rotation policy; anything above the published medians should trigger an alert.
- 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 the JSON export, paste a screenshot of this page, and include your own commentary so reviewers see both the data and the narrative.
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.