> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/exchange-layer-1/es-419/nex-token/tokens-and-bridges.md).

# Tokens y puentes

## NEX

NEX es el token nativo de la blockchain de Nexus, y el gas se paga en NEX. WNEX es la versión ERC-20 envuelta (wrapped) de NEX en la blockchain de Nexus, y en Ethereum NEX también existe como ERC-20. Consulta [NEX](/exchange-layer-1/es-419/nex-token/tokens-and-bridges/usdnex.md) para más detalles.

## USDX *(en desarrollo)*

USDX será la moneda de margen y de cotización de Nexus Exchange. Los traders la usarán para abrir posiciones y para saldar sus operaciones. Está en desarrollo con M0 Protocol.

## Uso del puente

NEX se mueve entre cadenas a través de dos mecanismos:

* El **puente canónico de NEX** conecta la blockchain de Nexus y Ethereum.
* Una **Hyperlane Warp Route** conecta Ethereum y Binance Smart Chain (BSC): NEX se bloquea en Ethereum y se emite un NEX sintético en BSC.

Consulta [Uso del puente](/exchange-layer-1/es-419/nex-token/tokens-and-bridges/bridging.md) para ver los contratos y las instrucciones paso a paso.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexus.xyz/exchange-layer-1/es-419/nex-token/tokens-and-bridges.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.