asset · quantum risk
Is ETH on Ink Quantum Proof?
Verdict
ETH on Ink is not quantum-proof. Ink authorizes ordinary user actions with classical secp256k1 ECDSA (typical EOAs). A CRQC running Shor’s algorithm threatens those keys when public keys are known. L2 deployment does not install NIST PQC by itself. ETH on Ink is controlled by the keys that sign spends on that network—classical unless the chain migrates authorization crypto.
Overview
Wave 7g matrix: “Is ETH on Ink quantum proof?” Separate **host-chain authorization** from **asset-specific operational risk** (issuer, bridge, wrap, protocol admins).
Ink authorizes ordinary user actions with classical secp256k1 ECDSA (typical EOAs). A CRQC running Shor’s algorithm threatens those keys when public keys are known. L2 deployment does not install NIST PQC by itself.
ETH on Ink is controlled by the keys that sign spends on that network—classical unless the chain migrates authorization crypto.
Link the ETH dossier and Ink hub to inventory keys without treating multi-chain brands as one cipher. Educational only—not investment advice.
Cryptographic profile
- Signatures: ECDSA-secp256k1 (EOAs on L2)
- Hash: Keccak-256
- Public-key exposure: User/account keys on Ink control ETH here; plus issuer/bridge/protocol roles for ETH.
- Wave 7g matrix pair: eth-on-ink
- Host family: evm-secp256k1
- Asset role: gas
What breaks
- Classical signatures on Ink controlling ETH transfers
- Hot wallets and exchange deposit practices for this pair
- Protocol admin or bridge keys if this deployment is bridged
- Assuming another chain’s PQC roadmap automatically applies here
Mitigations
- Inventory every wallet that holds ETH specifically on Ink
- Read host hub /is-quantum-proof/ink and asset pages /crypto/eth / /is-quantum-proof/ethereum
- Map bridges if balances move across domains
- Hardware/MPC for treasuries; limit unlimited approvals on EVMs
- Open /is-quantum-proof/wrapped-assets and /is-quantum-proof/host-chain-matrix for navigation
FAQ
Is ETH on Ink quantum-proof?
ETH on Ink is not quantum-proof. Ink authorizes ordinary user actions with classical secp256k1 ECDSA (typical EOAs). A CRQC running Shor’s algorithm threatens those keys when public keys are known. L2 deployment does not install NIST PQC by itself. ETH on Ink is controlled by the keys that sign spends on that network—classical unless the chain migrates authorization crypto.
Does an L2 or wrap make ETH safer against quantum computers?
Most EVM hosts share secp256k1 user authorization. L2s add operator/bridge surfaces—they are not post-quantum wallets.
What should I inventory first?
Wallets holding ETH on Ink, any bridge/wrap path used to arrive, and issuer or protocol controls when relevant.
Key concepts (technical dictionary)
Terms used on this page — open a definition: