Binary Provenance & Trust
Every FRB release is cryptographically signed and hash-verified. We maintain an immutable record of checksums to ensure your trading environment remains untampered.
How to verify hashes
Open PowerShell and run the command below to compute your local file hash. Compare the result with the official values listed below.
Get-FileHash .\frb-agent.exe -Algorithm SHA256Integrity Validation
Every official build publishes a SHA-256 hash. Run Get-FileHash on the installer and confirm it matches the value listed for that release before running it.
Latest Builds
1 Releases Cachedv8.6
Latest"Hardened transport security, obfuscation-resistant pairing protocol, and a new branded installer."
590286d2d6632931b2610c915fd5d90bec2d436f82491d40267b6ed2e01df33cHistorical Archive Access
If you operate air-gapped networks or require retired versions for compliance testing, contact our support desk for signature chains.
Contact Security DeskRelease management tips
- Store hashes + download timestamp in your internal change ticket.
- Require two-person review before promoting a new build to production.
- Keep the previous installer handy for quick rollback if you discover an issue.
- Document which relays or regions each build targets so you can roll forward with confidence.
Need older builds or offline hashes? Contact support and reference this page.