> For the complete documentation index, see [llms.txt](https://docs.naorisquantumprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.naorisquantumprotocol.com/technical-guide/post-quantum-cryptography.md).

# Post-quantum cryptography

## Signature scheme

The protocol uses post-quantum signature schemes — **Dilithium-5** — chosen to withstand attack by quantum computers as well as classical ones.

## Crypto-agility

Algorithm choices are expected to change as standards mature. The architecture treats cryptographic primitives as replaceable components:

* algorithms can be upgraded as standards change
* no costly infrastructure redesign is required
* systems remain adaptable to future threats

## Why now rather than later

The **harvest-now, decrypt-later** threat means waiting is itself a risk. Data captured today under classical encryption can be decrypted once quantum capability arrives. Verification and confidentiality therefore need to be quantum-resistant before that capability exists, not after.

## Standards alignment

Governments and standards bodies including **NIST** and the **White House** have initiated migration toward post-quantum cryptography. The protocol is built to align with that direction rather than to anticipate a proprietary alternative.


---

# 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://docs.naorisquantumprotocol.com/technical-guide/post-quantum-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.
