FRB is a toolkit for MEV workflows (e.g., backrun, sandwich, arbitrage). These strategies are experimental and high-risk. Losses can occur quickly due to market microstructure, gas dynamics, and inclusion uncertainty.
Material risks
- Market & slippage risk: MEME/illiquid pairs move fast; quotes may slip before inclusion.
- Inclusion uncertainty: Private bundles may fail to land; public gas auctions can be outbid.
- Reorgs & variance: Short-range reorgs can invalidate assumed state; MEV profits are volatile.
- RPC/infra outages: Latency spikes, dropped websockets, or rate-limits can break pipelines.
- Smart-contract risk: Interacting with unverified or malicious contracts can lead to permanent loss.
- Compliance risk: MEV legality and market rules vary by jurisdiction and venue—you must assess applicability.
Controls in FRB (you must configure)
- Budget guards: per-trade gas cap, session limits, and daily spend ceilings.
- Slippage & routing: max slippage per route; enforce liquidity & depth checks.
- Execution path: prefer private bundles (Flashbots) where possible to reduce PGA waste.
- Blocklists: exclude honeypots, blacklisted routers, or tokens failing simulation.
- Simulation: dry-run before live; enable canary size on new routes.
No guarantees
Historical or simulated performance does not guarantee future results. You are solely responsible for due diligence, configuration, and compliance with applicable laws and exchange policies.
Operational responsibilities
- Maintain your own keys and wallets; FRB never requests custody.
- Log every configuration change (slippage, budgets, endpoints) in your internal KB.
- Run post-mortems for any significant loss and share takeaways with your stakeholders.
Contact support if you need help triaging an incident; provide timestamps, hashes, and logs.