> 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-usdelvo.md).

# Official $ELVO

$ELVO is the native ecosystem token of Elvo Exchange.

$ELVO was launched on **Robinhood Chain** through the **PONS Launchpad**, connecting the Elvo ecosystem with Robinhood Chain's onchain environment.

PONS provides an onchain token launch and trading platform on Robinhood Chain. [pons](https://docs.ponsfamily.com/?utm_source=chatgpt.com)

### Token Information

|                      |                    |
| -------------------- | ------------------ |
| **Token Name**       | Elvo               |
| **Ticker**           | $ELVO              |
| **Network**          | Robinhood Chain    |
| **Launch Platform**  | PONS               |
| **Total Supply**     | 1,000,000,000 ELVO |
| **Contract Address** | `Coming Soon`      |

> **Contract Address:** The official $ELVO contract address will be published here. Never purchase or interact with a token based only on its name or ticker.

### $ELVO on PONS

$ELVO launched through **PONS**, a token launch and trading platform built for Robinhood Chain.

Users can visit PONS to explore tokens and access its onchain trading interface.

[**Visit PONS →**](https://ponsfamily.com/)

**Official $ELVO PONS Page:**\
`ELVO_PONS_LAUNCHPAD_URL`

> The direct $ELVO PONS link will be added here once the official launch URL is published.

### The Role of $ELVO

$ELVO is designed as the native token of the broader Elvo Exchange ecosystem.

As the Elvo ecosystem develops, official information regarding $ELVO utility, integrations, and supported Elvo products will be published through Elvo Exchange's official channels and documentation.

Only features that have been officially released should be considered active. Future utility should not be assumed until it is announced by Elvo Exchange.

### How to Verify the Official $ELVO

Token names, symbols, and branding can be copied. **The contract address is the definitive identifier of the official $ELVO token.**

Before buying or interacting with $ELVO:

1. Verify the contract address against the address published in this documentation.
2. Confirm the same address through Elvo Exchange's official channels.
3. Verify that you are using the correct Robinhood Chain network.
4. Use the official PONS link published by Elvo Exchange.
5. Never rely solely on a token name, ticker, logo, screenshot, or forwarded message.

> **Important:** A token using the name **Elvo** or ticker **$ELVO** is not necessarily the official Elvo Exchange token.

### Official Sources

Always verify $ELVO information through official Elvo Exchange sources:

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

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

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

**PONS**\
[ponsfamily.com](https://ponsfamily.com/)

Official contract information and the direct $ELVO PONS page should match the information published through these Elvo Exchange channels.

> **Security Notice:** Elvo Exchange team members will never ask for your private key, seed phrase, or wallet recovery phrase. Always verify the official $ELVO contract address before approving a transaction.


---

# 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-usdelvo.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.