# Why Cloak Shield Pool?
## Why this section matters
Explains *why Tirai is non-trivial to build*.
Solana is a public, transparent ledger.\
Smart contracts cannot natively hide:
* The link between a deposit transaction and a withdrawal transaction
* The recipient address of a private transfer
* The relationship between a project's treasury and its researchers
* The amount paid in a bounty payout
The **Cloak Shield Pool** enables Tirai to:
* Generate **Groth16 zero-knowledge proofs** for both deposits and withdrawals
* Maintain a **Poseidon Merkle tree** of UTXO commitments inside the pool
* Issue **per-deposit viewing keys** that scope audit visibility
* Allow withdrawals to **arbitrary recipient addresses** chosen at claim time
This allows Tirai to safely route bounty payouts through a shielded primitive without centralized trust or custodial risk.
## Why Generic Mixers Don't Fit
Without Cloak, Tirai would need to rely on:
* **Generic mixers** — blanket-banned in most jurisdictions, no project-scoped audit trail
* **Trusted relayers** — reintroduces the centralized trust we are trying to remove
* **Custodial platforms** — incompatible with self-sovereign whitehat workflows
Cloak replaces all three with a single, audit-friendly primitive.
---
# 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://moai-3.gitbook.io/tirai-frontier/mission/why-cloak-shield-pool.md?ask=
```
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.