# Why Off-Chain Tickets?
A **claim ticket** is an opaque base58 blob that encodes the UTXO commitment plus its spending key.
In Tirai, every bounty payout produces exactly one ticket — handed from the project to the researcher **outside the blockchain**.
## Why Not On-Chain?
Putting the ticket on-chain would defeat the entire purpose of the Shield Pool.
If the ticket lived on-chain:
* Anyone could observe **which deposit** was destined for **which researcher**
* The deposit ↔ withdrawal edge becomes visible again
* Privacy collapses to the level of a regular Solana transfer
The ticket must travel **only between the project and the researcher**, never through any public channel.
## What Tickets Enable
Off-chain tickets unlock three core Tirai behaviors:
* **Out-of-band delivery** — Telegram, Signal, email, or any private channel
* **Trial-decryption preview** — researcher can inspect the ticket locally without broadcasting any transaction
* **One-time-use semantics** — once claimed, the underlying UTXO is consumed and the ticket becomes invalid
Tirai never persists tickets — not in Supabase, not in the auth-server, not in browser local storage past the success card.
---
# 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-off-chain-tickets.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.