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

# Trust & Security

What protects your funds and your keys on Dasus — stated as it is built, without marketing gloss.

## Non-custodial by design

Dasus is an interface on top of an on-chain exchange protocol. Your funds stay in your own on-chain account: Dasus never holds, pools or moves them. Deposits and withdrawals happen between your wallet and the protocol.

Every order, cancel and modification is signed by a key you control. Dasus holds no balance of yours, and no Dasus server can sign a withdrawal.

## Session keys that cannot withdraw

To trade without a wallet popup per click, you approve an agent key ("Establish connection"). The protocol enforces that such keys cannot withdraw or transfer funds, by construction; they sign orders and account settings that do not move money (leverage, referral code). They expire, are named per device, and you can rotate or revoke them at any time from **Settings → Agent wallets**.

{% hint style="warning" %}
A compromised agent key still cannot withdraw, but it **can place trades and cause losses**. If you ever suspect one, revoke it immediately from Agent wallets.
{% endhint %}

For copy trading and the 24/7 trailing stop, a dedicated agent key runs on Dasus servers so they work while you are offline. It is stored encrypted (AES-256-GCM) with a key that lives outside the database and is never returned by any API. Pausing a copy keeps it; it is deleted when you delete the copy, once its mirrored stops and targets are cancelled. The 24/7 trailing key you remove yourself from **Settings → Agent wallets**. Like every agent key, it cannot withdraw, and you can revoke it on-chain at any time.

With that same key, and only if you leave the box ticked when establishing the connection, Dasus registers your account under its referral code: you get 4% off the protocol fees and Dasus receives 10% of those fees. It happens once, moves no funds, and the protocol does not allow changing it afterwards.

## What you sign, and why it can't be reused

Accepting the Terms of Service or the copy-trading risk disclosure is a gas-free signature. The message names the document and its version, the SHA-256 hash of its text, the URL, the domain you are signing on, your wallet, a server-issued nonce and a short expiry. A signature therefore cannot be replayed on another site or later, and the exact text you signed is archived with your acceptance.

We only ever request readable `personal_sign` (EIP-191) and EIP-712 messages. **Dasus never asks for a blind `eth_sign`.**

## Transparent fees

Dasus earns through the protocol's builder-code mechanism: a platform fee attached on-chain to each order you place, capped by the maximum you approve once and shown in the order summary before you confirm. The schedule — including maker and volume discounts — is published on the [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md) page and computed by a single calculator shared by the order form, the Fees page and the copy engine.

## Third-party markets

HIP-3 perpetuals and HIP-4 outcome markets are deployed permissionlessly by third parties on the protocol. Dasus surfaces them from on-chain activity and **does not review, verify or approve them**; the first time you open one you are shown the deployer disclaimer. Please read each market's details and the deployer's documentation before trading.

## Web security posture

HTTPS only with HSTS, a Content-Security-Policy, the site cannot be framed by other sites (`frame-ancestors none`), no permissive CORS, and rate limiting on our API. Admin actions are authorised server-side on every request by wallet role.

Security researchers can reach us through the contact published at [`/.well-known/security.txt`](https://dasus.xyz/.well-known/security.txt).


---

# 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://dasus.gitbook.io/dasus-docs/the-app/trust-and-security.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.
