Threat modelling
A living threat model closed out before every release.
M5Liquid is threat-modelled from the first commit and verified with evidence, not slogans. Here is how we protect systems, keys, data and assets.
Security pillars
A living threat model closed out before every release.
Development, test, staging and production fully separated.
Hardware-backed multi-factor access and scoped credentials.
Keys and secrets never live in code, documents or chat.
Software bill of materials, licence tracking and scanning.
Playbooks, backup and restore and regular drills.
KeyMorph
KeyMorph maintains an algorithm registry and key epochs so the network can migrate cryptography in reviewed stages, running classical and post-quantum signatures side by side before any switch.
ProofLedger
Execution, configuration, benchmark and operational events produce signed, tamper-evident receipts that authorized parties can verify independently.
Independent assurance
M5Liquid is reviewed continuously by independent specialists across protocol, application, cryptography, risk models and infrastructure.
Responsible disclosure is welcomed and rewarded through the M5Liquid bug bounty program.

Asset safeguards
Customer assets, liquidity capital, operating capital and protection funds are kept legally and operationally separate. Custody uses approved providers with MPC or HSM key management, and trading and withdrawal authority are strictly separated.
Continue exploring
Open your M5Liquid account in under a minute, or talk to our team about institutional onboarding, liquidity partnerships and integrations.