1 Signature scheme 0/10, weighted 30%
Band 0: Classical signatures only on mainnet, with nothing post-quantum protecting live funds. Short-lived devnets and one-off benchmarks sit here: they demonstrate research rather than something a user can hold keys on.
Aptos transactions are signed with Ed25519 today and nothing post-quantum protects live APT. The SLH-DSA-SHA2-128s authenticator is enabled only on devnet, which is reset and is not a network a holder keeps funds on; the feature flag is off on testnet and mainnet.
source
2 Deployment stage 5/10, weighted 25%
Band 5: Tier 3: Committed.
Tier 3: Committed. AIP-137, written by Aptos Labs and accepted in April 2026, names SLH-DSA-SHA2-128s as the post-quantum scheme for Aptos accounts, and its implementation is merged and enabled on devnet. No post-quantum signature is live on mainnet.
source
3 NIST alignment 8/10, weighted 15%
Band 6 to 8: The scheme is NIST-selected but the standard is not yet final, or a NIST-approved scheme is named but not yet deployed.
SLH-DSA-SHA2-128s is a parameter set of FIPS 205, a final NIST standard published in August 2024, not a candidate awaiting publication, and AIP-137 names it for Aptos accounts. It is not yet deployed: the feature is enabled on devnet only and is off on mainnet. Choosing a hash-based standard also means the security rests on SHA-256, which the chain already depends on.
source
Placement in the band The top of the band rather than a 9: the scheme is a final standard named under an accepted proposal, but it is switched off on mainnet, so it is not in use protecting funds, and use on mainnet is what the 9 to 10 anchor requires.
4 Migration path 7/10, weighted 15%
Band 6 to 8: A credible published plan exists with a mechanism identified, but key parts are unbuilt or undated.
AIP-137 is accepted and makes SLH-DSA opt-in: existing Ed25519 accounts keep working, and a holder who wants protection rotates the account's authentication key to an SLH-DSA key with the existing rotate_authentication_key_call function, keeping the same address and funds. The verification logic and gas pricing are merged; command-line support, indexer support and documentation are still unbuilt, and there is no mainnet date.
source
Placement in the band A 7 rather than a 6: the mechanism is in-place key rotation under an accepted proposal with merged code, so no holder has to move funds to a new account. Not an 8: protection is opt-in, the feature is off on mainnet with no date, and the command-line tools a holder would use are not built.
5 Exposure 2/10, weighted 10%
Band 0 to 2: Public keys are exposed for effectively all accounts, or a large, measured share of total supply sits in exposed addresses.
Aptos is an account-model chain and an account's public key is revealed on-chain when it first signs a transaction, so effectively all economically active supply has an exposed key and is harvestable today.
source
Placement in the band At the top of the band rather than a 0 or a 1: the key is revealed only on first transaction, so never-used accounts retain protection, though on an active chain that covers almost nothing.
6 Verification 4/10, weighted 5%
Band 3 to 5: A post-quantum component exists, on mainnet, on a persistent testnet or as a merged implementation, but is unreviewed.
SLH-DSA-SHA2-128s was merged into aptos-core's cryptography crate in December 2025 (pull request 18293) and as a transaction authenticator in January 2026 (pull request 18300), shipped in release v1.41 and enabled on devnet. Pull request 18300 was written by Alin Tomescu of Aptos Labs and approved by three Aptos Labs engineers, with an automated review bot; we found no reviewer from outside Aptos Labs.
source
Placement in the band A 4 rather than a 5: merged and running, but only on devnet, which is reset, rather than on mainnet or a persistent testnet a holder or a reviewer could use.