> For the complete documentation index, see [llms.txt](https://docs.zipper.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zipper.trade/security-and-compliance/compliance-mechanisms.md).

# Compliance Mechanisms

<figure><img src="/files/YJx5qVNTa9dmavnUAbQw" alt=""><figcaption></figcaption></figure>

### **Compliance Mechanisms**

Zipper integrates **two key compliance mechanisms** to ensure a secure, transparent, and trustless asset zipping (wrapping) and unzipping (unwrapping) process:

1. **On-Chain Transaction Monitoring** - Detecting and preventing interactions with illicit or sanctioned funds.
2. **Immutable Smart Contracts** - Ensuring Zipper remains secure, non-custodial, and resistant to external interference.

These mechanisms **work together** to **mitigate risk, maintain regulatory integrity, and build trust** among users and developers alike.

***

### **1. On-Chain Transaction Monitoring**

Zipper employs a **third-party chain monitoring service** to scan all transactions for compliance violations, including:

✅ **Sanctioned Wallets** - Blocking addresses flagged under **OFAC (Office of Foreign Assets Control)** or similar regulatory frameworks.\
✅ **Illicit Activity** - Identifying wallets linked to **hacked, stolen, or blacklisted funds**.\
✅ **Anti-Money Laundering (AML) Measures** - Monitoring suspicious transaction patterns and blocking high-risk transfers.

#### **How It Works**

* Chain monitoring services **run real-time checks** on deposit and withdrawal transactions.
* If a transaction **involves a flagged address**, the transfer is automatically **rejected and flagged for further review or returned the originator**.
* This system **protects Zipper from becoming a vehicle for illicit financial activity** while allowing legitimate users to transact.

#### **Why This Matters**

🔹 **Ensures Zipper remains compliant** with global financial regulations.\
🔹 **Prevents stolen assets from being laundered** through the protocol.\
🔹 **Increases user confidence** by maintaining a secure and trusted environment.

{% hint style="info" %}
**Important:** Zipper **does not collect user data** or interfere with transactions beyond these compliance checks. The system operates at the **protocol level**, ensuring neutrality while enforcing security measures.
{% endhint %}

### **2. Immutable Smart Contracts**

Zipper's **smart contracts are immutable**, meaning they **cannot be modified, upgraded, or altered** after deployment. This immutability is a **key compliance mechanism** because it ensures that:

✅ **The contract logic remains trustless** - No entity (including developers) can change how Zipper operates post-deployment.\
✅ **Users are fully protected from governance takeovers** - No centralized group can introduce new permissions, backdoors, or exploits.\
✅ **Regulatory transparency is enforced** - The protocol operates under **fixed, predictable conditions**, eliminating concerns about external manipulation.

#### **How It Works**

* Once Zipper contracts are **deployed and verified**, they **cannot be altered or upgraded**.
* Any changes to how Zipper functions **would require deploying an entirely new version**, ensuring that existing contracts remain untouched.
* This model **protects users from unexpected risks**, ensuring **the same rules apply to all participants at all times**.

#### **Why This Matters**

🔹 **Prevents centralized control over user funds.**\
🔹 **Eliminates the risk of malicious contract updates.**\
🔹 **Ensures Zipper remains decentralized, predictable, and censorship-resistant.**


---

# 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.zipper.trade/security-and-compliance/compliance-mechanisms.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.