chain · quantum risk
Sui Cryptography Profile (Quantum Risk)
Verdict
As a chain, Sui should be modeled via its authorization cryptography—not market narratives. Sui is not quantum-proof by default. Account signatures are classical (commonly Ed25519-class); object model sophistication does not equal PQC.
Overview
Sui (SUI) is included in Wave 6a as a top-market-cap L1 / native smart-chain target. This page is the chain cryptography profile.
Sui uses an object-centric Move data model with modern classical signatures for account authorization. Performance and developer UX are not substitutes for post-quantum primitives.
Inventory wallet keys, custody, and any shared upgrade authorities for critical packages—same authority-graph thinking as Solana/Ethereum, different runtime.
For the direct verdict hub see /is-quantum-proof/sui. For holder framing see /crypto/sui.
Cryptographic profile
- Signatures: Ed25519 and other schemes supported by Sui accounts (verify current wallet defaults)
- Hash: Move/object model hashing as specified by Sui
- Public-key exposure: Object-centric accounts; authorities and pubkeys are on-chain identities.
What breaks
- Classical signatures authorizing SUI value movement under Shor-class adversaries once public keys are known
- Custodial hot wallets and exchange operational keys
- Bridges or wrapped representations with concentrated signers (if used)
Mitigations
- Inventory every key that can move SUI (self-custody, exchange, multisig)
- Prefer multiparty / hardware policies for treasuries
- Document bridges and wrapped asset paths
- Track ecosystem PQC research; do not assume branding equals deployment
- Use /assessment and chain comparison hubs on this site for program framing
FAQ
Is Move quantum-safe?
Move is a language/runtime model, not a PQC signature suite.
Closest comparison pages?
Solana (Ed25519 accounts) and Ethereum (smart-contract authority graphs).
Key concepts (technical dictionary)
Terms used on this page — open a definition: