> For the complete documentation index, see [llms.txt](https://docs.lyzi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lyzi.io/en/user/blockchains-et-tokens.md).

# Blockchains and Tokens

This page lists all blockchains and tokens supported in Lyzi's non-custodial flow.

{% hint style="info" %}
Only tokens marked as available are supported in the non-custodial flow.
{% endhint %}

### Summary Tables

#### By Blockchain

| Blockchain            | Supported Tokens      |
| --------------------- | --------------------- |
| **Ethereum**          | USDC, EURC, ETH, WBTC |
| **Polygon**           | USDC, POL             |
| **Arbitrum One**      | USDC, ETH             |
| **Base**              | USDC, EURC, ETH       |
| **OP Mainnet**        | USDC, ETH             |
| **Avalanche C-Chain** | AVAX                  |

#### By Token

| Token                      | Supported Blockchains                             |
| -------------------------- | ------------------------------------------------- |
| **USDC** (USD Coin)        | Ethereum, Polygon, Arbitrum One, Base, OP Mainnet |
| **EURC** (Euro Coin)       | Ethereum, Base                                    |
| **ETH** (Ether)            | Ethereum, Arbitrum One, Base, OP Mainnet          |
| **WBTC** (Wrapped Bitcoin) | Ethereum                                          |
| **POL** (Polygon)          | Polygon                                           |
| **AVAX** (Avalanche)       | Avalanche C-Chain                                 |

***

## Ethereum

**Chain ID:** 1\
**Block Explorer:** [Etherscan](https://etherscan.io/)

### Supported Tokens

| Token           | Symbol | Decimals | Contract Address                             |
| --------------- | ------ | -------- | -------------------------------------------- |
| Ether           | ETH    | 18       | Native                                       |
| USD Coin        | USDC   | 6        | `0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48` |
| Euro Coin       | EURC   | 6        | `0x1aBaEA1f7C830bD89Acc67eC4af516284b1bC33c` |
| Wrapped Bitcoin | WBTC   | 8        | `0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599` |

***

## Polygon

**Chain ID:** 137\
**Block Explorer:** [PolygonScan](https://polygonscan.com/)

### Supported Tokens

| Token    | Symbol | Decimals | Contract Address                             |
| -------- | ------ | -------- | -------------------------------------------- |
| Polygon  | POL    | 18       | Native                                       |
| USD Coin | USDC   | 6        | `0x3c499c542cef5e3811e1192ce70d8cc03d5c3359` |

***

## Arbitrum One

**Chain ID:** 42161\
**Block Explorer:** [Arbiscan](https://arbiscan.io/)

### Supported Tokens

| Token    | Symbol | Decimals | Contract Address                             |
| -------- | ------ | -------- | -------------------------------------------- |
| Ether    | ETH    | 18       | Native                                       |
| USD Coin | USDC   | 6        | `0xaf88d065e77c8cC2239327C5EDb3A432268e5831` |

***

## Base

**Chain ID:** 8453\
**Block Explorer:** [Base Explorer](https://basescan.org/)

### Supported Tokens

| Token     | Symbol | Decimals | Contract Address                             |
| --------- | ------ | -------- | -------------------------------------------- |
| Ether     | ETH    | 18       | Native                                       |
| USD Coin  | USDC   | 6        | `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` |
| Euro Coin | EURC   | 6        | `0x60a3E35Cc302bFA44Cb288Bc5a4F316Fdb1adb42` |

***

## Avalanche C-Chain

**Chain ID:** 43114\
**Block Explorer:** [Avalanche Explorer](https://subnets.avax.network/c-chain/)

### Supported Tokens

| Token     | Symbol | Decimals | Contract Address |
| --------- | ------ | -------- | ---------------- |
| Avalanche | AVAX   | 18       | Native           |

***

## OP Mainnet (Optimism)

**Chain ID:** 10\
**Block Explorer:** [OP Mainnet Explorer](https://optimistic.etherscan.io/)

### Supported Tokens

| Token    | Symbol | Decimals | Contract Address                             |
| -------- | ------ | -------- | -------------------------------------------- |
| Ether    | ETH    | 18       | Native                                       |
| USD Coin | USDC   | 6        | `0x0b2c639c533813f4aa9d7837caf62653d097ff85` |

***

## Important Notes

{% hint style="warning" %}
**Warning:** When making a payment, it is crucial to select the same blockchain and the same token as the one used in your wallet. Sending a token to the wrong blockchain or using the wrong token can result in loss of funds.
{% endhint %}

{% hint style="info" %}
Native tokens (ETH, POL, AVAX) do not have a contract address because they are the native currency of their respective blockchain.
{% endhint %}


---

# 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://docs.lyzi.io/en/user/blockchains-et-tokens.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.
