CRONOS · L1 · STAGE 0 UNAWARE-OF-DEPLOYMENT-PATH · QRI 20 v3.1.0 methodology

Cronos's posture is the v2 evaluator's 'wait' call substantiated under v3.1: zero PQ R&D, zero PQ announcement, no PQ migration lead. The chain inherits whatever Cosmos SDK + CometBFT + go-ethereum upstream eventually merges, and the maintenance burden of four downstream forks (crypto-org-chain/cometbft, cosmos-sdk, ethermint, go-ethereum) means Cronos lags upstream by months on every adoption. Crypto.com custody concentration is a structural quantum-risk amplifier.

inLinkedIn ↷Audit access ⇆Compare Verified 2026-05-01

Summary

Cronos is Crypto.com's Ethermint-based EVM L1 on Cosmos SDK + CometBFT, mainnet beta 2021-11-08, 33 invitation-only validators, dense bridge connectivity (IBC, Crypto.com Bridge, LayerZero), Crypto.com-led governance. Migration Stage 0 (Unaware-of-deployment-path). No PQ on mainnet, no merged PQC code across the four crypto-org-chain forks (cometbft, cosmos-sdk, ethermint, go-ethereum), no published roadmap. Active primitives: Ed25519 (CometBFT validator consensus signing); secp256k1 ECDSA (EVM EOA signatures via Ethermint, Keccak-256 message digest); Keccak-256 (EVM transaction / state hashing); SHA-256 (Cosmos SDK / CometBFT block-hash and IBC commitment); X25519 / Ed25519 (CometBFT p2p secret connection handshake). The 33-invited-validator model means coordination authority for a PQ migration sits with Crypto.com / Cronos Labs as a single decision-maker, fast (7b) but legitimacy-narrow (7a). V4, V5, V6 mainnet upgrades sustained smoothly. Gate 1a-Sig FAIL, Gate 1a-KEM FAIL. QRI 20, Band 2 Acknowledged (boundary case; raw 19.53 sits at Band-2 ceiling, Band-3 floor at 21).

What the gates say

Gate 1a, Hybrid signature: FAIL , no documented hybrid signature composition AND or OR; no ADR, no spec, no roadmap
Gate 1a, Hybrid KEM: FAIL , CometBFT secret-connection X25519, RPC TLS classical X25519 / RSA / ECDH; no hybrid PQ KEM deployed
Gate 1b, Commit-to-hash: COND , only relevant if Gate 1a-Sig passes via OR-composition
Gate 2, Evidence reconstruction: PASS , every sub-score reconstructible from public artifacts within 48 hours
Gate 3, Primitive naming: PASS , Ed25519, secp256k1 ECDSA, X25519, Keccak-256, SHA-256 named with mechanism

Burn-vs-rescue policy on file

Declared option f, Undeclared. No published Cronos / Crypto.com policy on what happens to CRO at quantum-vulnerable EOAs post-CRQC. No freeze / burn proposal, no STARK rescue scheme, no rate-limit canary, no client-layer hybrid migration framework.

Seven dimensions

Each dimension scores 0–100 internally; the weighted roll-up produces the QRI.

1 Cryptographic Exposure weight 15% 25 / 100

1a · primitive inventory 12 / 20

Reconstructible from crypto-org-chain/cronos go.mod (CometBFT v0.38.20 fork, Cosmos SDK v0.53.4 fork, evmos/ethermint fork, go-ethereum v1.15.11 fork). Not enumerated in any Cronos-authored spec.

Primitives: Ed25519 (CometBFT validator consensus signing, default per priv_validator_key.json) · secp256k1 ECDSA (EVM EOA signatures via Ethermint, Keccak-256 message digest) · Keccak-256 (EVM transaction / state hashing) · SHA-256 (Cosmos SDK / CometBFT block-hash and IBC commitment) · X25519 / Ed25519 (CometBFT p2p secret connection handshake) · Standard TLS for RPC / REST

1b · shor grover pq tag 6 / 20

Tags:

