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

# Security Design

### **Security Design: Quantum-Resilient from the Ground Up**

#### Post-Quantum Cryptographic Foundation

All core operations (hashing, log anchoring, key exchange simulations) use **quantum-safe primitives**, including:

* **Hashing**: SHA3-512, BLAKE3
* **Simulated Signature**: SPHINCS+ (in roadmap), Dilithium (simulated node signing)
* **Merkle Trees**: For audit trail integrity, updated per batch
* **Key Agreements**: Simulated use of Kyber-style logic

This positions NovaQ to operate securely even in a **post-quantum adversarial landscape**.

#### Simulated Secure Enclaves

While NovaQ operates initially as a simulation layer through bots and light clients, its model verifier is **TEE-aware** and replicates trusted loading conditions:

* Mimics SGX-style memory constraints
* Simulates measurement hashing for model files
* Generates “attestation receipts” bound to project identifiers

#### Multi-Checkpoint Protocol (MCP)

MCP is NovaQ’s internal **decentralized integrity simulation** — validating models across three or more simulated verification nodes (“Checkpoints”):

* Each checkpoint logs the hash of the model, timestamp, and loading behavior
* Nodes cross-verify state snapshots and sign Merkle roots
* Clients receive an **Attestation Summary** with trust grade, node agreement rate, and quantum-resilience score


---

# 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://novaq-docs.gitbook.io/novaq/novaq-protocol/security-design.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.