> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/protocol/status.md).

# Audits and status

## Audits

Audit reports are listed here as they are published, with the firm, the scope and the date. The scope covers the vault layer, the position adapter and the token layer, with the pool hook reviewed on its own.

| Report    | Firm | Scope | Date |
| --------- | ---- | ----- | ---- |
| *pending* |      |       |      |

## Source

The contracts are Solidity 0.8.28 built with Foundry. Source is verified on the explorer at every deployment, so the bytecode at each address on [Contract addresses](/protocol/addresses.md) can be checked against the repository.

Every invariant on [Security invariants](/protocol/invariants.md) is a test in the suite, which runs on every commit: unit and fuzz tests against tokens that can pause, blocklist and charge transfer fees, invariant tests with a handler that exercises every external function, and fork tests against the live chain.

## Who holds what

* **Nobody** holds a key to user funds. The vault has no owner and no upgrade path.
* **A 2-of-3 Safe** owns the registry, the fee sink's route switch, and the weekly epoch rates. Every value it can set has a compile-time bound. A timelock is added after launch.
* **The deployer** has no authority once the deployment is wired and ownership has moved to the Safe.

## Reporting a vulnerability

Write to the team on [X](https://x.com/gagecash) and ask for a private channel. Do not post details publicly. A disclosure programme with its scope and rewards is published here when it opens.

## Licence

The source licence is decided before launch and recorded in every file's header.


---

# 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://docs.gage.cash/protocol/status.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.