What it is. Osmosis is the busiest trading hub linking dozens of separate crypto networks, and it has done nothing to prepare its account and validator security for future quantum computers.
What we found. Because so many other networks trust Osmosis to verify cross-chain transfers, a quantum attacker who broke its security could fake activity that ripples outward to the 45-plus chains plugged into it, and the team has no plan, no proposal, and no code to close that gap.
Why it matters. Anyone holding tokens or moving money through Osmosis is exposed not only on Osmosis itself but across every connected network, and a separate vote to fold Osmosis into another chain could quietly shift who is even responsible for fixing this.
Osmosis inherits CometBFT Ed25519 validator-consensus signing and Cosmos SDK secp256k1 ECDSA account signing without modification; as the largest IBC DEX hub (~45+ connected zones), Osmosis amplifies the same downstream sig-validity fanout that Cosmos Hub has. No public PQC roadmap, no PQ governance proposal, no PQC code in canonical osmosis-labs/osmosis client.
Summary
Osmosis scores QRI 22, Band 3 Planning, Migration Stage 0. Built on CometBFT + Cosmos SDK, Osmosis uses Ed25519 for validator consensus signing, secp256k1 ECDSA (R||S lower-S, SHA-256 digest) for osmo1... account signatures, SHA-256 for block and IBC commitment hashing, X25519 for CometBFT p2p secret-connection handshake, and standard TLS for RPC/REST. Custom modules (gamm, concentrated-liquidity, superfluid-staking, lockup, valset-pref, txfees, protorev) inherit signing posture from baseline Cosmos SDK and add no new cryptographic surface beyond classical primitives. ~150 active validators per genesis-validators.md and TMKMS validator docs. No PQ-safe primitive in active use. No published PQC ADR, no governance proposal on cryptography in trailing 12 months on Mintscan. Co-founder Dev Ojha has publicly redirected to Zcash post-quantum scaling work, interpreted as Osmosis having no internal PQ migration lead. Active governance attention is on Proposal 1007 (Osmosis-into-Cosmos-Hub integration), which would consolidate Osmosis modules into Hub and make Hub's PQ posture controlling. Mainnet-Traffic Cap binds at 5a=0%. Migration Stage 0 with milestone-discipline cap on top.
What the gates say
- Gate 1a, Hybrid signature: FAIL , no documented hybrid signature composition AND or OR on Osmosis; no spec, no roadmap, no governance proposal
- Gate 1a, Hybrid KEM: FAIL , CometBFT secret-connection X25519, RPC TLS classical X25519/RSA; no hybrid PQ KEM deployed
- Gate 1b, Commit-to-hash: COND , only relevant if 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 , primitives named at every sub-score
Burn-vs-rescue policy on file
Declared option f, Undeclared. No published Osmosis policy on what happens to OSMO or pooled DEX assets at quantum-vulnerable accounts post-CRQC. No freeze/burn proposal, no STARK rescue scheme, no rate-limit canary, no client-layer hybrid migration framework. Pending Proposal 1007 may transfer the question to Cosmos Hub jurisdiction.
Seven dimensions
Each dimension scores 0–100 internally; the weighted roll-up produces the QRI.
1 Cryptographic Exposure weight 15% 28 / 100
Inventory clear and reconstructible from CometBFT, Cosmos SDK, and osmosis-labs/osmosis docs/code.
Ed25519 (CometBFT validator consensus signing, default per priv_validator_key.json and cometbft init) · secp256k1 ECDSA (Cosmos SDK account signatures for osmo1... addresses, R||S lower-S form, SHA-256 message digest) · SHA-256 (block hashing, IBC commitment hashing) · X25519/Ed25519 (CometBFT p2p secret connection handshake) · Standard TLS for RPC/REST No PQ-safe primitive in active use. Custom Osmosis modules (gamm, concentrated-liquidity, superfluid-staking, lockup, valset-pref) add no new cryptographic primitives beyond Cosmos SDK baseline.
Ed25519→ Shor-break-via-DL-without-pairingssecp256k1 ECDSA→ Shor-break-via-DL-without-pairingsSHA-256→ Grover-weaken (256→128-bit)
0 PQ families. Two classical families (Edwards-curve EdDSA, Weierstrass-curve ECDSA), but neither PQ-safe; the diversity rubric counts PQ families.
Ed25519 ≈ 128-bit classical / 0-bit post-Shor; secp256k1 ECDSA ≈ 128-bit classical / 0-bit post-Shor; SHA-256 ≈ 128-bit post-Grover. No NIST PQC category mapped because no NIST PQC primitive in scope.
CometBFT consensus has TLA+ specification and machine-checked safety proofs; underlying Ed25519 / secp256k1 libraries are standard Go implementations without machine-checked PQ-relevant proofs. Standard Go crypto/ed25519 is constant-time; secp256k1 uses btcec/dcrec, known constant-time. Tier 1 (mature classical EC + SHA-2). No PQ implementation.
2 Quantum Recovery Exposure weight 10% 21 / 100
osmo1... accounts derive from secp256k1 pubkey hash. Pubkey is published on-chain on first outbound tx, so any account that has ever signed (every active LP, swapper, validator self-delegator) has its pubkey publicly recorded, Shor-forgeable post-CRQC. As the largest Cosmos DEX, the active-key surface is materially larger than for Cosmos Hub.
Accounts that have never signed retain pubkey-hash protection; accounts that signed once retain exposed pubkeys indefinitely. Osmosis mainnet has been live since June 2021; large fraction of OSMO supply has revealed pubkeys at some point through staking, pool entry, or governance voting.
Every historical Ed25519 validator vote and secp256k1 account signature is forgeable after CRQC. Osmosis is the largest IBC hub by transaction volume, its IBC light-client checkpoints are trusted by ~45+ counterparty zones. A CRQC adversary can forge valid-looking historical Osmosis headers against any Tendermint light client trusting historical validator-sets. Downstream fanout exceeds Cosmos Hub by transaction-volume measure.
CometBFT p2p secret connection uses X25519 ECDH key agreement for transport encryption between validators (Shor-vulnerable). RPC/REST endpoints use standard TLS. No hybrid PQ KEM deployed. Validator gossip and mempool transport sit fully in classical-DH HNDL scope.
3 Metadata, Anonymity & Confidentiality weight 13% 21 / 100
Fully transparent ledger; osmo1... addresses pseudonymous; AMM swap routes, LP positions, and IBC packet receipts make trade flow trivially linkable to any passive observer.
Top public RPC endpoints concentrated among a handful of operators (Polkachu, Numia, Imperator, Lavender.Five, Stake.Systems). Mempool gossip observable to any validator-grade node; protorev and mev-blocker-style ordering protections operate in-protocol but no validator-metadata-retention policy declared at protocol level.
Osmosis is the largest IBC routing hub by volume; channels to ~45+ connected zones make flows directly linkable. Axelar (BLS + Ed25519 classical) and Wormhole-wrapped assets add EVM-side correlation. Skip Protocol cross-chain swap routing further concentrates observability.
Osmosis does not publish encrypted payload data, ZK-shielded transactions, or DL-based ring signatures at protocol level. Confidentiality risk from Shor on its curves is limited to long-term cryptographic identity correlation rather than payload decryption.
None at protocol level. Threshold-encryption mempool concepts have been discussed by co-founders (ZK Podcast 188 on MEV prevention) but not deployed.
4 Migration Architecture weight 10% 55 / 100
Inherits Cosmos SDK crypto/keys modularity (Ed25519 default, secp256k1 selectable, sr25519 added historically) and CometBFT --key-type at validator init. No production validator-consensus-key-type swap on Osmosis mainnet within 5 years; agility is architectural, not demonstrated.
Inherits ADR-016 validator consensus key rotation and Cosmos SDK x/authz / x/feegrant. Olympus (SDK v0.52) consensus-key-rotation and x/accounts module flow into Osmosis as it tracks SDK upstream. No native account abstraction comparable to ERC-4337 / EIP-7702. No documented client-layer PQ migration path.
Coordinated upgrades v17, v18, v19, v20, v21, v22, v23, v24, v25, v26, v27, v28 sustained through 2024-2025 via on-chain governance with ~5-day voting period. Strong execution cadence. Proposal 1007 (Osmosis-Hub integration) is currently the largest contested governance item and has progressed through community discussion to passage on the Osmosis side.
cometbft init --key-type architecturally supports multiple consensus key types, so a hybrid validator key (parallel keys per validator, both verified at consensus) is constructible. No spec proposal or ADR for a hybrid Ed25519+PQ scheme on Osmosis. No osmosis-labs PR demonstrating hybrid-validator-key handling.
N/A by default, no stateful hash scheme in scope; stateless schemes score full per v3.1 rubric.
N/A. Osmosis uses Ed25519 non-aggregating signatures at consensus per CometBFT default (inherited from Tendermint; the Tendermint BLS-aggregation feature request was closed as not planned upstream). BLS is not in the Osmosis consensus path. Per v3.1 rubric, 4f is N/A for non-aggregating-signature consensus.
5 Deployment Execution weight 22% 13 / 100
0% of validator votes or account signatures on Osmosis mainnet under a PQC primitive.
No PQC scheme merged into osmosis-labs/osmosis main, no PQC scheme merged into cometbft/cometbft main, no PQC scheme merged into cosmos/cosmos-sdk main crypto/keys. External research forks (DoraFactory tendermint-pqc, cosmos-pqc) provide upstream Dilithium drop-in research but are not adopted in canonical Osmosis client.
All ~150 active Osmosis validators use Ed25519 consensus keys per CometBFT default. No validator has registered a PQC consensus key. TMKMS validator-key-management docs reference Ed25519 only.
VOIDED to 0 per v3.1 rule (5a = 0). No dated, enforcement-mechanism-backed PQC milestones for Osmosis mainnet.
Announced PQC trailing-12-mo from Osmosis Labs / Sikka / co-founders specifically about Osmosis: ~0 official communications. Co-founder Dev Ojha has publicly redirected to Zcash post-quantum work, that is Zcash-scope, not Osmosis-scope. Shipped PQC: 0. Ratio undefined / low. No washing detected (no claims to deflate).
No PQ deployment, no published bytes-per-block analysis under any PQ scheme for Osmosis. Undisclosed.
6 Supply Chain Vendor Readiness weight 22% 8 / 100
Top-3 in-ecosystem wallets supporting Osmosis: Keplr, Leap, Ledger HW. None publish a PQC roadmap. Ledger HW has internal PQC research at Ledger Donjon but no shipped PQ-signing for Cosmos accounts.
Top-3 routes into Osmosis liquidity: IBC (light-client model, Ed25519 verification), Axelar (BLS + Ed25519 classical), Wormhole (Ed25519 guardian set, classical). None publish a PQC roadmap. IBC v2 / Eureka work targets ZK-Tendermint light client, succinctness, not PQ; the Ed25519 verification stays. Skip Protocol cross-chain orchestration adds no PQ layer.
Top-3 institutional custodians supporting OSMO: Coinbase Custody, BitGo, Anchorage. None publish an Osmosis-specific PQC roadmap. None have MPC-PQ in production for OSMO signing.
Top RPC providers: Polkachu, Numia, Imperator, Lavender.Five. None publish PQ-enabled RPC TLS. HSMs used by validators per TMKMS docs: standard YubiHSM2 / Ledger / AWS KMS, no PQ signing for Ed25519/secp256k1 in production. TEE attestation chains not in Osmosis validator stack at protocol level.
7 Governance & Coordination weight 8% 44 / 100
~150 active validators per genesis-validators.md and Osmosis docs. Reported Nakamoto coefficient broadly comparable to Cosmos Hub range; top validators concentrated among professional operators. Client diversity weak: nearly universal CometBFT (no second consensus client).
Sustained quarterly major-version cadence (v17→v28) with several emergency / chain-halt-recovery upgrades historically (e.g. epoch-related halts in 2021-2022 resolved via coordinated patches). Strong execution muscle.
Osmosis Labs (engineering, Sunny Aggarwal CEO), Sikka (validator infrastructure co-founded by Aggarwal and Ojha), Osmosis Foundation. Clear named ownership. No named PQC migration lead for Osmosis. Co-founder Dev Ojha has publicly redirected to Zcash post-quantum scaling work, interpreted as PQ ownership not residing in Osmosis Labs.
Multiple chain-halt recoveries (epoch bug 2021, frontrunning-related halts) executed under time pressure. June 2022 frontend exploit ($5M LP-position drain) resolved with coordinated patch and reimbursement governance. Proposal 1007 (Hub integration) is contested high-stakes governance currently in motion. No precedent of a coordinated cryptographic-primitive change while under attacker pressure.
No canary, honeypot, rate-limited spending rule, or cryptographic tripwire on Osmosis.
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?
Verdict
X+Y > 2035, Outside risk window vs Z25; X+Y > 2030, Crisis Zone vs Z10
Z-compliance
Outside compliance window, OSMO and DEX flow face the 2035 disallowance for any classical PK still in active validator-key or account-signing scope
Source-disagreement disclosure
v3.1 requires every chain card to publish material divergences among authoritative sources, plus the delta-QRI under alternative weighting.
Proposal 1007 (passed on Osmosis side) would migrate Osmosis core modules into Cosmos Hub. If executed, Hub's PQ posture becomes controlling for what is today Osmosis-scope; if not, Osmosis remains an independent appchain with its own migration debt. Card scores Osmosis as a sovereign chain at evaluation date.
Osmosis runs CometBFT default (Ed25519, non-aggregating). Some Cosmos appchains (Babylon for Bitcoin-checkpoint multisig, Skip Protocol BLS variants) use BLS internally, that is appchain-scope, not Osmosis-scope. Osmosis itself has no BLS aggregation in consensus.
Delta-QRI under alternative weighting
Under a profile that weighted Dim 5 at 30% and Dim 6 at 30%, QRI would fall to ≈ 18 and Band would remain 2-3.
Announcement-to-shipped ratio
Announced: 0. Shipped: 0. Ratio: 0.
Tag: none
Peers in the L1 profile
9 chains closest to Osmosis by Stage then QRI.