Protecting member funds and data is not a feature we balance against other priorities. It is the unconditional foundation upon which every system, policy, and decision at Octagon is built.
In fintech, the most common security failures are not caused by technically sophisticated attacks. They are caused by organisations that made deliberate trade-offs — choosing convenience over security controls, deferring fixes to ship features faster, or trusting their security posture to a set of checklists rather than genuine, adversarial thinking about how a determined attacker would approach their systems.
At Octagon, we do not make security trade-offs. Our security team operates with a full veto over any product or operational change that would weaken a control — and that veto has never been overridden. If something improves user experience at the cost of security, we do not ship it. We find a way to improve experience while maintaining the control, or we ship neither. This is not a policy we enforce reluctantly — it is a conviction the entire leadership team holds.
The record speaks for itself: since Octagon launched in 2021 and processed over $2.1B in cumulative trading volume, we have had zero member fund losses attributable to security failure. We intend to keep it that way indefinitely.
Octagon's security architecture is built on the principle of defence-in-depth: multiple independent security layers, each designed to stop an attack even if every layer above it has been compromised. This means that no single technical failure, no single insider threat, and no single operational error should be capable of resulting in member fund loss.
Our infrastructure is distributed across geographically separated data centres with no single point of failure. Hot wallet exposure — the portion of user funds kept online for operational liquidity — is kept at the absolute minimum required to process normal withdrawal volumes. The remainder is in offline cold storage, physically disconnected from any network.
Security Stack (Top to Bottom)
Member funds are protected at multiple independent layers. A failure at any one layer does not create a path to fund loss — which is the entire point of the architecture.
Every withdrawal from Octagon's cold storage requires multiple cryptographic signatures from key holders in different physical locations. No single person — including any member of the executive team — holds enough keys to authorise a withdrawal unilaterally. This design means that even a complete compromise of any individual's credentials cannot result in unauthorised fund movement.
95%+ of all member funds are held in hardware wallets that have never been and will never be connected to the internet. These wallets are stored in physically secured, access-controlled facilities. Accessing them requires multiple human authorisations, physical presence, and a documented operational procedure reviewed by the security team before any transaction is executed.
Every withdrawal request submitted by a member is reviewed by a human administrator before funds are released. This review checks the requested amount against balance, verifies the destination address against known-good wallet patterns, and flags any requests that deviate from the member's historical withdrawal behaviour for additional verification.
Our Security Operations Centre runs custom monitoring dashboards that track all fund movements, API activity, and system metrics in real time. Automated alerts fire immediately on any anomaly — unusual withdrawal volumes, authentication failures, or network behaviour that deviates from baseline. Our team is on call 24/7 to investigate and respond.
Member funds are held in accounts that are fully segregated from Octagon's operational capital. This means that even in a worst-case scenario where Octagon faced business-level financial difficulties, member funds would not be commingled with company assets or exposed to operational creditors.
Octagon maintains cybersecurity insurance coverage on critical platform infrastructure. While our security programme is designed to prevent any incident that would trigger a claim, this coverage provides an additional backstop protection for members in the event of an unforeseen circumstance beyond the platform's control.
Octagon's security posture is not self-certified. We commission independent third-party security audits on an annual basis, with scope covering our web application, API infrastructure, smart contract code, cold storage procedures, and internal access controls. Findings from each audit are reviewed by the executive team, remediated according to a risk-prioritised plan, and tracked to closure before the next audit cycle begins.
In addition to annual comprehensive audits, we conduct quarterly penetration testing exercises using red team methodology — where external security professionals are engaged to actively attempt to breach our defences using the same techniques a real attacker would use. This continuous testing regime ensures our controls remain effective as the threat landscape evolves.
Octagon's infrastructure security is our responsibility — and we take it seriously. But your account's personal security depends on the steps you take to protect your login credentials. The most common account compromises are not technical attacks on our systems — they are phishing attacks and credential theft that exploit weak or reused passwords. Here is how to protect yourself.
Security researchers who identify vulnerabilities in Octagon's systems are asked to report them privately to our security team before any public disclosure. We take all reports seriously, acknowledge receipt within 24 hours, investigate thoroughly, and provide recognition to researchers who disclose responsibly. We do not pursue legal action against security researchers acting in good faith within the scope of our disclosure policy.
Report a Vulnerability