> For the complete documentation index, see [llms.txt](https://docs.mento.org/mento-v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mento.org/mento-v3/build/smart-contracts/audits.md).

# Audits

**Mento V3** is covered by two **ChainSecurity** audits:

1. **Mento Core V3** — FPMM-based exchange, OracleAdapter, liquidity strategies, CDP integration, and TradingLimitsV2. The report covers functional correctness, oracle implementation and operational implications, rounding, and documentation.\
   [ChainSecurity — Mento Core V3](https://www.chainsecurity.com/security-audit/mento-core-v3)
2. **Mento Liquity V2** — The Liquity v2 fork that underpins **CDP-backed stables** (e.g. GBPm). Users deposit USDm and mint non-USD stables against it; the system includes governance-controlled SystemParams, an upgradable Stability Pool used for rebalancing, and an FX price feed.\
   [ChainSecurity — Mento Liquity V2](https://www.chainsecurity.com/security-audit/mento-liquity-v2)

***

## Historical audits (earlier versions)

The following audits refer to earlier protocol versions (V2 / V1) and are kept for reference. They do not cover the current V3 FPMM layer.

<table><thead><tr><th width="143">Date</th><th>Link</th><th>Auditor</th><th width="100">Version</th></tr></thead><tbody><tr><td>03/2024</td><td><a href="https://0xmacro.com/library/audits/mento-3">Macro audit 3</a></td><td>Macro</td><td>V2.3.0</td></tr><tr><td>03/2024</td><td><a href="https://audits.sherlock.xyz/dashboard/404ec017225af69f6deff9b722393a44">Sherlock contest</a></td><td>Sherlock</td><td>V2.3.0</td></tr><tr><td>01/2024</td><td><a href="https://0xmacro.com/library/audits/mento-2">Macro audit 2</a></td><td>Macro</td><td>V2.3.0</td></tr><tr><td>08/2023</td><td><a href="https://0xmacro.com/library/audits/mento-1">Macro audit 1</a></td><td>Macro</td><td>V2.2.0</td></tr><tr><td>05/2023</td><td><a href="https://www.verilog.solutions/audits/mento/">Verilog (extended)</a></td><td>Verilog</td><td>v2.1.0</td></tr><tr><td>02/2023</td><td><a href="https://www.verilog.solutions/audits/mento/">Verilog</a></td><td>Verilog</td><td>v2.0.0</td></tr><tr><td>2020-2021</td><td><a href="https://blog.openzeppelin.com/celo-contracts-audit/#phase-3">OpenZeppelin</a></td><td>OpenZeppelin</td><td>v1.0.0</td></tr></tbody></table>


---

# 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.mento.org/mento-v3/build/smart-contracts/audits.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.