Risk & Ethics Policy
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 (especially on Solana Pump.fun) move fast; quotes may slip before inclusion.
- Inclusion uncertainty: Private bundles (Flashbots or Jito) 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/Jito) where possible to reduce PGA waste and sandwich attacks.
- Blocklists: exclude honeypots, blacklisted routers, or Solana tokens failing mint/freeze authority simulation.
- Simulation: dry-run before live; enable canary size on new routes.
Ethics of Extraction
FRB is designed to promote neutral, efficient, and transparent markets. We strictly oppose:
- DDoS & Spam: We do not support spamming RPCs. The agent uses highly optimized, low-frequency bundles.
- Reorgs: We do not provide tooling for time-bandit attacks or chain reorganization.
- Malicious Contracts: The software is built for atomic arbitrage and liquidation, not exploits.
Anti-Sandwich Protection
The public mempool is a "Dark Forest" where predators wait to sandwich your trades. FRB protects you by default:
- Private Bundles: Transactions are sent directly to block builders (Flashbots, BeaverBuild, Jito Block Engine), bypassing the public mempool entirely.
- Atomic Execution: If your trade creates a loss (due to slippage or attack), the bundle reverts, costing you nothing but simulation gas or base compute fee (Solana).
- Simulation Mode: Dry-run every strategy against mainnet state to detect sandwich vectors before deployment.
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.