> 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/help/official-links.md).

# Official Links

Everything Dasus publishes lives on the handful of addresses below. Before you click a link, connect a wallet or send funds, check it against this list.

## Website and app

|                    |                                                                       |
| ------------------ | --------------------------------------------------------------------- |
| **App & website**  | <https://dasus.xyz> — the only Dasus domain                           |
| **Referral links** | `https://dasus.xyz/join/CODE` — always on the same domain             |
| **Documentation**  | <https://dasus.gitbook.io/dasus-docs> — this site; the app links here |

Any other domain that claims to be Dasus — a different ending (`.com`, `.io`, `.app`…), an extra word, a lookalike spelling — is not operated by Dasus.

## Community and support

| Channel              | Address                                                                                                |
| -------------------- | ------------------------------------------------------------------------------------------------------ |
| **X (Twitter)**      | [@dasus\_xyz](https://x.com/dasus_xyz)                                                                 |
| **Telegram**         | [t.me/dasus\_xyz](https://t.me/dasus_xyz) — this is also where the in-app **Support** button takes you |
| **Issue reports**    | <ceo@dasus.xyz> — the "Report an issue" address shown on error and maintenance pages                   |
| **Security contact** | <security@dasus.xyz> — published in `dasus.xyz/.well-known/security.txt`                               |

No other channel is official. A Discord server, a second X account or a Telegram group that is not listed here is not ours, whatever name or logo it uses.

## The underlying protocol

Your account lives on Hyperliquid, not on Dasus. If dasus.xyz is ever unavailable, the maintenance page points you to these two links so you can keep managing your positions:

* **Hyperliquid app:** <https://app.hyperliquid.xyz/trade> — connect the same wallet to manage or close your positions directly.
* **Hyperliquid status:** <https://hyperliquid.statuspage.io>

{% hint style="danger" %}
**Phishing and impersonation**

* **Never share your seed phrase or private keys with anyone** — not even someone claiming to be Dasus support. No team member will ever ask for them.
* Dasus will **never DM you first**, ask you to "validate" or "sync" your wallet, or request funds, keys or remote access.
* Dasus only asks for signatures you can read: plain-text messages (`personal_sign`) and EIP-712 typed data. A site that asks you to sign an unreadable `eth_sign` blob is not Dasus.
* Type `dasus.xyz` yourself or use a bookmark. Do not follow links from DMs, emails, search ads or unofficial groups.
* If a site or a person asks for your seed phrase, it is a scam. Close it.
  {% endhint %}

{% hint style="info" %}
Dasus is [non-custodial](https://dasus.gitbook.io/dasus-docs/start-here/readme.md): your funds sit in your own Hyperliquid account, controlled by your wallet, and the session key you approve for trading cannot withdraw them. Protecting your keys protects your funds. See [Getting Started](https://dasus.gitbook.io/dasus-docs/start-here/getting-started.md) for how connecting and signing works.
{% endhint %}

## Reporting suspicious activity

If you find a fake website, a fake social account or someone impersonating Dasus staff, report it on the official Telegram or by email to <ceo@dasus.xyz> so we can act on it and warn the community. Security vulnerabilities go to <security@dasus.xyz>.


---

# 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/help/official-links.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.
