# Compliance Bridge: Trust for Institutional DeFi

Every **DeFi founder** knows the appetite is there. **Pension funds, insurers, and sovereign wealth funds** want exposure to **yield, tokenized assets, and new liquidity** venues. But one high-profile failure could close the door for the entire sector.

The real obstacle isn’t technology. It’s **trust**.

#### The Risks

* **AML gaps**: Funds moving through pools without clarity on source of funds.
* **Sanctions evasion**: Blacklisted wallets sneaking in, sanctioned countries or individuals participating
* **Auditability**: Regulators demand clear trails, but DeFi often provides opacity.

#### Why This Matters

Institutions aren’t waiting for “perfect” regulation—they’re waiting for **credible guardrails**. Without them:

* Banks can’t custody assets.
* Funds can’t allocate capital.
* Regulators can shut doors overnight.

#### The Bridge: Verify → Prove → Access

```mermaid
flowchart LR
    A[Institution defines KYC/AML policy] --> B[Users complete KYC with provider]
    B --> C[Vault stores commitments + ZK proof]
    C --> D[Identity Token issued]
    D --> E[dApp checks eligibility]

```

* Define → Institutions define rules and users complete KYC with trusted providers.
* **Prove** → Fairway vaults turn KYC data into ZK-proofs (no raw PII on-chain).
* **Access** → Identity tokens unlock compliance-gated DeFi participation.

#### Tools

* **KYC Vaults** (off-chain storage + ZK commitments).
* **Identity Proofs** (Merkle trees / ERC-3643 style).
* **Policy Engines** (programmable eligibility checks).

**Takeaway Framework: The 3-Steps for users**

{% stepper %}
{% step %}

### Verify once

Users go through traditional KYC process
{% endstep %}

{% step %}

### Prove without revealing

They gain a proof that can be connected to multiple wallets and used to prove eligibility
{% endstep %}

{% step %}

### Access everywhere

Same proofs will be accepted on any DeFI
{% endstep %}
{% endstepper %}


---

# 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://docs.fairway.global/learn/compliance-and-risk-management-guides/compliance-bridge-trust-for-institutional-defi.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.