# Why Viewing Keys?

A **viewing key** is a 32-byte secret returned by the Cloak SDK on every deposit.

It grants **read-only, scoped visibility** into the deposits made by a single project — without revealing destination wallets or breaking researcher privacy.

## The Core Tension

Privacy and compliance pull in opposite directions:

* **Pure privacy** breaks the audit trail accountants need
* **Pure transparency** exposes researchers to doxxing

Most privacy tools pick one side. Tirai does both — through viewing keys.

<figure><img src="/files/3HSOeJ2LjubVaDsfIqRV" alt="" width="563"><figcaption></figcaption></figure>

## What the Auditor Sees

When the auditor pastes the viewing key:

* Every payment the project ever made via Tirai
* Amount, date, label, and claim status for each entry
* A full ledger sufficient for compliance filing

What the auditor **cannot** see:

* The destination wallet of any claim
* The researcher's identity
* The on-chain transaction signature of the withdrawal

These fields are **structurally absent** from the SDK output — not hidden behind a flag or permission system.

## Per-Project Scope

Each viewing key is issued per project, not per researcher.

Properties:

* The project can rotate keys across audit periods (e.g. quarterly)
* A leaked key never exposes destination wallets — only metadata
* The auditor cannot use the key to claim or move funds

This makes viewing keys safe to share via email, encrypted DM, or compliance portal.


---

# 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-viewing-keys.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.