> For the complete documentation index, see [llms.txt](https://docs.onyx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyx.org/tokenomics/xcn-token.md).

# XCN Token

XCN is the native coin of Onyx Mainnet and is used for gas and native transfers.

## Ethereum XCN

ERC-20 contract:

```
0xA2cd3D43c775978A96BdBf12d733D5A1ED94fb18
```

[View Ethereum XCN on Etherscan](https://etherscan.io/address/0xA2cd3D43c775978A96BdBf12d733D5A1ED94fb18)

## Wrapped XCN on Onyx

Wrapped XCN (WXCN) is the ERC-20 representation used by Onyx smart contracts and DEX pools:

```
0x1a0Da75ADf091a69E7285e596bB27218D77E17a9
```

[View WXCN on the Onyx Explorer](https://explorer.onyx.org/address/0x1a0Da75ADf091a69E7285e596bB27218D77E17a9)

[The Onyx bridge](https://app.onyx.org/en/bridge) moves XCN between its Ethereum ERC-20 representation and native Onyx representation. Supply, staking, bridge reserves, and market values are mutable; use current explorer, Markets, and bridge data rather than a fixed snapshot in documentation.

Native XCN uses 8-decimal ledger precision even though JSON-RPC represents values with 18-decimal scaling. See [XCN Decimal Handling](/developer-guide/decimal-handling.md).


---

# 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.onyx.org/tokenomics/xcn-token.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.