Movement's published M1 protocol specification names three primitives and attributes consensus vote authentication to Ed25519. The running chain returns 48-byte BLS12-381 G1 consensus public keys, so the published inventory is both incomplete and wrong at one named point. Partial credit reflects that specific algorithms are named at all with usage attached; the deduction reflects a documented inventory that a reader cannot rely on for the consensus signature path.

The classification above is LayerQu's. Movement publishes no per-primitive Shor or Grover classification and no post-quantum tagging of any kind, which is what the score reflects.

0 post-quantum families. The deployed surface is entirely classical: discrete-log signatures (Ed25519, Multi-Ed25519, secp256k1 and secp256r1 ECDSA), pairing-based constructions (BLS12-381, Groth16 over BN254), Diffie-Hellman key exchange (X25519), and Grover-weakened symmetric and hash primitives (AES-256-GCM, SHA-256, SHA3-256). No lattice, hash-based, code-based or isogeny family is deployed.

No NIST PQC primitives deployed, so no NIST security category 1 to 5 mapping exists for this chain. The active surface contains only classical primitives: Ed25519 at roughly 128-bit classical security, BLS12-381 at roughly 128-bit classical security, BN254 below that after the extended tower number field sieve results, and SHA3-256 at roughly 128-bit post-Grover collision resistance.

The consensus client is a fork of Aptos Core and inherits Aptos's Move Prover formal-verification tooling for Move smart contracts. Library provenance is inherited Rust crates: the BLS12-381 module wraps the blst library and its own documentation warns that non-aggregated verification requires public keys to be wrapped in a validating type to prevent small-subgroup attacks, a caveat that transfers to Movement unexamined. No published audit specifically of Movement-divergent cryptographic code was found. The public mainnet RPC fullnode advertises a build from a fork commit dated 2026-04-27 while the fork's branch head carries later commits, so deployed build currency lags the source tree. Cryptanalytic-maturity tiers: Ed25519 and SHA-2 tier 1, SHA-3 and Keccak tier 2, BLS12-381 and BN254 pairing-based and classically mature but pairing-exposed under Shor.

Accounts authenticate with Ed25519 under the Aptos-derived model, in which the authentication key is a SHA3-256 commitment to the public key and the public key itself is revealed with the first transaction the account signs. Validator consensus public keys need no such trigger: all four BLS12-381 G1 keys are readable from the on-chain validator-set resource right now. MOVE traded at roughly 0.0062 USD on 2026-08-19, having set an all-time low of roughly 0.0058 USD the same day, which lowers dollar value at risk without changing the fraction of accounts with revealed public keys.

The mainnet ledger is continuous from its first block, timestamped 2024-12-05, giving roughly 20 months of accumulated account history at evaluation rather than the shorter horizon implied by the 2025 sovereign-L1 cutover. Any account that has ever transacted has a revealed Ed25519 public key and stays Forge-exposed indefinitely unless its authentication key is rotated to a post-quantum scheme, which no such scheme exists on this chain to rotate into. LayerQu has not measured the share of dormant or abandoned accounts on this chain and makes no claim about it.

All historical Ed25519 account signatures and all historical BLS12-381 consensus signatures across the full ledger are forgeable once Shor is available, the latter meaning that historical quorum certificates can be re-forged as well as individual spends. No published signature-scheme transition plan, no archival re-anchoring, and no hash-based commitment to long-term-valid history.

Validator and fullnode transport uses Noise_IK_25519_AESGCM_SHA256, a stripped-down Noise IK handshake over X25519 with AES-256-GCM and SHA-256, per the consensus client's own transport module. The handshake pattern is IK, not NK: the initiator knows the responder's static X25519 key in advance and transmits its own static key encrypted, so a harvested transcript yields both endpoint identities and the session payload to a future Shor attacker. Movement's primary mainnet RPC endpoint and its five documented partner endpoints (Sentio, Hello Moon, BlockPi, Lava, Ankr) terminate standard TLS with no hybrid post-quantum key exchange documented at any of them. NodeOps does not appear in Movement's endpoint documentation.

Movement is a transparent ledger; the Move account model and Move-VM execution traces are publicly observable through the public REST endpoint and the block explorer. No native shielding and no zk-account scheme. The keyless-account module, which would introduce an OIDC-derived identity path, is present on mainnet but inert with zero configured providers.

Five documented partner RPC endpoints (Sentio, Hello Moon, BlockPi, Lava, Ankr) plus Movement's primary endpoint; NodeOps is not on the documented list. No RPC traffic-share telemetry is published, so partner concentration is not measurable. Mempool propagation is measurably concentrated for a different reason: all four active validators advertise both their validator and their fullnode network addresses as load-balancer hostnames in a single cloud provider's us-east-1 region, so transaction propagation among validators traverses one operator's network. Validator metadata-retention policy is undeclared.

Movement integrates LayerZero, whose developer tooling is maintained as a public fork under the Movement organization, and the framework carries a native atomic-bridge configuration resource on mainnet. Bridge transactions between Ethereum L1 and Movement create observable source and destination address pairs. No mixing and no bridge-level privacy primitive is deployed.

