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

# Token Contracts on Gravity

This page is the authoritative list of canonical ERC-20 token contracts on Gravity L1. The list is populated as tokens are bridged in and deployed.

{% hint style="info" %}
For the Alpha Mainnet (L2, Chain ID `1625`) token list — which has G / wG / WBTC / DAI / ETH(WETH) / USDT / USDC — see [Token Contracts on Gravity Alpha (L2)](/legacy-alpha-mainnet-l2/token-contracts-on-gravity.md). Addresses below are for **L1 only** and are different from the L2 addresses.
{% endhint %}

## Native token

| Token | L1 address                      | Notes                                                                                                                                                                                         |
| ----- | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| G     | Native coin — no ERC-20 address | Used for gas, staking, and governance. Bridged from Ethereum ERC-20 `0x9C7BEBa8F6eF6643aBd725e45a4E8387eF260649` via the canonical bridge (see [How to Get G](/the-g-token/how-to-get-g.md)). |

## Bridged assets

These addresses are populated as the canonical bridge goes live for each asset. Each entry lists the canonical L1 address, the Ethereum source contract, and the official bridge route used.

| Token          | L1 address                                   | Ethereum source                                              | Official bridge |
| -------------- | -------------------------------------------- | ------------------------------------------------------------ | --------------- |
| wG (Wrapped G) | `0xBB859E225ac8Fb6BE1C7e38D87b767e95Fef0EbD` | native G on L1 (wrapper, not bridged from an external chain) | —               |
| WETH           | TBA                                          | Native ETH                                                   | TBA             |
| USDT           | TBA                                          | `0xdac17f958d2ee523a2206206994597c13d831ec7`                 | TBA             |
| USDC           | TBA                                          | `0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48`                 | TBA             |
| DAI            | TBA                                          | `0x6B175474E89094C44Da98b954EedeAC495271d0F`                 | TBA             |
| WBTC           | TBA                                          | `0x2260fac5e5542a773aa44fbcfedf7c193bc2c599`                 | TBA             |

## Submitting a new token

Canonical tokens are tracked in the public [Galxe/gravity-token-list](https://github.com/Galxe/gravity-token-list) repository (`src/tokenlist.json`). To get your token added:

1. Deploy the ERC-20 on Gravity L1.
2. Fork [Galxe/gravity-token-list](https://github.com/Galxe/gravity-token-list).
3. Add an entry to `src/tokenlist.json` with `chainId: 127001`, address, symbol, decimals, and logo URI.
4. Open a PR following the template. The Gravity team reviews for basic sanity (no impersonation, verified contract, correct metadata).

## See also

* [G Token](/the-g-token/g-token.md) — native token overview.
* [How to Get G](/the-g-token/how-to-get-g.md) — bridging flow.
* [Gravity Mainnet (L1) Contracts](/developer-resources/mainnet.md) — system and bridge contract addresses.
* [Legacy L2 token list](/legacy-alpha-mainnet-l2/token-contracts-on-gravity.md) — Alpha Mainnet (L2) canonical list.


---

# 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.gravity.xyz/the-g-token/token-contracts.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.