FRB Quick Start
FRB quick start walks you through four moves from download to dashboard.
Keep this FRB quick start checklist next to the Safe start guide. Once every step is completed, click “Launch dashboard” to pair your first node client and finish the FRB MEV agent onboarding.
Download the signed installer
Grab the latest Windows ISO/EXE from the Download page and note the SHA‑256 + file size.
You know exactly which artifact will be verified next.
View resourceVerify SHA‑256 & Authenticode
Use CertUtil or Get-FileHash then Get-AuthenticodeSignature. Publisher must read FRB Labs Ltd.
Binary integrity confirmed before execution.
View resourceMount ISO, copy to C:\FRB, run in Simulation
Mount to a drive letter, copy contents, launch MultiChainFrontAgent.exe, choose Simulation.
Agent runs in a sandbox with zero live exposure.
View resourcePair with /app and follow Safe start
Open `/app/login`, connect wallet, add bot via 6-char PIN, then apply the Safe start checklist.
Node client visible in dashboard with guardrails set.
View resourceBest practices checklist
- Log hashes + screenshots in your internal ticket before installing.
- Use Simulation for at least 24 hours; capture Ops Pulse metrics.
- Promote to canary size with per-route caps documented in /kb.
- Review risk disclosures with the team.
- Share the Safe start FAQ with anyone touching production.
Treat this list like a pre-flight check. If a step fails, stop and re-evaluate before moving on.
Video walkthrough
Checksum validation, Windows SmartScreen bypass, and pairing the bot with `/app`.
Prerequisites
Environment checklist
Run through this grid before touching live capital. Store the evidence in your internal ticket.
- Windows 10/11 64-bit
- Latest updates installed
- 8 GB RAM + SSD storage
- Two WSS providers whitelisted
- NTP/clock sync verified
- Firewall allows outbound HTTPS/WSS
- Hashes logged in ticket
- Refund policy acknowledged
- Telemetry opt-in/out documented
Simulation → Production timeline
| Day | Focus | Artifacts to store |
|---|---|---|
| Day 0 | Install, verify SHA-256, pair first node | Installer hash log, Authenticode screenshot, ticket link |
| Day 1 | Simulation only, collect Ops Pulse metrics | Inclusion vs refund chart, WSS baseline table |
| Day 2 | Canary size (≤10%), refine guardrails | Signed approval, updated budget sheet, latency snapshots |
| Day 3+ | Scale cautiously, prep postmortem notes | Weekly KPI export, support ticket IDs, KB entry links |
Artifacts to store for audits
- Installer hash + Authenticode output (attach to ticket or Confluence page).
- Ops Pulse exports showing simulation and canary phases with timestamps.
- Endpoint benchmark CSV plus the decision log describing any rotations.
- Refund guard configuration screenshot and the rationale for thresholds.
- Support ticket IDs (if any) and corresponding resolutions or KB updates.
Auditors love narrative + evidence. Capture both while the context is fresh.
When to escalate
Pause the rollout and contact support if:
- SHA-256 or signature mismatches after two downloads.
- Simulation emits repeated relay connection errors even after rotating WSS endpoints.
- Refund guard halts canary mode more than twice in a 24-hour window.
- Telemetry shows unrecognized devices/wallets pairing with your workspace.
Include logs, hashes, hardware IDs, and severity when escalating so on-call engineers can reproduce quickly.
Next steps after the FRB quick start
Keep momentum by lining up procurement, training, and monitoring resources while the agent runs its first profitable opportunities.