> 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/4.-cryptographic-foundations-and-compliance-framework/4.6-native-compliance-architecture-erc-3643-mapping.md).

# 4.6 - Native Compliance Architecture (ERC-3643 Mapping)

Polarischain embeds regulatory requirements directly into the protocol layer. Rather than relying on upgradeable smart contracts or off-chain legal wrappers, compliance, identity verification, and asset transfer restrictions are enforced natively by every validator during transaction validation.The model is inspired by the **ERC-3643 (T-REX)** standard but implemented as a **protocol-enforced transaction pipeline**:

* **Identity Attestation:** KYC/AML status is represented as a BLAKE2b-256 hash of verified documentation, signed by an accredited identity provider or custodian using Dilithium2.
* **Transfer Restrictions:** Jurisdictional limits, accreditation thresholds, holding periods, and agent approval requirements are encoded as native policy flags attached to each asset registry entry.
* **Deterministic Enforcement:** Validators reject non-compliant transactions before they enter the DAG. No post-execution rollbacks, no contract-level workarounds, no gas-dependent rule application.

**Role-Based Access Control**

| Role               | Function                                                 | Cryptographic Binding                                    |
| ------------------ | -------------------------------------------------------- | -------------------------------------------------------- |
| **Issuer**         | Creates/manages asset registry entries                   | Dilithium-signed issuance + legal wrapper hash           |
| **Transfer Agent** | Approves restricted transfers, manages corporate actions | Policy-enforced signature with jurisdictional scope      |
| **Custodian**      | Holds keys, attests KYC/AML, signs compliance metadata   | HSM-backed Dilithium keys, MPC co-signing                |
| **Validator**      | Enforces compliance rules at consensus layer             | Committee-stake-weighted voting, slashing-bound uptime   |
| **Regulator**      | Read-only audit access, compliance reporting             | Permissioned observer node, zero-write, metadata-indexed |

Identity claims are not stored on-chain. Only cryptographic attestations, policy hashes, and compliance metadata commitments are persisted, preserving data minimization while enabling full regulatory traceability.


---

# 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/4.-cryptographic-foundations-and-compliance-framework/4.6-native-compliance-architecture-erc-3643-mapping.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.