> For the complete documentation index, see [llms.txt](https://zenko.gitbook.io/zenko-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zenko.gitbook.io/zenko-whitepaper/zenko-l1/quantum-security.md).

# Quantum Security

Zenko Layer 1 is being developed with native support for **quantum-resistant cryptography**, addressing a critical and often overlooked vulnerability in current blockchain infrastructure. Most public blockchains today rely on cryptographic primitives such as **ECDSA** (Elliptic Curve Digital Signature Algorithm) and **RSA**, both of which are vulnerable to **Shor’s algorithm** — a quantum computing method capable of breaking their underlying mathematical assumptions in polynomial time.

Zenko takes a forward-compatible approach by embedding quantum-resilient systems into the chain’s core cryptographic stack, ensuring long-term integrity, wallet safety, and governance protection.

#### Threat Model

* **Signature Forgery**: Quantum adversaries could derive private keys from public keys exposed during on-chain interactions (e.g., when sending a transaction).
* **Retroactive Exploits**: Even if powerful quantum computers are years away, adversaries can harvest and store public keys today, then use future quantum capabilities to exploit historical data.
* **Multisig and DAO Risk**: Multisignature wallets, DAO contracts, and smart contracts relying on classical key aggregation are particularly vulnerable to quantum compromise.
* **Validator Attacks**: Consensus validators signing blocks with non-quantum-hardened keys may expose chain-level governance and consensus integrity.

#### Zenko’s Mitigation Strategy

**1. Post-Quantum Signature Schemes**

Zenko will support **quantum-secure signature algorithms** at the protocol level, such as:

* **CRYSTALS-Dilithium** (NIST finalist)
* **Falcon** (lattice-based, suitable for compact signatures)
* **Hash-based schemes** (e.g., XMSS or SPHINCS+) for cold storage applications

These algorithms are resistant to known quantum attacks and are part of the NIST post-quantum cryptography standardization effort.

**2. Dual-Key Account Infrastructure**

User accounts will support dual-key structures:

* **Classical Key Pair** (e.g., ECDSA/secp256k1) for legacy compatibility
* **Quantum-Resistant Key Pair** for signing future transactions and recovering assets

During the migration period, both key types can co-exist with support for **gradual key rotation** and fallback mechanisms to quantum-safe paths.

**3. Quantum-Hardened Validator Keys**

All validator nodes on Zenko will be required to operate using **post-quantum secure validator keys** as a protocol-enforced requirement. Consensus messages, block signatures, and vote attestations will be verifiable using lattice-based or hash-based schemes.

This ensures that no critical consensus function remains vulnerable to private key recovery or signature forgery.

**4. ZK-SNARK-Compatible Attestation**

Zenko will support zero-knowledge proofs for attestations and quantum-safe signature verification, allowing off-chain generation of complex post-quantum cryptographic logic that can be verified on-chain without revealing internal structure.

This reduces the cost and size limitations typically associated with quantum-safe algorithms.

**5. Future-Proofing Governance**

Zenko’s DAO voting mechanisms will adopt **quantum-resistant voter authentication**, allowing governance participants to submit proposals and cast votes securely without exposing classical cryptographic weaknesses.

Multi-sig treasuries and upgrade permissions will migrate to quantum-safe schemes as part of the validator onboarding roadmap.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zenko.gitbook.io/zenko-whitepaper/zenko-l1/quantum-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.