Movement does not deploy on-chain encryption at the protocol level: no ElGamal note ciphertexts in use, no discrete-log ring signatures, no zk-SNARK shielded pool. The framework does carry inherited ElGamal and Bulletproofs modules from upstream Aptos, but no shielded-asset path is configured on mainnet. Post-Shor, the marginal retroactive privacy loss beyond what is already public from a transparent ledger is small.

No mixnet, no on-chain commit-reveal mixing, no cryptographic shuffle, no information-theoretically secure cMix-class mixing.

The Aptos-derived account module deployed on Movement mainnet exposes rotate_authentication_key, rotate_authentication_key_call, rotate_authentication_key_from_public_key and rotate_authentication_key_with_rotation_capability, with the matching rotation-proof-challenge structures, so the signature scheme bound to an account can change without changing the address. Movement has no published production instance of rotating an account to a new signature family, and no post-quantum family exists on this chain to rotate into. Inherited capability, no deployed precedent.

Native authentication-key rotation is deployed and live at the framework level on mainnet, confirmed against the account module's on-chain ABI, which is account-model-abstraction equivalent and scores 15 under the rubric's account-model band for rotation without a documented client-layer post-quantum path. Movement's standard accounts commit to an RFC 8032 Ed25519 seed-derived key, so the scheme seed floor of 6 also applies but is subsumed by the higher account-model component, combined by maximum rather than sum. The post-quantum rebind bonus is 0: there is no chain-specific rebind design, no post-quantum-sound prover, and no path to freeze acceptance of raw Ed25519 signatures. No Movement-specific client-layer PQC path is documented.

Movement executed an L2-to-L1 architectural pivot on an existing ledger, announcement-dated to 2025-12-22, with no new genesis. Coordinated-upgrade history since then is real but thin: four tagged sovereign-L1 full-node releases shipped between 2026-03-18 and 2026-05-29, and the consensus-client fork has carried commits continuously through 2026-08-19, including through the Chapter 11 period. Against that, the public mainnet RPC fullnode still advertises a build from 2026-04-27, so shipping a release and having the network run it are visibly different things here, and no upgrade in this period has been documented as a coordinated network-wide hard fork. Concurrent governance turbulence, including the May 2025 leadership terminations and the Foundation-to-Move-Industries operational transfer, further limits what the coordination record demonstrates.

Architecturally possible through the authentication-key abstraction and the single-key authenticator, which already carries multiple public-key variants and could in principle carry another. Movement has not announced or scoped a hybrid post-quantum deployment. Upstream, aptos-core has merged SLH-DSA-SHA2-128s (FIPS 205) implementation code under AIP-137 and defines its feature flag in the Rust-side default feature set, but the proposal remains at status Accepted, the flag position is clear in Aptos mainnet's own on-chain feature bitvector, and none of that code or that flag exists in Movement's fork. Announced-not-shipped upstream, absent downstream; architectural-possibility credit only.

Not applicable, no stateful hash-based scheme (XMSS per RFC 8391, LMS per RFC 8554, leanXMSS) is deployed, so no state-management or one-time-key-reuse risk exists. Default 15.

In scope and scored 0. Movement M1 runs a Jolteon-style BFT consensus whose quorum certificates aggregate BLS12-381 signatures: every active validator's consensus public key is a 48-byte G1 element in the minimal-pubkey-size variant with proof-of-possession, read directly from the on-chain validator set. This is a BLS-aggregating BFT chain with epoch-public validator keys and zero declared post-quantum aggregation path, which the rubric flags as consensus-layer-exposed regardless of finality speed. No merged specification, no research statement, and no acknowledgement that the aggregation path needs replacing. This sub-score is in scope for Dim 4: the chain state shows consensus votes are not Ed25519-only.

0% of Movement M1 mainnet signing traffic is on post-quantum primitives. Account signatures are Ed25519 and consensus vote signatures are BLS12-381. SLH-DSA-SHA2-128s, the post-quantum signature scheme carried in the upstream Aptos tree, has its feature-flag position clear in Movement mainnet's on-chain feature bitvector and is not defined in Movement's fork at all, so no post-quantum authenticator can be submitted.

No post-quantum code in the Movement consensus client. A code search for the SLH-DSA scheme across Movement's active fork returns zero results, and the fork's feature-flag enumeration does not define the flag despite enumerating flags well past the upstream number, so this is an absence in Movement's own tree rather than a stale fork. Upstream aptos-core carries the implementation, is not activated on Aptos mainnet, and earns Movement no credit.

0% of validators run post-quantum keys. All four active validators present 48-byte BLS12-381 G1 consensus public keys, and their owner and operator accounts authenticate with Ed25519. No post-quantum key type exists in the client to adopt.

Voided per the rule that milestone discipline requires non-zero mainnet post-quantum traffic (5a = 0). Independently, no published dated PQC migration milestones exist from the Movement Network Foundation or Move Industries, and Movement's own improvement-proposal repository contains 13 numbered proposals with no post-quantum entry.

