How FRB approaches chain-specific routing
Every chain behaves differently. Ethereum offers the deepest liquidity and most mature relay ecosystem, whereas BNB Chain rewards aggressive token hygiene, and Base focuses on tight fee control. This hub consolidates the playbooks our desks use so you can evaluate which venues deserve capital and how to bootstrap safely.
Start with the big idea: private bundles should be your default lane. Public PGAs are useful for canaries or parity checks, but they introduce noise and leak strategies. FRB’s refund guard, Ops Pulse telemetry, and Latency Test tool make it easier to adapt without improvising settings under pressure.
Private relays vs public PGAs
Private relays let you send sealed bundles directly to searcher-friendly builders. You get predictable inclusion probabilities, better refund behavior, and less competition. Public PGAs remain a fallback—think of them as an escape hatch when relays degrade or when you only need to test a hypothesis with tiny size.
- Define exactly when FRB is allowed to fall back to public (e.g., relay outage).
- Limit fallback size to ≤10% of the session cap and log each attempt.
- Review Ops Pulse charts weekly to see whether public attempts still add value.
Per-chain snapshots
Use the summaries below to decide where to deploy first, then dive into the individual guides for deeper routing, latency, and compliance notes.
Ethereum
Deepest liquidity, largest number of relays, and strictest scrutiny. Baseline with the Ethereum guide before cloning routes elsewhere. Focus on Flashbots integration, per-pair budgets, and comprehensive logging.
BNB Chain
High throughput with uneven router quality. Stick to audited allowlists, enforce liquidity minimums, and record every refund reason to stay ahead of exploit waves.
Polygon
Sensitive to endpoint jitter. Follow the Polygon guide for best practices on WSS rotation and gas multipliers when baseFee swings.
Base
Friendly fee profile with Coinbase sequencer nuances. The Base playbook covers how to stage routes in simulation, log Ops Pulse metrics, and scale after clean sessions.
Arbitrum
Fast rollup windows with occasional throttling. See Arbitrum MEV for latency windows, recommended routing, and how to measure inclusion deltas during sequencer bursts.
Optimism
Fee-aware chain that rewards patient scaling. Read the Optimism guide for canary promotion steps, refund governance, and documentation habits.
Ethereum MEV
Endpoints, tips & reliable execution.
BNB Chain MEV Agent
Routing guardrails, liquidity checks, and refund-safe playbook.
Best MEV Bot Comparison 2026
Compare FRB vs other bots on inclusion, relay coverage, pricing, and guardrails.
BNB Chain MEV
Endpoints, tips & reliable execution.
Polygon MEV
Endpoints, tips & reliable execution.
Base MEV
Endpoints, tips & reliable execution.
Arbitrum MEV
Endpoints, tips & reliable execution.
Optimism MEV
Endpoints, tips & reliable execution.
Cross-chain readiness checklist
Treat this hub as your pre-flight binder. Before deploying a route on any chain:
- Benchmark endpoints using Latency Test and store the results.
- Review the chain-specific MEV guide linked above; copy over guardrails.
- Simulate for at least 24 hours, compare inclusion to the metrics page, and document anomalies.
- Enable refund guard, Ops Pulse alerts, and escalation paths defined on /support.
- Share the entire packet (hashes, metrics, runbook) with your compliance lead.
Once you run through this cycle a few times, paste the completed checklists into Knowledge Baseso future launches are even faster.
How to prioritize chains
Rank candidates by liquidity depth, relay quality, and your internal appetite for experimentation. A common sequence is Ethereum → Base → BNB/Arbitrum → Polygon → Optimism. Keep a copy of your metrics dashboard handy so stakeholders can see inclusion and refund trends per venue.
If a chain shows repeated anomalies—variance, exploit risk, or compliance blockers—archive the checklist, pause size, and escalate via support. It is better to redeploy capital to a known-good venue than to chase short-term yield on shaky infrastructure.
FAQ
Can we deploy on multiple chains simultaneously? Yes, provided each has its own checklist and monitoring. FRB lets you tag node clients per chain so on-call engineers know which workstation handles which routes.
How often should we refresh these notes? Update them every time you rotate endpoints, change refund policy, or notice inclusion drifts. Treat this hub like a living runbook.
Where do we store compliance artifacts? Use the compliance brief plus entries in Knowledge Base. Attach links to each chain guide so reviewers have context.