# Legal & Regulatory Layer

**Focus:** Adherence to legal requirements and standards.

**Objective:** Ensure compliance with relevant laws and regulations.

**Description:**  This layer governs the legal aspects of blockchain use and interoperability, including compliance with local and international laws, regulatory requirements, and oversight.

**Layer owner:**  National regulatory bodies, International organizations (e.g., Financial Action Task Force (FATF) for anti-money laundering (AML) and combating the financing of terrorism (CFT) regulations)

<br>

***

**Some considerations:**

* EU DLT Pilot Regime (DLTR) : <https://www.esma.europa.eu/sites/default/files/2023-10/ESMA12-2121844265-3182_Report_on_the_DLT_Pilot_Regime_-_Study_on_the_extraction_of_transaction_data.pdf>
* Abu Dhabi Global Market (ADGM) DLT Foundations Regime
* Legal Entity Identifiers (LEIs)
* A ‘Designated Depository’ role is important to satisfy regulatory obligations. Liability and recourse must be clearly addressed for cross-chain transfers. Issuer control & rights
* Public blockchains as an underlying settlement layer, how can this be supported in a secure and compliant manner.
* Regulatory clarity remains the market’s largest need.
* Ownership of an asset must be legally unambiguous at all times in order to ensure events such as interest payments can be correctly processed, making solutions dependent on technical ‘escrow’ functionality or terminology inappropriate
* Onboarding of Users: This would be conducted only by Institutions that are regulated entities. All users of the scheme will be KYC’d.
* Data Privacy: Records and operations would be conducted in the partition operated by an Institution are intended to be private to that institution. Only the parties involved in a transaction would have transaction visibility.
* FATF Recommendations: Payments would include necessary information of the parties involved in the payments chain through the messaging layer that carries the information associated with each settlement.
* Sanctions: Participating institutions would sanctions check all transactions according to the applicable lists through the messaging layer.
* Anti-Money Laundering: participating institutions would conduct AML monitoring through the messaging layer.
* Fraud: All customer instructions would be authenticated using Strong Customer Authentication (SCA) to reduce the likelihood of fraud.
* Transaction Limits: These would be maintained by each participating institution and may be enforced through smart contracts.

\------------------

Related to tokenization:

1. Providers take full responsibility for tokenized products, ensure effective record-keeping, and demonstrate operational soundness.
2. Public-permissionless blockchains cannot be used without proper controls.
3. Disclosure on whether settlements happen on-chain or off-chain.
4. Providers must prove ownership of tokens at all times.
5. Have at least one competent staff member with relevant experience to operate/supervise tokenization arrangements and manage associated risks.
6. Meet all applicable product authorization requirements for the underlying investment product being tokenized.
7. Implement additional safeguards to address risks associated with tokenization.
8. Clearly disclose terms and details of tokenization arrangement to investors.
9. Comply with all existing regulatory requirements applicable to the underlying product.
10. Ensure intermediaries meet licensing requirements and are competent in tokenized products.
11. Conduct proper due diligence on agents distributing tokenized products.
12. Provide regular training to staff on tokenized products and arrangements.

<https://www.trisa.io/>

&#x20;


---

# Agent Instructions: 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:

```
GET https://qualitax.gitbook.io/interop/requirements/legal-and-regulatory-layer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.