Trailing-12-month post-quantum announcements from Movement: 0. Trailing-12-month shipped post-quantum capability: 0. Nothing has been claimed that was not delivered, so no washing tag fires. This sub-score credits the absence of inflation, not the presence of progress.

Undisclosed. No post-quantum scheme is deployed and Movement publishes no sizing or gas analysis for one. Per the scoring table, undisclosed scores 0. For reference, the upstream proposal Movement has not adopted would carry a 7,856-byte signature with a 32-byte public key against Ed25519's 64 and 32 bytes.

Wallets named in Movement's current documentation: Motion, described there as the official self-custodial wallet built by Move Industries with keys encrypted and stored locally, plus OKX Wallet and Nightly. Razor Wallet does not appear. None of the three publishes a post-quantum roadmap and no quantum-safe language appears for any of them on Movement's documentation.

LayerZero is the dominant cross-chain messaging integration; its developer tooling is maintained as a public fork under the Movement organization, and Movement's framework carries a native atomic-bridge configuration resource on mainnet. Stargate, which provides liquidity transport over LayerZero, was acquired by LayerZero in a deal approved by Stargate governance in August 2025 at a stated 110 million dollars. LayerZero publishes no post-quantum roadmap. Wormhole and Celer are secondary or absent integrations on Movement.

A major US-regulated spot exchange announced on 2025-05-01 that it would suspend MOVE trading, effective 2025-05-15, reported at the time as a delisting, which narrowed institutional venue coverage for the asset. The 2026-07-15 Chapter 11 filing of MVMT Labs, Inc. and the continued MOVE price decline add counterparty and relevance uncertainty for custodians, even with Move Industries stating that network operations are unaffected. Fireblocks, BitGo and Anchorage publish no Movement-specific post-quantum support, and no top-3 custodian publishes a Movement-specific post-quantum roadmap.

Documented RPC partners: Sentio, Hello Moon, BlockPi, Lava, Ankr, with NodeOps absent from the list. No partner publishes a Movement-specific post-quantum RPC roadmap and none advertises hybrid key exchange at its TLS termination. HSM and TEE attestation chains for Movement validator infrastructure are not documented at the Foundation level, and the validator set's advertised endpoints are cloud load-balancer hostnames with no attestation surface published.

Measured, not estimated. The on-chain validator-set resource returns four active validators and zero pending, holding roughly 24.8%, 25.5%, 24.6% and 25.2% of voting power, so two validators together exceed one third and the Nakamoto coefficient for consensus halting is 2. All four advertise their validator and fullnode network addresses as load-balancer hostnames in a single cloud provider's us-east-1 region, so operator and jurisdiction concentration compounds stake concentration. Validator-set change is permitted by the staking configuration, but no validator has joined or is pending. Movement publishes no Foundation-grade transparency report and its block explorer surfaces price, transaction and account totals with no consensus-decentralization metric, so this figure has to be read off the chain rather than off a Movement page. Client diversity is single-client.

The L2-to-L1 pivot was announced in May 2025 and dated to December 2025. Engineering output did not stop under pressure: four tagged sovereign-L1 full-node releases shipped between 2026-03-18 and 2026-05-29, and the consensus-client fork carried commits through the Chapter 11 window and up to 2026-08-19. Against that, the public mainnet RPC fullnode advertises a build from 2026-04-27, so released does not equal deployed, and the period includes co-founder termination, leadership turnover, a major-exchange trading suspension, and the 2026-07-15 Chapter 11 filing of the original core-development entity, alongside a publishing pivot to stablecoin-payments output. Demonstrated capacity to keep a client moving is not the same as demonstrated capacity to coordinate a protocol-wide cryptographic migration across a validator set, and nothing in the record demonstrates the latter.

Move Industries is the named primary operating service provider and CEO Torab Torabi is re-confirmed by name and title in the official statement of 2026-07-28 responding to the Chapter 11 filing. The President and CTO roster named in 2025 press is not re-confirmed in that statement and is treated as unconfirmed-current. The original core-development entity, MVMT Labs, Inc., is in Chapter 11 as of 2026-07-15. The Movement Network Foundation oversees governance. There is no named post-quantum working group, no named post-quantum technical lead, and no published post-quantum mandate anywhere in Movement's documentation, blog, improvement proposals or code repositories.

The 2025 token-dump episode, in which an undisclosed market-making arrangement placed tens of millions of dollars of MOVE with an intermediary, drew an exchange action against the market maker on 2025-03-25, investigative press coverage from 2025-04-30, a major-exchange trading suspension announced 2025-05-01 and effective 2025-05-15, and the dismissal of a co-founder in May 2025. The 2026-07-15 Chapter 11 filing followed. Both episodes were answered with leadership change and corporate or legal restructuring, not with a coordinated technical fork, rollback or emergency protocol response. There is no post-quantum-relevant adversarial coordination precedent, and no adversarial precedent of any kind that exercised the validator set.

No canary, no Hourglass-style rate-limit, no cryptographic tripwire embedded in consensus, and no automated-response mechanism. Nothing in the deployed framework watches for anomalous signature validity or for a break in either the Ed25519 or the BLS12-381 path.