Ed25519 → Shor-break-via-DL-without-pairings
secp256k1 ECDSA → Shor-break-via-DL-without-pairings
X25519 → Shor-break-via-DL-without-pairings (HNDL-relevant)
Keccak-256 → Grover-weaken (256→128-bit)
SHA-256 → Grover-weaken (256→128-bit)

1c · family diversity 0 / 20

0 PQ families. Two classical EC families in use, but neither is PQ-safe.

1d · nist security category 2 / 20

secp256k1 ECDSA ≈ 128-bit classical / 0-bit post-Shor; Ed25519 ≈ 128-bit classical / 0-bit post-Shor; Keccak-256 / SHA-256 ≈ 128-bit post-Grover. No NIST PQC primitive mapped.

1e · implementation quality 5 / 20

CometBFT carries a TLA+ specification from upstream Tendermint; go-ethereum and Ethermint forks have no machine-checked PQ-relevant proofs. Standard Go crypto/ed25519 constant-time; secp256k1 via btcec constant-time. Cronos forks every major upstream via go.mod replace-directives, adds maintenance surface. Stateless. Cryptanalytic tier 1.

2 Quantum Recovery Exposure weight 10% 17 / 100

Forge subtotal: 13/75 Decrypt subtotal: 4/25

2a · active key exposure 4 / 25

Cronos EVM EOAs follow standard go-ethereum / Ethermint pattern: address = keccak256(uncompressed_secp256k1_pubkey)[12:]. Pubkey is Shor-recoverable from any signed transaction. Supply concentration is exchange-heavy: Crypto.com Exchange / foundation / treasury wallets hold the largest CRO share.

2b · cold key exposure 5 / 25

Accounts that never signed retain address-as-keccak256-hash protection. EOAs that signed once expose pubkey indefinitely. Mainnet beta launched 2021-11-08, ~54 months at evaluation. Crypto.com custody concentration adds correlated cold-key risk.

2c · sig long term validity 4 / 25

Every historical Ed25519 validator vote and secp256k1 EVM signature is forgeable post-CRQC. IBC channels rely on Ed25519 validator-set signatures for light-client header verification, a CRQC adversary can forge valid-looking historical Cronos headers against any Tendermint light client. Crypto.com Bridge and LayerZero bridge attestations extend sig-validity exposure further.

2d · encryption confidentiality hndl 4 / 25

CometBFT p2p secret connection uses X25519 ECDH for validator transport (Shor-vulnerable, HNDL scope). RPC / REST endpoints (Crypto.com-operated plus Ankr, QuickNode, GetBlock) use standard TLS with classical X25519 / RSA / ECDH. No hybrid PQ KEM deployed anywhere in Cronos transport.

3 Metadata, Anonymity & Confidentiality weight 13% 16 / 100

3a · tx graph visibility 4 / 20

Fully transparent EVM ledger. Cronos addresses (0x...) pseudonymous; Cronoscan and Mintscan provide full historical analytics. IBC packet receipts and bridge events make cross-chain flow trivially linkable.

3b · rpc mempool concentration 3 / 20

Public RPC concentrated among Crypto.com-operated endpoints (evm.cronos.org, cronos-rpc.crypto.org) plus Ankr, QuickNode, GetBlock, NodeReal. Crypto.com runs the dominant share via the foundation-issued DeFi Wallet defaulting to Crypto.com endpoints. With 33 invited validators, the mempool surface is concentrated.

3c · cross chain bridge correlation 3 / 20

Cronos has dense bridge connectivity: IBC (Cosmos zones), Crypto.com Bridge, LayerZero. Each surface enables source-to-destination correlation. Crypto.com Exchange acts as a primary fiat / CEX on/off-ramp, adding KYC-linked correlation at the boundary.

3d · retroactive de anonymization 6 / 20

Cronos publishes no encrypted payload data, ZK-shielded transactions, or DL-based ring signatures at the chain level. Confidentiality risk under Shor is limited to identity-linkability rather than payload decryption.

3e · mixnet shuffle 0 / 20

None at protocol level.

4 Migration Architecture weight 10% 48 / 100

4a · crypto agility 5 / 15

