chain · quantum risk
Flow Cryptography & Quantum Risk Profile
Verdict
Profile view: Flow is not quantum-proof while accounts and node operators rely on classical signatures. Consumer app scale concentrates custody and account key risk.
Overview
This is the Wave 7e network/profile page for Flow (l1).
Flow powers consumer crypto apps and NFTs. Account model supports multi-key weights—excellent ops, classical algorithms unless upgraded.
Studios and marketplaces should inventory hot wallets and admin keys.
Verdict hub: /is-quantum-proof/flow. Asset framing: /crypto/flow.
Cryptographic profile
- Signatures: Flow account keys / signature algorithms as configured (verify), Node operator keys
- Hash: Flow transaction hashing
- Public-key exposure: Multi-key accounts possible; still classical public-key classes in common configs.
- Verify Flow signature schemes from current docs.
What breaks
- Classical signatures authorizing FLOW value under Shor-class adversaries once public keys are known
- Custodial hot wallets and exchange operational keys
- Bridges, issuers, or operator sets outside ordinary user wallets
Mitigations
- Inventory every key that can move FLOW (self-custody, exchange, multisig, protocol roles)
- Name the host chain and bridge path for every balance
- Document operator/admin sets for L2s and apps
- Track ecosystem PQC research; branding is not deployment
- Use /assessment and claims methodology pages for program framing
FAQ
Multi-key accounts = PQC?
Weighted keys improve classical resilience, not post-quantum math.
Cadence vs EVM on Flow?
Inventory whichever environment holds your value.
Key concepts (technical dictionary)
Terms used on this page — open a definition: