> For the complete documentation index, see [llms.txt](https://ample-2.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ample-2.gitbook.io/docs/security-and-risk/overview.md).

# Security & Risk

Security comes first at Ample. This is how deposits are protected, and what risks remain.

### The security model

* **Non-custodial by design**
  * Deposits sit in ERC-4626 smart contracts. Ample never takes custody of user funds; only your keys move your balance, and withdrawals are open at all times.
* **Independently audited**
  * Ample's vault and payout contracts were audited by **Pashov Audit Group** (December 2025 & March 2026). They're built on Euler, one of the most rigorously reviewed protocols in DeFi with more than fifty independent audits, and Morpho, which secures billions across the ecosystem.
* **A strict yield policy**
  * Deposits go to institutional-grade, overcollateralized lending markets only. No leverage, no directional positions, no exotic strategies, under any circumstances. Deposit caps keep every vault sized to what its strategies deploy well.
* **Provably fair draws**
  * Every cycle seals its ticket list into a published merkle root before the draw, generates randomness through a VRF that ships with a cryptographic proof, and commits results onchain before any claim. Once committed, no result can be edited, added, or rerolled without it being publicly visible, by anyone, including Ample.
* **Hardened OpSec**
  * Ample team follows industrial-grade opsec policies, each team member with even the slightest access has very strict access guidelines & monitoring. 
  * All of our multisigs have timelocks, high thresholds and remain in cold wallets following industry standards. 

### Where payouts come from

Payouts are funded by yield. There is no flow in the system by which deposits become payouts, so the prize mechanism can never touch your principal, no matter who wins or how often. The pool is interest, and everyone's stake stays their own.

### Risks

Ample is an onchain product, and onchain products carry risk that careful engineering reduces.

| Risk                                                                      | What stands in the way                                                                                                                    |
| ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Smart contract bugs, in Ample's code or the venues beneath it             | Independent audits at every layer; minimal contract surface; battle-tested venues only                                                    |
| A stablecoin moving off its peg, or market moves on non-stablecoin vaults | Major, deeply liquid assets only; per-vault behavior shown in [Supported Chains & Assets](/docs/vaults-and-deposits/chains-and-assets.md) |
| Bridge or DEX issues while a cross-chain route is in motion               | Established infrastructure (LI.FI, LayerZero); route status tracked end to end; direct deposit always available                           |
| Stressed-market liquidity briefly limiting instant withdrawals            | Conservative venues and deposit caps keep utilization healthy; the app shows the live maximum                                             |

### Audits

| Scope    | Auditor            | Date          | Report                                                                                         |
| -------- | ------------------ | ------------- | ---------------------------------------------------------------------------------------------- |
| Audit #1 | Pashov Audit Group | December 2025 | <p></p><div data-gb-custom-block data-tag="file" data-src="/files/3cD4LgsgYRO0rHQAjfF1"></div> |
| Audit #2 | Pashov Audit Group | March 2026    | <div data-gb-custom-block data-tag="file" data-src="/files/0rNmzkq8yJRZmdmSQMZp"></div><p></p> |

Questions on the model are welcome at **<ample@layer3.xyz>**.&#x20;


---

# 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:

```
GET https://ample-2.gitbook.io/docs/security-and-risk/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.