Frameworks
- NIST AI RMF – risk identification and controls.
- Operational guidelines for responsible use of MEV‑related tooling.
Allowed use
Users are responsible for complying with applicable laws and exchange/network policies. We provide simulation and guardrails to reduce risk.
Due diligence checklist
- Review Security & signing plus release hashes.
- Download the refund policy and escalation contacts.
- Confirm telemetry retention explained on /telemetry.
- Log your safe-start procedure using Quickstart + Knowledge Base.
How we support reviews
Need enterprise paperwork? Contact support:
- Signed statements on refund, data handling, and incident response.
- References to applicable frameworks (NIST AI RMF, SOC 2 inspired controls).
- Sample runbooks covering simulation → production promotion.
We do not custody funds and do not operate as an exchange. Users remain responsible for protocol-specific compliance.
Internal controls we recommend
Even though FRB provides tooling, desks should implement their own controls:
- Dual-approval for moving from simulation to live capital.
- Weekly review of Ops Pulse anomalies with compliance sign-off.
- Version pinning: record the exact FRB build hash in every change ticket.
- Telemetry retention policy mirrored with your firm's privacy requirements.
These habits align with NIST, SOC 2, and internal audit frameworks and make external reviews painless.
Sample compliance memo structure
- Scope: summarize the strategy, chains, and wallets involved.
- Controls: reference guardrails (slippage, budgets, refunds) with screenshots.
- Monitoring: link to Ops Pulse dashboards and alerting policies.
- Incidents: describe escalation paths and timelines (who responds within which SLA).
- Artifacts: attach hashes from /releases, telemetry notes, and WSS benchmarks.
Store the memo in your GRC or Notion workspace so auditors can trace every production change.
FAQs
Do you provide DPAs or vendor security questionnaires?
Yes. Email support with your template; we reference this page plus the Security, Telemetry, and Refund sections.
How are data requests handled?
Telemetry data is anonymized and retained 30 days. Submit deletion/export requests through Support and include legal justification.
What about sanctions screening?
FRB does not intermediate transactions. Users must ensure wallets and routes comply with their jurisdiction's sanctions lists.