# Top-notch security

In the rapidly evolving landscape of blockchain, security remains the most important concern. The increasing complexity of transactions, coupled with the growing stakes involved, requires a platform that, before even offering advanced features and tangible utility, ensures that users’ funds are safe. This is why we have been unwavering in our commitment to providing our users with an experience that seamlessly combines cutting-edge functionality with industry-leading security.

Here is an overview of what ensures our extension’s security:

1. Ally is originally a fork of the Rabby extension, which had already undergone three audits by SlowMist up to the point of our fork. The most recent audit was conducted in July 2023, ensuring the latest security standards are met.
   * [First audit](https://github.com/RabbyHub/Rabby/blob/master/docs/Rabby%20chrome%20extension%20Penetration%20Testing%20Report.pdf) (July 2021)
   * [Second audit](https://github.com/RabbyHub/Rabby/blob/master/docs/SlowMist%20Audit%20Report%20-%20Rabby%20browser%20extension%20wallet-2022.03.18.pdf) (March 2022)
   * [Third audit](https://github.com/RabbyHub/Rabby/blob/master/docs/SlowMist%20Audit%20Report%20-%20Rabby%20Wallet-2023.07.20.pdf) (July 2023)
2. Similar to Rabby, Ally harnesses the proven component for key storage and encryption from MetaMask, the industry-leader crypto wallet with over 30 million monthly users.
3. Ally’s codebase is fully open-source and available for review on [GitHub](https://github.com/viaprotocol/companion).
4. Finally, **Ally’s security is enhanced by its most distinguishing feature, the deliberate avoidance of proxy smart contracts**. Instead, Ally empowers users to interact directly with the smart contracts of decentralized exchanges (DEXs) and bridges, thereby avoiding any additional trust assumption and minimizing security vulnerabilities.


---

# Agent Instructions: 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://allyhq.gitbook.io/docs/security/top-notch-security.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.