CometBFT (forked v0.38.20) supports --key-type for validator consensus key selection (Ed25519 default, secp256k1 selectable); Cosmos SDK crypto/keys is modular. Cronos inherits both. No production agility move on Cronos itself within 5 years: V6 was an infrastructure bump, not a primitive change. EVM precompile additions follow go-ethereum; no PQ precompile added.

4b · aa key rotation 6 / 20

Chain level: ADR-016 consensus-key-rotation inherited from Cosmos SDK upstream. EVM-account level: ERC-4337 contracts deployable but no documented Cronos-specific AA bundler / paymaster ecosystem from the foundation, and no foundation announcement of EIP-7702 enablement. The go-ethereum fork at v1.15.11 is post-Pectra upstream, EIP-7702 opcodes are present in the binary, but Cronos has not announced enablement at chain level.

4c · hard fork track record 9 / 15

V4, V5, V6 mainnet upgrades sustained (CometBFT v0.38 + Cosmos SDK v0.50 family); 2025–2026 roadmap documents block-time-to-0.5s and 90%-gas-fee-reduction upgrades. Crypto.com-led governance executes smoothly; the 33-invited-validator model makes upgrade coordination a foundation operation. No publicly contested fork.

4d · hybrid deployment readiness 3 / 15

Architecturally, Cosmos SDK + CometBFT + Ethermint supports a hybrid validator key, constructible in principle. No spec, ADR, or roadmap item from Cronos for hybrid Ed25519+PQ or secp256k1+PQ. No Cronos-specific PQ R&D published.

4e · stateful hash state management 15 / 15

N/A by default, no stateful hash scheme in scope; stateless schemes score full per v3.1 rubric.

4f · bft aggregation path 0 / 0

N/A, Cronos uses CometBFT default Ed25519 non-aggregating signatures at consensus. Per v3.1 rubric, 4f is N/A for non-aggregating-signature consensus chains.

5 Deployment Execution weight 22% 13 / 100

5a · mainnet pqc traffic pct 0 / 25

0% of validator votes or EVM EOA signatures on Cronos mainnet under a PQC primitive.

5b · pqc code in consensus client 0 / 15

No PQC scheme merged into crypto-org-chain/cometbft, crypto-org-chain/cosmos-sdk, crypto-org-chain/ethermint, or crypto-org-chain/go-ethereum forks. No PQ-related branch, PR, or feature flag in crypto-org-chain/cronos repository.

5c · validator pqc key adoption 0 / 15

All 33 active Cronos validators (invitation-only, vetted by Cronos team and existing validators) use Ed25519 consensus keys per CometBFT default. No validator has registered a PQC consensus key.

5d · published dated milestones 0 / 10

VOIDED to 0 per v3.1 rule (5a = 0). The Cronos 2025 Whitepaper and 2025–2026 roadmap headline tokenization (RWAs), AI agents, and infrastructure scaling, they contain no PQC milestone, no flag-day for classical-key sunset, no PQ-validator-key registration deadline.

5e · pqc washing delta 13 / 15

Announced PQC trailing-12-mo from Cronos / Crypto.com Labs: ~0 official communications mentioning post-quantum, PQC, NIST FIPS 203/204/205, or quantum migration. Shipped PQC: 0. No washing detected.

5f · signature footprint multiplier 0 / 20

No PQ deployment, no published bytes-per-block analysis under any PQ scheme. Undisclosed.

6 Supply Chain Vendor Readiness weight 22% 7 / 100

6a · wallet 2 / 25

Top-3 wallets: Crypto.com DeFi Wallet (foundation-issued, secp256k1), MetaMask, Ledger HW. None publish a Cronos-specific PQC roadmap. Crypto.com DeFi Wallet has no public PQC posture. Ledger has internal PQC research at Ledger Donjon but no shipped PQ-signing for Cronos.

6b · bridge 2 / 25

Top-3 bridges: Crypto.com Bridge (Crypto.com-operated EVM bridge, classical multisig + secp256k1), IBC (light-client model, Ed25519 verification, classical), LayerZero (DVN-based omnichain messaging, classical secp256k1 / BLS). None publish a PQC roadmap.

6c · custodian 2 / 25

Top-3 custodians: Crypto.com Custody (foundation-affiliated; received initial U.S. federal-charter approval for a regulated crypto custodian bank in 2026), Coinbase Custody, BitGo. MPC-PQ for secp256k1 signing not in production for CRO at any of the three.

