> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/9.-native-compliance-framework-erc-3643/9.3-quantum-resistant-identity-claims.md).

# 9.3 - Quantum-Resistant Identity Claims

Claims are cryptographically signed attestations issued by trusted entities. Each claim binds five protocol-enforced fields:

1. **Topic ID:** Verification category (KYC, AML, accredited status, etc.)
2. **Issuer Address:** Authorized entity that produced the claim
3. **Signature:** `CRYSTALS-Dilithium2` signature over the claim body
4. **Data Hash:** `BLAKE2b-256` digest of off-chain verification records
5. **Expiry Timestamp:** Automatic re-verification trigger

Unlike legacy ERC-3643 implementations reliant on ECDSA, Polarischain’s Dilithium2-signed claims provide **quantum-resistant identity proofs**, protecting long-lived regulatory attestations against future cryptographic compromise.


---

# 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://polarischain-1.gitbook.io/polarischain/9.-native-compliance-framework-erc-3643/9.3-quantum-resistant-identity-claims.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.