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

# Audits

## Security Audit Report: Solana LP Handler

### Overview

DeGate’s Solana LP Handler has been independently audited by **Adevar Labs**, a boutique blockchain security firm with over 100 audits completed and a track record securing protocols across Solana, Ethereum, and beyond.

The audit covered the full `programs/*` codebase of the Solana LP Handler, a wrapper around Raydium CLMM liquidity management flows that powers DeGate’s [Turbo Range](https://app.slack.com/features/turbo-range.md) product on Solana.

### What was audited

The Solana LP Handler supports:

* Position creation and liquidity management (increase/decrease)
* Token swaps into the required deposit ratio (zap flows)
* Reward and fee collection
* Protocol-specific security controls for integrator fee routing and operational safety

All High and Medium severity findings were resolved before the first production deployment.

#### Auditor’s assessment

> *“The Degate team has demonstrated a strong understanding of Raydium CLMM primitives and the preliminary audit adopted a security-first mindset. The Degate team promptly resolved all High and Medium severity issues and demonstrated a strong understanding of the security implications.”*
>
> — Adevar Labs, March 2026

### Ongoing security review

The Adevar Labs report above covers the Solana LP Handler. The other components of the current wallet (email-wallet key storage, cross-chain routing, Simple Earn integrations, the mobile and web front ends) are reviewed on an ongoing basis by DeGate’s dedicated security team as part of our regular release process, and are covered by the active [bug bounty](https://app.slack.com/security-and-self-custody/bug-bounty.md), which focuses on the live web and mobile apps.

### Full report

The complete audit report including all findings, proof-of-concept exploits, code snippets, and developer responses is publicly available:

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

*Audited by Adevar Labs · March 2026*

{% hint style="info" %}
To report a vulnerability, contact <bounty@degate.com>. See [Bug Bounty](/security-and-self-custody/bug-bounty.md).
{% endhint %}


---

# 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.degate.com/security-and-self-custody/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.