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

# Security Audits

Morpheus’ decentralize architecture is built on Smart Contracts. To ensure safety, reliability, trust, and scalability on a global scale, maintaining the highest level of cybersecurity is essential.

Morpheus prioritizes security by subjecting its Smart Contracts to rigorous audits, performed by both experts and independent white-hat hackers through [Bug Bounty Program](/security-audits/morpheus-bug-bounty-program.md). Even the smallest upgrades to the Smart Contracts undergo a thorough audit process.

You can find the latest audit below, and the full list is publicly available on [GitHub](https://github.com/MorpheusAIs/Docs/tree/main/Security%20Audit%20Reports).

{% file src="/files/9VPqI30yQvt8fOSKL8Nv" %}
MOR OFT Audit Report
{% endfile %}

{% file src="/files/j8W7SpCuYKcjLhpPeEAc" %}
MOR20 Contracts Audit Report
{% endfile %}

{% file src="/files/SAEhjGQwvfJRUgXEQban" %}
1st Morpheus Lumerin Compute Contract Audit Report
{% endfile %}

{% file src="/files/Uqw9gM7aD116myfOYNla" %}
2nd Morpheus Lumerin Compute Contract Audit Report
{% endfile %}

{% file src="/files/22nxGAUakWHHQG8Zs2RX" %}
Distribution V3 (Capital Rewards Staking) Audit Report
{% endfile %}

{% file src="/files/Mk8XIZXhJpZ20nkWdSG6" %}
Distribution V3 (Code Rewards Staking) Audit Report
{% endfile %}

{% file src="/files/ETSwLRGftrqW6JScgB76" %}
Distribution V4 (Claim Lock) Audit Report
{% endfile %}

{% file src="/files/kcuSsixEIX1wTZcGS9hI" %}
Distribution V5 (Referral Program) Audit Report
{% endfile %}

{% file src="/files/sVenCfCIK0l7il1pDjyR" %}
Morpheus Capital V2 Zenith Audit Report
{% endfile %}

{% file src="/files/KOJyfGqdOAqIHDWNuEkZ" %}
Morpheus Capital V2 Code4rena Audit Report
{% endfile %}


---

# 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://gitbook.mor.org/security-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.