How FRB orchestrates execution
Execution is more than “send bundle, hope for the best.” FRB keeps a live state machine of every relay, PGA lane, and refund guard so you know exactly where capital flows. Use this hub as a systems guide: private bundles, public auctions, telemetry, and rollback procedures belong in one place so the desk operates predictably.
Private bundle workflow
Private bundles are the default lane for FRB. They keep payloads sealed, respect refund policies, and provide deterministic inclusion windows. A standard workflow looks like:
- Choose relays with clean health metrics from Relay Status.
- Run the Latency Test and tag endpoints by region.
- Feed bundles through FRB’s policy engine so slippage, gas, and session budgets stay in sync.
- Stream results into Ops Pulse + telemetry for day-two audits.
If anything drifts—variance spikes, refund ratio climbs—document the cause and pause gracefully. The Flashbots vs Public PGA guide outlines how to choose new relays or escalate to support.
Public PGA fallback
Public PGAs still matter. They let you verify pricing, send tiny canary trades, and keep routes alive when relays degrade. But they must be fenced in:
- Size < 10% of your private bundle allocation unless approved.
- Attach extra logging (envelope, rejection reason, broker) for every attempt.
- Expire public attempts after a handful of blocks—never chase indefinitely.
When FRB flips to public mode, the UI surfaces a banner, and Ops Pulse alerts your on-call operator. Close the loop by noting the event in the Knowledge Base.
Telemetry-first culture
Reliable execution depends on measurement. Export metrics into Prometheus, Datadog, or your preferred stack, but also keep the human-readable summaries: Ops Pulse snapshots, refund reports, and the metrics dashboard form the backbone of every retro. When you debrief a session, ask: Which chains performed best? Did public fallbacks add or subtract value? Were there budget overruns?
Chain-focused guidance
Each chain surfaces unique quirks—Arbitrum throttling, Base sequencer bursts, BNB liquidity hygiene. Link this hub to the chain guides so your team can jump from high-level concepts to actionable checklists:
- Ethereum MEV for Flashbots-first routing.
- Base MEV for Coinbase sequencer nuances.
- BNB Chain MEV for router hygiene and tiering.
- Arbitrum MEV for bursty latency management.
Encourage teammates to add notes after every incident—execution quality improves fastest when knowledge is shared.
Private bundles
How private MEV execution works.
Flashbots vs Public PGA
Picking the right path per scenario.
Relay Status
Quick reachability checks.
WSS Latency Test
Benchmark endpoints in browser.
Reduce gas waste
Cost‑effective execution patterns.
Execution scorecard
Evaluate your routing setup monthly. Score yourself 1–5 on relays, monitoring, risk guardrails, and documentation. Anything under 4 deserves attention. For example, if you lack an on-call rota for Ops Pulse alerts, schedule one.
Questions to ask
- Can we prove which relay handled each bundle last week?
- How fast do we rotate when latency spikes? Is it automated?
- Does every public PGA attempt include an audit trail?
- Are refunds reconciled daily with finance/compliance?
Answer honestly, record gaps, and link follow-up tasks to your sprint board.
Incident response flow
When a route misbehaves, follow a consistent flow: capture telemetry, snapshot config, pause via FRB UI, and escalate through support if needed. This keeps downtime short and produces proof for compliance.
- Log the incident in Knowledge Base with timestamps.
- Attach Ops Pulse graphs plus relevant metrics screenshots.
- Note which relay or PGA lane was active so we can correlate with relay status.
FAQ
Should we ever skip private bundles? Only when relays are down or you need price discovery. Document the reason and revert as soon as conditions normalize.
How do we keep configs in sync? Version-control FRB policies, mirror them in your internal repo, and link to this hub so new teammates understand the intent behind every setting.
Can FRB integrate with our monitoring? Yes. Use telemetry exports to push data into Prometheus, Datadog, or any stack you prefer. The built-in dashboards still help for quick human review.