# Flywheel

## Tirai Privacy Flywheel

```mermaid
stateDiagram-v2
    direction LR
    [*] --> Whitehats
    Whitehats: 1. Whitehats Trust
    Projects: 2. Projects Bounties
    Volume: 3. Higher Volume
    Privacy: 4. Stronger Privacy
    Auditor: 5. Auditor Adoption
    Ecosystem: 6. Ecosystem Adoption
    
    Whitehats --> Projects
    Projects --> Volume
    Volume --> Privacy
    Privacy --> Auditor
    Auditor --> Ecosystem
    Ecosystem --> Whitehats: loop stronger

```

{% stepper %}
{% step %}

### More Whitehats Trust the Platform

When researchers see that Tirai produces **structurally unlinkable payouts**:

* They stop demanding fresh wallets through awkward off-chain negotiations
* They report bugs faster, knowing payouts are private by default
* They engage with smaller projects that previously could not offer privacy

**Impact:** Each new researcher reduces friction in future bounty programs.
{% endstep %}

{% step %}

### More Protocols Post Bounties

As researcher trust grows:

* Protocols experience **higher whitehat engagement**
* Bug reports arrive faster and through more legitimate channels
* Compliance teams approve bounty programs they previously blocked

**Assumption (conservative):**

* A 10% increase in active researchers leads to a 15–20% increase in bounty programs, driven by reduced trust friction.
  {% endstep %}

{% step %}

### Higher Bounty Volume

More bounties posted result in:

* More on-chain Cloak transactions, strengthening the pool's anonymity set
* Larger Merkle tree, exponentially harder to de-anonymize via timing analysis
* More viewing-key audit traffic, validating the compliance model

**Observed effect:**

* Larger anonymity sets directly improve privacy guarantees for every participant
* Tirai earns optional fees only on premium org subscriptions, not on volume
  {% endstep %}

{% step %}

### Stronger Privacy Guarantees

A larger anonymity set means:

* Each individual payout becomes **statistically more private**
* Timing-based heuristics fail more often
* The Shield Pool becomes more valuable as core infrastructure

**Example:**

* Pool anonymity set of 100 deposits → meaningful privacy
* Pool anonymity set of 10,000 deposits → resistant to nearly all heuristic attacks
  {% endstep %}

{% step %}

### More Auditor Adoption

As audits prove the model:

* Compliance teams normalize privacy-by-default payouts
* Regulators accept viewing-key audits as valid evidence
* More organizations migrate from doxxable platforms to Tirai

**Assumption:**

* A 20–30% increase in audited bounty programs attracts new compliance-aware orgs and increases premium subscription conversions.
  {% endstep %}

{% step %}

### Ecosystem-Wide Adoption

With privacy normalized:

* Other Solana protocols integrate the Cloak Shield Pool
* White-label deployments emerge for DAOs and grants programs
* Tirai's UX patterns become the default for private payouts

**Flywheel restarts with higher baseline trust.**
{% endstep %}
{% endstepper %}

## Flywheel Metrics Snapshot

| Metric                | Effect                     |
| --------------------- | -------------------------- |
| +10% Researcher Trust | +15–20% Bounty Programs    |
| +20% Bounties         | +25% Pool Volume           |
| +25% Pool Volume      | Stronger Anonymity Set     |
| Stronger Anonymity    | +30% Auditor Adoption      |
| More Auditors         | More Premium Subscriptions |


---

# 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/business/flywheel.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.