> 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/ecosystem-components/wallet-opsec.md).

# Wallet OpSec

Wallet OpSec modules help users understand what a wallet reveals publicly and which wallet-level risks may need attention before they connect, sign, or trade.

## What It Helps Answer

* What can someone infer from this wallet's public activity?
* Which recent counterparties or contracts appear in the wallet history?
* Are there token accounts with risky delegates, close authorities, or freeze states?
* Does the wallet expose patterns that should be reviewed before further use?

## Active Modules

| Module                    | Purpose                                                                                     | Status     |
| ------------------------- | ------------------------------------------------------------------------------------------- | ---------- |
| **wallet\_exposure.scan** | Reviews wallet identity exposure, balances, token accounts, and recent transaction signals. | MVP active |
| **wallet\_graph.map**     | Builds a one-hop public counterparty map from recent wallet transactions.                   | MVP active |
| **approval\_risk.scan**   | Checks Solana token account delegates, close authorities, and frozen accounts.              | MVP active |

## Report Focus

Wallet reports should be practical and readable. The goal is to help users understand:

* High-risk approvals or account authorities.
* Suspicious or unfamiliar counterparty activity.
* Public behavior patterns that may reduce privacy.
* Follow-up actions that improve wallet hygiene.

## Current Limits

| Area                | Current Limit                                                      |
| ------------------- | ------------------------------------------------------------------ |
| **Chain support**   | Solana-first. Ethereum enrichment exists only where configured.    |
| **Graph depth**     | Current graphing is one-hop. Multi-hop cluster scoring is planned. |
| **False positives** | Wallet risk signals require human review and context.              |


---

# 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/ecosystem-components/wallet-opsec.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.