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

# Institutional Compliance

The Dilemma

Privacy protocols often face a critical failure mode: they become safe havens for illicit actors. When a mixer is used by hackers or sanctioned entities, the entire liquidity pool becomes "tainted," making it unusable for legitimate users and institutions.

**TSS solves this with Zero-Knowledge Compliance (ZK-C).**

#### Our Solution: Proof of Innocence

We utilize a proprietary ZK-SNARK circuit to enforce a "Blacklist Check" *without* revealing the user's identity. This allows the protocol to remain **permissionless** for good actors while being **impenetrable** to bad actors.

#### The Mechanism

1. **The Blacklist:** The protocol maintains an on-chain Merkle Tree containing addresses linked to illicit activity (e.g., OFAC sanctions list, known exchange hacks).
2. **Client-Side Proving:** Before a deposit is accepted, the user's browser generates a Zero-Knowledge Proof locally.
3. **The Assertion:** This proof cryptographically asserts:

   > *"I certify that the source of these funds is NOT included in the current Blocklist Merkle Tree."*
4. **On-Chain Verification:** The smart contract verifies this proof. It receives a simple `True` or `False` signal.

#### The Result

* **For the User:** You prove your funds are clean without ever revealing *who* you are.
* **For the Protocol:** The anonymity set remains "compliant," ensuring that withdrawing funds from TSS does not flag your wallet at exchanges or banks.

#### Dynamic Updates

The TSS Governance module allows $TSS token holders to vote on updates to the Blacklist Merkle Root, ensuring the protocol can adapt to new threats in real-time without centralized control.

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


---

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

```
GET https://docs.thesecretservice.io/protocol-architecture/compliance.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.