Blockchain Quantum Readiness Index / Aptos
L1 · Move
Aptos
A post-quantum signature for accounts (SLH-DSA, a NIST scheme) is merged code but only enabled on devnet, not mainnet. Accounts and validators still use elliptic-curve keys, and no official bridge is documented. Migration is planned through the existing key-rotation feature.
Last reviewed 2026-10-19
Is Aptos quantum safe?
Not yet. Aptos is at Stage 2 (Code merged) in LimeChain's Blockchain Quantum Readiness Index, with a progress score of 17.3/100. Post-quantum accounts are in the core code but not yet running on a public network. Still exposed or unproven: consensus, bridges & messaging.
What Aptos needs for Stage 3: Testnet
- Stage 3 needs PQ user accounts on a public testnet or mainnet (U is: in-dev)
Caps and adjustments
- cap 40: users cannot hold and spend funds under a production PQ mechanism on mainnet
- cap 60: consensus PQ not even on testnet
Rosette slices
| Slice | State | Points | Weight | Reason & evidence |
|---|---|---|---|---|
| U User keys | In development At rest: Hidden until first spend The address is the initial authentication key, sha3-256(pubkey | scheme), so an account that never signed keeps its Ed25519/secp256k1 key hidden until the first transaction. The unproven rotate_authentication_key_call takes only the new authentication key (a hash), so a fresh key stays hidden until it signs (the proven rotation passes the new public key on-chain). SLH-DSA (feature 107) is not on mainnet, so there is no `pq` option. Account abstraction was not assessed as a PQ vault. |
4/10 | 25 | SLH-DSA-SHA2-128s authenticators are merged (PR #18300, feature flag 107) but enabled only on devnet; the mainnet and testnet Features bitsets lack flag 107 as of 2026-10-12. |
| C Consensus | Exposed | 0/10 | 20 | Validator consensus keys are BLS12-381 (ValidatorConfig.consensus_public_key: bls12381::PublicKey), account keys Ed25519/secp256k1; AIP-137 is accounts-only, so no PQ path for validator signatures. Sources 7 |
| P Proof system | Not applicable | — | — | L1 with no validity or fraud proof system. no evidence |
| B Bridges & messaging | Unknown | 0/10 | 15 | No canonical bridge in official docs or accepted AIPs. The former Aptos Bridge site now serves the LayerZero/Stargate front-end, with no primary source showing Foundation endorsement or a majority of bridged value, so the surface is not rated. no evidence |
| A Admin & upgrade keys | Not applicable | — | — | No admin/upgrade key: core code and Aptos Framework changes go through on-chain governance (aptos_governance) with stake-weighted votes; vote signatures fall under C/U. Sources 8 |
| M Migration & recovery | Planned | 2/10 | 15 | AIP-137: PQ adoption uses the existing account::rotate_authentication_key_call entry function, which changes the auth key without changing the address. The flag is not yet on mainnet. Sources 1 |
Stage gates
| Requirement | Status | Details & evidence |
|---|---|---|
| Current audit of the deployed PQ signing code (Stage 5) | Not met | not claimed |
| Admin timelock of at least 30 days with a PQ override (Stage 6, alternative to PQ admin keys) | Not met | not claimed |
| Ratified migration plan with an activation date (Stage 6) | Not met | not claimed |
| New accounts PQ or hybrid by default (Stage 6) | Not met | not claimed |
| ECC sunset enforced (Stage 7) | Not met | not claimed |
PQ adoption published, not scored
There are no PQ accounts on mainnet yet. Having PQ accounts does not mean people move to them. This tracks the share of value and accounts that actually moved, over time.
Measured exposure
No on-chain probe run yet. Bitcoin, Solana, Cosmos and Substrate probes are planned.
Evidence and sources (8)
Every non-zero rating above cites at least one of these public sources.
- github.com/aptos-foundation/AIPs/blob/main/aips/aip-137-post-…
- github.com/aptos-labs/aptos-core/pull/18300
- fullnode.mainnet.aptoslabs.com/v1/accounts/0x1/resource/0x1::…
- aptos.dev/network/blockchain/accounts
- aptos.dev/build/guides/key-rotation
- raw.githubusercontent.com/aptos-labs/aptos-core/mainnet/aptos…
- raw.githubusercontent.com/aptos-labs/aptos-core/main/types/sr…
- aptos.dev/network/blockchain/governance
Source: chains/aptos.json. Reproduce: python3 score.py chains/aptos.json
Building on Aptos?
LimeChain helps teams plan their post-quantum migration: what is exposed, what to change first, and the engineering to get there.
Talk to usOpen, repeatable scoring. Non-zero ratings need public evidence; missing evidence means unknown. Methodology v0.4 · mechanism registry 2026-10-13.