> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/introduction/compliant-by-design.md).

# Compliant by design

***

### 1. Token-Level Enforcement (ERC-3643)

Unlike general-purpose blockchains that rely on simple wallet whitelisting, T-REX enforces compliance directly within the smart contract logic of the asset thanks to the T-REX Protocol (ERC-3643).

* Embedded KYC/AML: Every transfer triggers a real-time check against the OnchainID identity registry.
* Modular Rule Engine: Issuers can program specific restrictions based on jurisdiction, investor type (e.g., Accredited vs. Qualified), holding periods, etc.
* The "Golden Record": The T-REX Ledger maintains the definitive book of record for ownership, ensuring that even when assets move cross-chain, the compliance rules remain intact and non-bypassable.

***

### 2. Infrastructure & Sequencer Security

The T-REX Ledger is powered by a production-grade OP Stack deployment, managed via a professional team to ensure institutional-grade reliability and security.

* **Institutional PoA Consortium**: The network is operated by a consortium of regulated financial institutions and Tier-1 Web3 corporates who serve as Proof-of-Authority (PoA) validators, co-signing key network events.
* **Sequencer-Level Screening**: Compliance starts at the gateway. The sequencer will include OFAC-configurable ingress screening and AI-powered detection to identify and block suspicious behaviors or known bad actors before they reach the execution layer.
* **Guardian Role**: To mitigate critical security incidents, T-REX authorized engineers hold a "Guardian" role, providing the ability to pause L1 withdrawals in the event of a vulnerability or hack.

***

### 3. Curated AppStore Excellence

Compliance extends to the tools and services interacting with the ledger. The T-REX AppStore is a gated ecosystem.

* **Vetted Providers**: Only "Institutional Grade" providers who pass the T-REX Committee's five-dimensional vetting process (Utility, Business Model, Security, Compliance, and Reliability) are listed.
* **Verified Badge**: Approved applications receive the "T-REX Certified" badge, ensuring they meet global securities regulations and technical standards.
* **Non-Circumvention**: Providers are legally bound to maintain high SLAs and strict data protection standards (GDPR/PIPA).

***

### 4. Regulatory & Legal Framework

T-REX is structured to provide legal certainty for the world's largest asset managers.

* **Bermuda DABA License (pending approval)**: The network operator (Digital Asset Operational Services ISAC Ltd.) is seeking a Digital Asset Business Act (DABA) license from the Bermuda Monetary Authority (BMA), covering issuance, custody, and exchange operations.
* **MiCA Compliance**: We are filing a MiCA whitepaper in the EU to ensure the upcoming utility token is compliant for admission to trading across the European Union.
* **Clear classification**: The utility token will be strictly a utility token for gas, governance, and service credits, separate from the security tokens it settles.
* **Permissioned Settlements**: We are currently evaluating the integration of permissioned stablecoins and native cash legs like USD1 to ensure the entire transaction lifecycle, from gas to settlement, remains within a regulated perimeter.

***

### 5. Privacy without Anonymity

Through our partnership with Zama, T-REX will offer optional Fully Homomorphic Encryption (FHE).

* **Confidential Transfers**: Institutions can keep balances and transaction details encrypted while still allowing smart contracts to perform compliance checks.
* **Programmable Decryption**: Regulators can be granted "view keys" for specific data, enabling oversight without exposing sensitive commercial information to the public.


---

# 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.t-rex.network/introduction/compliant-by-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.
