# Security

At SurfLayer, security is our highest priority.\
We have built a unique architecture that processes cross-chain transactions without relying on traditional smart contracts, effectively minimizing the risk of exploits and contract-based vulnerabilities.

To further enhance user safety, SurfLayer enforces standardized transfer limits that reduce potential losses and protect users under unexpected network conditions or system anomalies.

Unlike most cross-chain protocols, SurfLayer operates using its own liquidity reserves instead of user-provided funds.\
This non-custodial approach ensures that users retain full control over their assets at all times.

Our principle is clear: security over hype.\
Every design choice is made with user protection in mind — delivering cross-chain interactions that are seamless, fast, and secure.

#### Audited by QuillAudits

SurfLayer has undergone a comprehensive smart contract audit by QuillAudits — a trusted security firm recognized for its work with top blockchain projects.

The audit reported an exceptional score of 99%, validating our system’s robustness and commitment to maintaining industry-leading security standards.

**QuillAudits Leaderboard:** <https://www.quillaudits.com/leaderboard/surflayer>

**📄 View Audit Report:** <https://github.com/Quillhash/QuillAudit_Reports/blob/master/Surflayer%20Smart%20Contract%20Audit%20report%20-%20QuillAudits.pdf>

<figure><img src="/files/fZsHViwvMEsgtakhU1oS" alt=""><figcaption></figcaption></figure>


---

# 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://docs.surflayer.xyz/surf-bridge-structure/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.