QuantumShield PQC

< 1K installs


Category

Developer

QuantumShield

Identifier

@quantumshield-js/snap
See details

Description by QuantumShield PQC

QuantumShield PQC Snap brings post-quantum cryptography to MetaMask. It implements ML-DSA-65 (NIST FIPS 204, Security Level 3) — a lattice-based digital signature algorithm standardized by NIST in August 2024 to resist attacks from both classical and quantum computers. Quantum computers running Shor's algorithm will eventually break the ECDSA signatures that secure every Ethereum wallet today. QuantumShield prepares users for this threat by adding a second, quantum-resistant signature layer on top of the existing ECDSA infrastructure. What this Snap does: Key Generation — Generates ML-DSA-65 key pairs (1,952-byte public key, 4,032-byte private key) inside the Snap's isolated storage. Private keys never leave the Snap environment. Users can generate multiple labeled key pairs and manage them independently. Hybrid Signing — Creates dual signatures that combine ECDSA (classical) and ML-DSA-65 (post-quantum) into a single 3,375-byte payload. A transaction is only valid when both signatures verify. This means security is maintained even if either algorithm is compromised individually. PQC-Only Signing — For scenarios where ECDSA is considered compromised, the Snap can produce ML-DSA-65-only signatures (3,310 bytes) that bypass ECDSA entirely. Signature Verification — Verifies the ML-DSA-65 component of both hybrid and PQC-only signatures locally within the Snap. Key Management — List, inspect, export, and delete key pairs. Key import is supported with automatic integrity verification (sign-and-verify check on import). Public key export enables on-chain registration with QuantumShield L2 smart accounts. This Snap is designed for use with QuantumShield L2, an OP Stack-based Layer 2 that includes an on-chain ML-DSA-65 verification precompile. However, the key generation and signing functionality works independently — any dApp can integrate post-quantum signatures by calling the Snap's RPC methods. Permissions used: snap_dialog (user confirmation before key generation, signing, and export), snap_manageState (encrypted key storage), snap_notify (operation notifications), endowment:rpc (dApp communication). No network access is required. All cryptographic operations are performed locally using the @noble/post-quantum library, a JavaScript implementation audited and maintained by Paul Miller.

Permissions by QuantumShield PQC

  • Allow websites to communicate with QuantumShield PQC

  • Allow https://quantumshield.xyz to communicate with QuantumShield PQC

  • Display dialog windows in MetaMask

  • Store and manage its data on your device

  • Show notifications


Related Snaps

See all

Start exploring blockchain applications in seconds. Trusted by over 30 million users worldwide.

About

  • Website
  • Developer docs

Get in touch

You acknowledge that any Snap that you install is a Third Party Service, unless otherwise identified, as defined in the Consensys terms of use. Your use of Third Party Services is governed by separate terms and conditions set forth by the Third Party Service provider. Consensys does not recommend the use of any Snap by any particular person for any particular reason. You access, rely upon or use the Third Party Service at your own risk. Consensys disclaims all responsibility and liability for any losses on account of your use of Third Party Services. Any information you share with Third Party Services will be collected directly by those Third Party Services in accordance with their privacy policies. Please refer to their privacy policies for more information. Consensys has no access to information you share with Third Party Services.

©2026 MetaMask. All rights reserved. Privacy policy & Terms of use