> 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.5-consensus-level-compliance-enforcement.md).

# 9.5 - Consensus-Level Compliance Enforcement

Compliance validation occurs in the **core transaction processing pipeline**, executed by every validator prior to DAG inclusion. No application-layer workarounds or post-execution rollbacks exist.

**Pre-Transfer Validation Sequence**

Every regulated asset transfer triggers deterministic checks:

1. Sender and receiver wallets are **not administratively frozen**
2. Sender possesses **sufficient unfrozen balance**
3. Receiver is **registered in the Identity Registry**
4. Receiver holds **valid, unexpired claims** for all required topics from trusted issuers
5. Transfer complies with **asset-specific rules** (investor caps, geographic restrictions, holding periods)

If any condition fails, the transaction is rejected at consensus. Non-compliant payloads never enter the committed ledger.

**Configurable Compliance Parameters**

Asset issuers define enforcement rules at issuance time:

<table data-header-hidden><thead><tr><th width="318.17578125">Rule Type</th><th width="329.90625">Enforcement Scope</th></tr></thead><tbody><tr><td>Max Investor Count</td><td>Global &#x26; per-jurisdiction caps</td></tr><tr><td>Max Token Holding</td><td>Per-wallet balance limits</td></tr><tr><td>Geographic Restrictions</td><td>Country allowlists/blocklists (ISO-3166)</td></tr><tr><td>Minimum Holding Period</td><td>Time-based transfer locks post-acquisition</td></tr><tr><td>Volume Limits</td><td>Daily/monthly per-investor transfer thresholds</td></tr></tbody></table>


---

# 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.5-consensus-level-compliance-enforcement.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.