> For the complete documentation index, see [llms.txt](https://docs.lacunalabs.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lacunalabs.xyz/security-and-compliance/proof-of-innocence.md).

# Proof Of Innocence

Prove funds aren't from illicit sources.

> Proof Of Innocence is part of Lacuna's roadmap and is not yet live. The design is described here; the on-chain components ship in a later phase.

## The Idea

Proof Of Innocence (POI) will let a user cryptographically prove that their funds are *not* associated with known illicit sources without revealing their identity or full history.

## How It Will Work

Using association sets (sets of "known-good" deposits), a user can generate a proof that their funds belong to an approved set, or that they exclude links to flagged sources. This gives honest users a way to demonstrate legitimacy while preserving privacy.

## Why It Matters

POI is the bridge between strong privacy and real-world acceptance privacy that doesn't require trusting the protocol to police anyone, because users prove their own innocence on their own terms.

See the [Roadmap](/resources/roadmap.md) for phasing.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lacunalabs.xyz/security-and-compliance/proof-of-innocence.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
