Adversaries are harvesting encrypted blockchain data today to decrypt once quantum computers reach cryptographic relevance. Shamwari has been quantum-safe since genesis block zero — no legacy ECDSA history, no retroactive exposure, no migration required.
This is not a 2030 problem. It is a 2024 problem that will manifest in 2030. Nation-state adversaries are actively capturing and archiving encrypted blockchain traffic today — every transaction, every identity proof, every certificate — with the explicit intent to decrypt it once a cryptographically relevant quantum computer exists.
Intelligence agencies operate dedicated programmes to capture and archive encrypted internet traffic. Blockchain transactions — public by design and broadcast globally — are the highest-value targets. Every hash, signature, and public key ever broadcast to a peer-to-peer network is permanently archived.
Financial records, identity proofs, and transaction histories created today will be decryptable by future quantum computers. For a chain that launches PQC in 2028, every transaction from 2015 to 2028 — years of user activity, institutional flows, and identity data — is permanently compromised.
For financial institutions holding sensitive user data on blockchain infrastructure, deploying quantum-safe cryptography is no longer optional. NIST, the European Union, and major central banks have all issued guidance requiring PQC migration. 2026 fiduciary standards require action, not planning.
Shamwari deploys a complete post-quantum cryptographic stack covering digital signatures, key encapsulation, symmetric encryption, and wallet key derivation. Every operation at every layer uses a NIST-standardised or NIST-compatible algorithm.
Every Shamwari account's public identity is a combined 2112-byte structure: 800 bytes of Kyber-512 encryption public key concatenated with 1312 bytes of Dilithium-2 signing public key. This combined key is stored in the block header for forgers and in the account table for all participants.
Every forged block carries a 2420-byte ML-DSA-2 (Dilithium Level 2) signature over the full block header. This is the quantum-resistant proof that a specific forger with a specific stake committed to this specific block content at this specific height. Verification is deterministic on every node.
Both Dilithium and Kyber are built on the hardness of Module Learning With Errors (MLWE); a lattice problem for which no efficient quantum algorithm is known. Shor’s algorithm, which breaks ECDSA and RSA in polynomial time on a quantum computer, has no known application to lattice problems. NIST reviewed all known quantum attacks and standardised both algorithms in 2024.
ML-DSA (Module Lattice-Based Digital Signature Algorithm) is NIST FIPS 204, finalised in 2024. It is the primary signature algorithm for all Shamwari blockchain operations from individual transaction signing to block production by forger nodes.
Shamwari uses the Level 2 parameter set, which targets NIST security category 2 comparable to AES-128 against both classical and quantum adversaries. This balances signature size, key size, and signing/verification performance for high-throughput blockchain operation.
Dilithium signatures (2420B) are larger than ECDSA (64B). This is an acceptable trade-off for financial infrastructure. A 10MB block at ~12-second intervals accommodates thousands of transactions. The security guarantee is significant: no quantum attack, no migration risk, no retroactive exposure which justifies the storage overhead at any financial transaction volume.
ML-KEM (Module Lattice-Based Key Encapsulation Mechanism) is NIST FIPS 203, finalised in 2024. It is used across all Shamwari ecosystem to encrypt sensitive on-chain data ensuring that account identities, purchase payloads, and insurance metadata remain confidential even if the encrypted ciphertext is captured and archived today.
Kyber is a Key Encapsulation Mechanism which encapsulates a symmetric key, not the data directly. The pattern is: (1) use Kyber KEM to establish a shared secret with the recipient's public key, (2) use that shared secret as an AES-256 key to encrypt the actual payload. This hybrid approach gives both the quantum resistance of Kyber and the performance of AES-256 for data.
Shamwari uses ML-KEM-512 (the Level 1 parameter set), which targets NIST security category 1 comparable to AES-128 against both classical and quantum adversaries. This is the right choice for data encryption where the value of the data does not need 30+ years of quantum-resistant protection, while maintaining excellent performance for high-volume on-chain storage.
Shamwari adapts the familiar BIP39 mnemonic standard for post-quantum key derivation. The same 12/15/18/21/24 word seed phrase that users already know from Bitcoin and Ethereum wallets now derives two NIST-standard post-quantum keys; the Dilithium signing key and Kyber encryption key with no additional complexity for the user.
Only public keys are stored on-chain. The combined 2112-byte generator public key (Kyber 800B + Dilithium 1312B) is written to the account record when first activated. Public keys are public by design — their security comes from the hardness of the lattice problem, not from secrecy.
Private keys are held exclusively by the account holder in the wallet application or hardware device. They are used to sign transactions (Dilithium) and decrypt received data (Kyber). The Shamwari protocol never requests, stores, or transmits private keys.
ShamwariCertificate extends java.security.cert.Certificate directly; the standard Java certificate interface. Any JVM application that currently accepts X.509 certificates accepts Shamwari certificates without modification, while gaining post-quantum security underneath.
Issue verified identity credentials that any chain participant verifies on-chain. KYC data Kyber-encrypted — verifiable without exposing underlying identity information to third parties. Institution-issued, blockchain-anchored, quantum-resistant.
Central Banks issue operating licences as on-chain certificates with block-height expiry. Licence status is verifiable by any counterparty in real time. No third-party registry, no manual verification phone call, no risk of stale data.
Node operators use Shamwari certificates for TLS mutual authentication. Accepted natively by JVM-based infrastructure without custom certificate authorities. Quantum-safe TLS for all inter-node communication in the Shamwari network.
The quantum threat to blockchain cryptography is not binary. It is a rolling window of increasing risk, where the value of currently-captured data increases as quantum computing capabilities advance. Shamwari has zero exposure at any point on this timeline.
Quantified security parameters for the Shamwari cryptographic stack. All values reference the deployed parameter sets as implemented in the protocol codebase.
Deploy applications on the only blockchain that has been quantum-safe from its first block.