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

# Official Links & Team

Always use official Elvo Exchange channels when accessing platform information, product updates, security announcements, or support.

Be cautious of impersonators, unofficial groups, and accounts claiming to represent Elvo Exchange.

### Official Elvo Exchange Links

**Website**\
[elvo.exchange](https://elvo.exchange/)

**Telegram Community**\
[t.me/elvoexchange](https://t.me/elvoexchange)

**X**\
[x.com/elvoexchange](https://x.com/elvoexchange)

> **Security Notice:** Always verify that you are using an official Elvo Exchange website, social media account, or team contact before sharing account-related information or following instructions.

***

### Official Elvo Exchange Team

The following Telegram accounts are recognized as official Elvo Exchange team contacts.

#### Nathan Jonath

**Founder — Elvo Exchange**

Telegram: [@NathanJonash](https://t.me/NathanJonash)

Nathan Jonath is the founder of Elvo Exchange.

***

#### ClevonNix

**Customer Care & Marketing**

Telegram: [@ClevonNix](https://t.me/ClevonNix)

ClevonNix assists with customer support, community communication, and marketing-related matters.

***

#### Zaylee

**Social Media Team**

Telegram: [@Mrgweieth](https://t.me/Mrgweieth)

Zaylee supports Elvo Exchange's social media and community communication activities.

***

#### Wang Zǐxuan

**Customer Care Team**

Telegram: [@Zixuanzi](https://t.me/Zixuanzi)

Wang Zǐxuan assists users with general customer care and support-related matters.

***

### How to Verify an Official Team Member

Before communicating with anyone claiming to represent Elvo Exchange:

1. Check the Telegram username carefully.
2. Compare it with the official account listed on this page.
3. Access team profiles only through links published in official Elvo documentation or official Elvo channels.
4. Be cautious of accounts using similar names, profile pictures, or usernames.

A display name or profile picture alone does **not** confirm that an account belongs to the Elvo Exchange team.

***

### Protect Your Account

Elvo Exchange team members will never ask you to provide:

* Your account password
* Your private key
* Your wallet seed phrase or recovery phrase
* Your authenticator code
* Full access to your wallet
* Remote access to your device

Never send funds to an address provided by someone claiming to be Elvo support unless the action is explicitly part of an official Elvo Exchange product flow shown on [elvo.exchange](https://elvo.exchange/).

If you are unsure whether a message is legitimate, verify the sender through the official Elvo Exchange channels before taking any action.

***

### Official Communication

Important announcements, product updates, and security notices should be verified through:

[**Elvo Exchange Website →**](https://elvo.exchange/)

[**Official Telegram →**](https://t.me/elvoexchange)

[**Official X →**](https://x.com/elvoexchange)

> Do not rely on forwarded messages, screenshots, unofficial groups, or third-party accounts as the sole source of Elvo Exchange information.


---

# 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://elvo-exchange.gitbook.io/elvo-exchange-docs/welcome/official-links-and-team.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.