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

# Security Audits

#### **Security Audits & Contract Verification** **Safeguarding Every Cross-Chain Asset with Uncompromising Security**

🔒 **Why Security Audits Matter?**\
In decentralized cross-chain interactions, smart contracts are the **core safeguard** for user assets. We fully recognize the gravity of this responsibility. That’s why we proactively engage globally renowned security firms to conduct **Slowmist  audits** of our cross-chain bridge contracts, ensuring:

✅ **Zero-vulnerability implementation** of asset locking/release mechanisms\
✅ **Reliability** of multi-signature and permission control systems\
✅ **Robust fault tolerance and rollback capabilities** under extreme scenarios\
✅ **Attack-resistant design** for cross-chain message verification mechanisms

***

#### **Key Features Highlighted**

* **Zero Vulnerabilities**: Rigorous auditing eliminates risks in asset flow logic.
* **Multi-Layer Security**: Combines cryptographic proofs and decentralized governance.
* **Battle-Tested Resilience**: Simulated attacks validate protocol robustness.

***

### *Official Cross-Chain Bridge*

{% file src="/files/vVgLdhpZCdZx6JAiIxva" %}

### *Decentralized Maker*

{% file src="/files/UfC3pmK010KAQ26xbMQV" %}

***

### *Swap & Bridge & OPOOL*

{% file src="/files/lfDOEkrMS9BtchDQEVb6" %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.orbiter.finance/faq/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 `build a script that syncs our docs to a CMS` 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.