FRB FAQ

FRB FAQ guides MEV traders and ops teams through setup and support.

This FRB FAQ highlights how the FRB MEV agent works as a MEV trading assistant, what licensing looks like, and the install/download steps that keep every Windows rollout verifiable.

Start with the verified FRB download center, walk through the Docs Quick Start, and log your findings in the Knowledge Base so the whole desk shares the same playbook before scaling budget caps.

Procurement leads can review plan details inside the pricing overview, while technical owners track inclusion performance on the Flashbots metrics dashboard and compare cross-chain behavior with the BNB benchmarks as they digest this FAQ.

Regulatory context for this frequently asked questions page

MEV desks often route this FRB FAQ to compliance and finance teams before signing off on installs. Use the prompts below to keep your notes aligned with those expectations without leaving the FRB ecosystem.

Flag which answers impact treasury, compliance, or security so the correct team follows up.
Include the business day timestamp, wallets involved, and any live-capital assumptions when you submit questions.
Reference support, telemetry, and pricing entries so the FAQ doubles as documentation for future audits.

Safe start checklist

Before any live route, confirm the following:

Install the signed build and verify the SHA‑256 hash.
Pair the device via PIN and confirm it under Node Clients.
Add trusted RPC/WSS endpoints and check latency.
Run Simulation with canary-size trades until inclusion is consistent.
Set slippage, gas, and daily budget caps before enabling Live.

Quick Start Guide Risk Disclosure

Ops & execution

What is FRB?

FRB is an AI-assisted MEV agent for Windows that helps you orchestrate private bundles, budget guardrails, and telemetry across Ethereum, BNB, Polygon, Base, Arbitrum, and Optimism. Think of it as a safer alternative to unsigned scripts—complete with signed releases, refund policy, and SLA.

How do I structure the rollout?

Follow the Quick Start: Day 0 install + verification, Day 1 simulation only, Day 2 canary size, then scale after you log inclusion vs refund stats. Capture Ops Pulse screenshots at each stage so stakeholders can audit the journey.

Are profits guaranteed?

No. MEV is adversarial. We provide tooling, not returns. Always assume trades can fail, set per-route caps, and lean on the Risk Disclosure before allocating capital.

Do I need Flashbots?

Private bundles like Flashbots give better privacy and refund behavior. FRB supports them out of the box, plus public PGAs for canaries. Review Flashbots vs Public PGA to decide when to toggle each lane.

Security & telemetry

How does FRB keep my keys safe?

FRB never asks for private keys or seed phrases. You connect via your own wallet, pair node clients with a PIN, and can even run inside a VM. See Security & Trust for verification steps.

What telemetry is collected?

Only health metrics required for Ops Pulse (latency, inclusion, refund counts) plus anonymized installer hashes. Review the Telemetry page for retention windows and opt-out flags.

How do I report a vulnerability?

Email /vulnerability or security@ai-frb.com with encrypted details. We respond within 24 hours and coordinate disclosure timelines.

Does FRB work on all pairs?

No. You must configure filters (routers, liquidity thresholds, blocked tokens) per chain. Always run simulation for at least 24 hours, then graduate to canary size. Cross-reference the relevant chain guide (e.g., Arbitrum MEV).

What risk guards exist?

Every plan includes slippage caps, per-trade gas limits, session budgets, refund guard, and honeypot blocklists. Enterprise adds admin roles and audit logs so ops teams can prove who changed what.

What about compliance?

You remain responsible for local laws. We publish Compliance notes, refund policy, telemetry disclosures, and escalation contacts to support your reviews.

How do I start safely?

Benchmark WSS endpoints and document SHA-256 verification.
Use Simulation mode and the Quick Start guide.
Only move to live size after Ops Pulse shows stable inclusion and the Safe Start checklist is complete.

Licensing & billing

How are plans billed?

Starter is free; Pro is subscription-based (monthly or annual), and Enterprise is custom. See /pricing for SKU details and contact support for quotes.

Can I pause or cancel?

Yes. Use the billing area in `/app` or email support. Access continues until the period ends and invoices remain in your portal for audit purposes.

Do you offer refunds?

Only for billing errors per the public refund policy. File a ticket within 48 hours with invoice numbers and supporting evidence.

Telemetry & support

How long do you retain telemetry?

Default retention is 30 days for Ops Pulse snapshots and 90 days for aggregate metrics. Enterprise can negotiate shorter windows; see Telemetry for flags.

What goes into a good support ticket?

Include agent version, relay/endpoint, timestamps with time zones, and severity. Attach logs/screenshots so the on-call engineer can reproduce faster.

Is there a status page?

Yes. Bookmark /status to monitor relay health and planned maintenance. Pair it with Ops Pulse alerts for full coverage.

Troubleshooting

Install succeeded but no telemetry?

Ensure the Windows service is running, VPN is not blocking outbound HTTPS, and the firewall allows the pairing domain listed in the Quick Start. Re-run pairing to generate a fresh PIN.

Bundles stopped landing after update?

Roll back to simulation, compare release notes, and share tx hashes with support. Often the fix is updating guardrails or rotating relays per the relevant chain hub.

Where can I ask more questions?

Open a ticket via Support/SLA. Provide logs, hashes, and severity so we can help quickly.