6d · rpc hsm tee infra 1 / 25

Top RPC providers serving Cronos: Crypto.com-operated cronos-rpc.crypto.org and evm.cronos.org, plus Ankr, QuickNode, GetBlock, NodeReal. None publish PQ-enabled RPC TLS. Validator HSMs: standard YubiHSM2 / Ledger / AWS KMS, no PQ signing in production. TEE attestation chains not declared.

7 Governance & Coordination weight 8% 35 / 100

7a · validator stake distribution 5 / 20

33 invitation-only validators, vetted by Cronos team and existing validators. Nakamoto coefficient structurally low, a permissioned set of this size with concentrated Crypto.com-aligned voting power implies a coefficient in low single digits. Client diversity: monoculture (single CometBFT fork, single go-ethereum fork).

7b · upgrade cadence under pressure 12 / 20

V4, V5, V6 upgrades coordinated cleanly via on-chain governance + invited-validator coordination. Block-time and gas-fee performance upgrades shipped. Cadence is fast, but it is a centralized cadence. No public test of upgrade execution under adversarial-pressure conditions.

7c · named coordination lead 10 / 20

Named: Crypto.com (parent corporate entity, CEO Kris Marszalek), Cronos Labs (development entity), the Cronos Network Council. No named PQC migration lead, no named cryptographer of record, no foundation working group on quantum migration.

7d · adversarial coordination precedent 8 / 20

Crypto.com itself disclosed a January 2022 exchange-side hot-wallet incident (~$30M, customer funds reimbursed). That was a Crypto.com Exchange operational incident, not a Cronos chain coordination event under attacker pressure.

7e · canary tripwire mechanism 0 / 20

No canary, honeypot, rate-limited spending rule, or cryptographic tripwire on Cronos.

X + Y vs Z, when does the math turn against you?

v3.1 demotes the X+Y vs Z timing test to a secondary signal, the headline output is Migration Stage. The timing test still answers the question: can this chain finish migrating before the threat lands?

X, signature shelf life

5–15 years (historical Ed25519 validator votes and secp256k1 EVM transaction signatures sit on-chain indefinitely; IBC light-client checkpoints, Crypto.com Bridge, LayerZero DVN attestations extend signature validity)

Y, migration time

5–10 years (Cronos-specific hybrid spec would need to be written or upstream ADR adopted, merged into the four crypto-org-chain forks, validated under 33-validator coordinated rotation, integrated into Crypto.com Bridge and LayerZero verification paths, and propagated to Crypto.com DeFi Wallet)

Z10 (10% CRQC year)

2030

Z25 (25% CRQC year)

2035

Verdict

X+Y > 2035, Crisis Zone (vs Z10 2030); Outside risk window (vs Z25 2035)

Z-compliance

Outside compliance window (CRO-issuing entity Crypto.com operates U.S. customer-facing exchange and U.S. federally-approved custody bank, direct exposure to NIST timelines)

Source-disagreement disclosure

v3.1 requires every chain card to publish material divergences among authoritative sources, plus the delta-QRI under alternative weighting.

Validator count

v2 baseline scorecard recorded 26 validators (evaluated 2026-04-18). Current Cronos foundation FAQ states 33 validators. Difference is consistent with set growth between v2 and v3 evaluation dates. Card uses 33 (current foundation source).

Consensus naming inconsistency in Cronos's own docs

Foundation FAQ describes consensus as 'Proof of Authority (POA) consensus, derived from the Tendermint POS consensus'; the architecture page describes it as 'Tendermint's Core BFT Proof-of-Stake consensus engine'; the go.mod shows CometBFT v0.38.20. Reconciled: Cronos runs CometBFT (BFT consensus engine) with a permissioned, invitation-only validator set.

Scope confusion with sibling chains

Some third-party guides conflate Cronos (EVM L1, this card) with Cronos POS Chain (the original Crypto.org Cosmos chain at cronos-pos.org) and Cronos zkEVM (the ZKsync L2 launched alpha 2024-08-15). This card scores Cronos EVM L1 only.