> 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/security-and-audits.md).

# Security & Audits

The security model, and what's done versus pending.

Security is foundational to a privacy protocol, if the cryptography or the contracts are wrong, privacy fails.

## What's Been Done

Lacuna's full stack smart contracts, mobile wallet, and relayer backend has undergone a comprehensive security review covering the contracts, cryptographic flows, key storage, and the client–relayer protocol.

## Ongoing Hardening

A re-audit covering fully on-device proof generation is part of the path to mainnet. Items still being strengthened on-device proving, anonymity-set growth, and relayer decentralization are tracked transparently on the [Roadmap](/resources/roadmap.md).

## Our Approach

* Standard, audited cryptographic primitives (Groth16 verifiers).
* Reentrancy protection and safe transfer patterns in the contracts.
* No custodial backend that can move user funds.

We publish what's done and what's pending, no overclaiming.


---

# 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/security-and-audits.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.
