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

# Contracts and audits

### **AMP token contract**&#x20;

> [0xff20817765cb7f73d4bde2e66e067e58d11095c2](https://etherscan.io/address/0xff20817765cb7f73d4bde2e66e067e58d11095c2)&#x20;

{% hint style="info" %}
**Do not send digital assets to the AMP contract for any reason; tokens will be&#x20;*****permanently unrecoverable*****.**
{% endhint %}

### Security Audits

The AMP token contract and related source materials have been audited by independent security researchers at ConsenSys Diligence and Trail of Bit&#x73;**.**

In June 2020, ConsenSys Diligence audited the AMP smart contracts. ConsenSys found zero critical issues and shared fifteen recommendations related to developer experience and other optimizations, which have been implemented.

In July and August 2020, Trail of Bits audited the AMP smart contracts and related collateral management contracts. Trail of Bits also found zero critical issues and shared one low-severity recommendation, which has since been acknowledged.

**Consensys Diligence Audit:**

> <https://consensys.net/diligence/audits/2020/06/amp>

**Trail of Bits Audit:**

> <https://github.com/trailofbits/publications/blob/master/reviews/amp.pdf>


---

# 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.amp.xyz/contracts-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.
