> For the complete documentation index, see [llms.txt](https://wiki.privai.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.privai.cloud/tokenomics/token-gating-and-premium-modules.md).

# Token Gating and Premium Modules

PRIVAI uses token gating to control OS access. Future versions may introduce additional gating tiers for advanced modules, higher limits, or partner workflows.

### Current OS Access Gate

To enter the PRIVAI OS, a user must connect a Solana wallet and verify ownership by signing a message.

The wallet must hold at least:

```
1,000,000 $PRIVAI
```

The token gate checks the configured Solana mint:

```
Gc7QGptjL88oM8uzGTBKw8Zhnm2Gp3P73sYdf6zZpump
```

### Verification Flow

The access check is designed to avoid transactions.

1. User connects a Solana wallet.
2. Server issues a login challenge.
3. User signs a message.
4. Server verifies wallet ownership.
5. Server checks token holdings.
6. If the wallet clears the requirement, the OS unlocks.

**No token transfer is required** for login.

### Current Access Model

| User Type                  | Access                                                                                              |
| -------------------------- | --------------------------------------------------------------------------------------------------- |
| **Qualified token holder** | Can enter the PRIVAI OS.                                                                            |
| **Non-holder**             | Cannot enter the OS.                                                                                |
| **Admin wallet**           | Hidden server-side access path for operations and testing. This is not shown in the user interface. |

### Module Access Philosophy

The OS login is the primary gate.

Once a user enters the OS, modules should not repeatedly ask for token verification. This keeps the product usable and avoids a broken flow where every app behaves like a separate gate.

> **Ideal flow:** verify once, enter the OS, run modules according to the user's access tier.

### Potential Premium Tiers

Future versions may introduce module-level premium access.

| Tier                | Example Access                                                          |
| ------------------- | ----------------------------------------------------------------------- |
| **Base Holder**     | Core wallet, token, identity, and domain scans.                         |
| **Advanced Holder** | Deeper graph analysis, richer project reports, larger scan limits.      |
| **Power User**      | Watchlists, recurring monitoring, exports, and higher-volume workflows. |
| **Partner/API**     | Programmatic access or integrations for other projects.                 |

These tiers are not finalized.

### Premium Module Candidates

Potential future premium modules include:

* Multi-hop Wallet Graph Explorer.
* Scammer Cluster Detection.
* Token Launch Intelligence.
* Recycled Project Detector Deep Scan.
* Watchlists and Alerts.
* Exportable Evidence Timelines.
* Premium AI Project Reports.
* Browser Extension Safety Layer.
* Higher-limit Private Routing workflows.
* Advanced Case File exports.

### Current Active Utility

| Utility                      | Status                                                              |
| ---------------------------- | ------------------------------------------------------------------- |
| **OS access gate**           | Active at **1,000,000 $PRIVAI**.                                    |
| **Wallet OpSec modules**     | Active MVP modules.                                                 |
| **Token Intel modules**      | Active MVP modules with Solana-first coverage.                      |
| **Identity Defense modules** | Active MVP modules with provider-dependent breach data.             |
| **Private Routing modules**  | Active MVP modules for supported swap and bridge flows.             |
| **AI Analyst modules**       | Active for summaries, action plans, and security terminal guidance. |
| **Case Files export**        | Active browser-local export.                                        |


---

# 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, and the optional `goal` query parameter:

```
GET https://wiki.privai.cloud/tokenomics/token-gating-and-premium-modules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.