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

# Supported Chains & Tokens

Chains and tokens available for Epoch cross-chain intents. Use the SDK's `testnetGraph` and `mainnetGraph` exports for programmatic discovery, or reference the tables below.

For additional chains or tokens beyond the public mainnet set below, [contact the Epoch team](https://epochprotocol.xyz/#contact) or reach out on [Telegram](http://t.me/AkshitOstwal).

Need testnet tokens? Mint via the [Epoch User Dashboard](https://userdashboard.epochprotocol.xyz/) faucets tab ([repo](https://github.com/epochprotocol/epoch-user-dashboard)).

***

## Testnet environment

<table><thead><tr><th width="258.84765625">Item</th><th>Value</th></tr></thead><tbody><tr><td>SDK <code>apiBaseUrl</code> (testnet)</td><td><code>https://testnet-dev.epochprotocol.xyz</code></td></tr><tr><td>The Compact (all chains)</td><td><code>0x00000000000000171ede64904551eeDF3C6C9788</code></td></tr></tbody></table>

### Testnet chains

<table><thead><tr><th width="222.22265625">Network</th><th>Chain ID</th><th>Gasless Compact deposit</th></tr></thead><tbody><tr><td>Ethereum Sepolia</td><td>11155111</td><td>Yes</td></tr><tr><td>Base Sepolia</td><td>84532</td><td>Yes</td></tr><tr><td>Optimism Sepolia</td><td>11155420</td><td>Yes</td></tr></tbody></table>

**Gasless** applies to the Compact approve + deposit step on testnet when using a local signer and a gasless-enabled allocator. See [Gasless Deposits](/integration-guides/gasless-deposits.md). Verify live support via `GET {apiBaseUrl}/gasless-status`.

Additional testnet source chains:

<table><thead><tr><th width="223.70703125">Chain</th><th>Chain ID</th></tr></thead><tbody><tr><td>Miden</td><td>999999999</td></tr></tbody></table>

### Testnet tokens

<table><thead><tr><th width="148.71484375">Symbol</th><th>Address</th></tr></thead><tbody><tr><td>USDC</td><td><code>0x2BB4FfD7E2c6D432b697554Efd77fA13bdbefd69</code></td></tr><tr><td>DAI</td><td><code>0xc30f1Ce05d1434d484E9A47283aA925fc8A8699a</code></td></tr><tr><td>USDT</td><td><code>0xc04d2869665Be874881133943523723Be5782720</code></td></tr><tr><td>WETH</td><td><code>0x7946dd86eE310D0aC16804A37787289Fa5b88A8A</code></td></tr><tr><td>WBTC</td><td><code>0x9b2a2754a9182fD65360E23afCDf3BeFF51796E9</code></td></tr><tr><td>PENGU</td><td><code>0xEA7dC9849206Ce73b11c465d37b85eC06B11Cf2C</code></td></tr><tr><td>OSWALD</td><td><code>0xB588418c0f90F07Bc9587d0050845a90C23C7502</code></td></tr><tr><td>KICK</td><td><code>0x512Ee6Bd7A4be5Ba4796F15Df080c4D0F89a38eD</code></td></tr><tr><td>FERB</td><td><code>0x145e03A80c19ad1b9d0429d06b6d52707de724A0</code></td></tr></tbody></table>

#### Miden testnet tokens

Tokens on **Miden** (chain ID `999999999`) are **fungible faucet accounts** and use **6 decimals** (not 18). The faucet account ID below is the token identifier used in intents. Mint them to your Miden account via the [User Dashboard](https://userdashboard.epochprotocol.xyz/) faucets tab. Account IDs are accepted in hex (`0x…`) or bech32 (`mtst1…`) form.

<table><thead><tr><th width="148.71484375">Symbol</th><th>Faucet ID (hex)</th></tr></thead><tbody><tr><td>USDC</td><td><code>0xfc90f0f4da30e51168453b60eafed7</code></td></tr><tr><td>DAI</td><td><code>0x176275876f2fd41103257e341832b9</code></td></tr><tr><td>USDT</td><td><code>0x7725b0e9bb9406912d2ebeaeb05f4d</code></td></tr><tr><td>WETH</td><td><code>0xa54717f6bd3210d128aeeaa8a2b7f3</code></td></tr><tr><td>WBTC</td><td><code>0x151823cde4b7bd91352617729d7614</code></td></tr><tr><td>MIDEN</td><td><code>0x2458e5446128e6b150b75b8ebd9ce1</code></td></tr></tbody></table>

***

## Mainnet environment

| Item                       | Value                            |
| -------------------------- | -------------------------------- |
| SDK `apiBaseUrl` (mainnet) | `https://api.epochprotocol.xyz/` |

### Mainnet chains

| Chain        | Chain ID |
| ------------ | -------- |
| Base         | 8453     |
| Arbitrum One | 42161    |
| Polygon      | 137      |
| Optimism     | 10       |

### Mainnet tokens

The following tokens are currently supported on **public mainnet** across all supported chains above:

| Symbol |
| ------ |
| USDC   |
| USDT   |
| WETH   |
| DAI    |

Need additional tokens? [Contact the Epoch team](https://epochprotocol.xyz/#contact) or on [Telegram](http://t.me/AkshitOstwal).

***

## Discovering chains and tokens in code

```typescript
import { mainnetGraph, testnetGraph } from "@epoch-protocol/epoch-intents-sdk";

// Pick graph by chainId (mainnet vs testnet)
// getTokensForChain(chainId) → { symbol, address, decimals }[]
// getChainsFromGraph(chainId) → destination chain options
```

See [SDK Integration Guide](/integration-guides/sdk-integration-guide.md) and [compact-demo-epoch](/integration-examples.md#compact-demo-epoch) for full patterns.

***

## Requesting new chains or tokens

The public mainnet set above covers Base, Arbitrum, Polygon, Optimism and the tokens USDC, USDT, WETH, and DAI. For anything beyond that, [contact the Epoch team](https://epochprotocol.xyz/#contact) or on [Telegram](http://t.me/AkshitOstwal) with:

* Chain name and chain ID
* Token contract addresses and decimals
* Use case (swap, bridge, protocol interaction)

New entries are added to Epoch's routing graph after validation.

***

## Next steps

* [Quickstart](/integration-guides/quickstart.md)
* [Integration Examples](/integration-examples.md)
* [SDK Reference](/integration-guides/sdk-reference.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.epochprotocol.xyz/supported-chains-and-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.