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

# Quantum-resistant cryptography

Data stolen today may be stored until future computing advances make older public-key systems easier to break. This is commonly called a **harvest-now, decrypt-later** risk.

Cifer addresses that risk with a post-quantum key-establishment design rather than relying only on RSA or elliptic-curve cryptography.

### Cryptographic components

| Purpose                        | Mechanism                  |
| ------------------------------ | -------------------------- |
| Post-quantum key encapsulation | ML-KEM-768                 |
| Data encryption                | AES-256-GCM                |
| Key derivation                 | HKDF-SHA-256               |
| Distributed custody            | 3-of-5 threshold fragments |

ML-KEM is standardized in NIST FIPS 203 and is designed to resist known classical and quantum attacks. AES-256-GCM provides authenticated symmetric encryption for protected data.

{% hint style="info" %}
The accurate public term is **quantum-resistant**, not “quantum-proof.” No responsible security architecture can promise resistance to every future cryptanalytic discovery or implementation failure.
{% endhint %}

### Crypto-agility

Algorithms and recommended parameters evolve. Cifer's architecture should keep algorithm selection versioned and replaceable so that a future migration does not require redesigning the complete custody and authorization model.

### What the claim means

“Quantum-resistant” means the design uses cryptography developed and standardized for resistance to known quantum attack methods. It does not guarantee perpetual security. Security still depends on implementation quality, randomness, endpoint protection, execution-environment security, correct policy enforcement, and timely upgrades.


---

# 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://cifer.gitbook.io/cifer-docs/network-whitepaper/quantum-resistant-cryptography.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.