> For the complete documentation index, see [llms.txt](https://elysia.gitbook.io/elysia-perps/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elysia.gitbook.io/elysia-perps/reference/network-and-contracts.md).

# Network & Contract Addresses

Everything you deposit lives on **one chain**. Sending funds from the wrong chain, or bridging them in, is the single most common way people lose money on any exchange, and it is **not recoverable**. Verify this page before your first deposit.

## Which chain

Elysia Perps uses **Ethereum mainnet** for everything on-chain:

|          |                                      |
| -------- | ------------------------------------ |
| Network  | **Ethereum mainnet**                 |
| Chain ID | **1**                                |
| Explorer | [etherscan.io](https://etherscan.io) |

Only **deposits, withdrawals, and custody** happen on-chain. **Trading, margin, funding, and settlement happen off-chain** on the matching engine. Those never touch the chain and cost no gas. So the only chain you ever interact with directly is Ethereum mainnet, at deposit and withdrawal time.

## Addresses to verify

Deposit **only** the supported collateral token, **only** on Ethereum mainnet, to the custody contract below. Always confirm the address in your own wallet and on Etherscan. Never trust an address pasted in a chat, email, or DM.

| What                                          | Address                                      | Explorer                                                                                     |
| --------------------------------------------- | -------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **Custody contract** (deposits & withdrawals) | `0x3C8643508c5568621CB6d21119e4076551522c84` | [View on Etherscan](https://etherscan.io/address/0x3C8643508c5568621CB6d21119e4076551522c84) |
| **EL token** (supported collateral)           | `0x2781246fe707bB15CeE3e5ea354e2154a2877B16` | [View on Etherscan](https://etherscan.io/token/0x2781246fe707bB15CeE3e5ea354e2154a2877B16)   |

> The app also shows the current custody address at deposit time. If what the app shows does not match the address here, **stop** and check with the team before sending anything.

## Before you deposit: checklist

* **Network is Ethereum mainnet (chainId 1).** Not a testnet, not an L2, not a sidechain. If your wallet is on any other network, switch it first.
* **Token is the EL token at the address above.** A token with the same name/ticker on another chain, or a look-alike contract, is **not** the same asset and will not be credited.
* **Destination is the custody contract above.** Do not send to any other address.
* **Do not bridge.** There is no supported bridge deposit path. Bridged or wrapped versions of the token are not the deposit asset.

Funds sent on the wrong chain, as the wrong token, or to the wrong address cannot be credited and generally cannot be returned.

## Where to go next

* Step-by-step deposit flow: **Getting Started →** [**Deposit**](/elysia-perps/getting-started/deposit.md).
* How the custody contract is secured, and how to inspect it: [Smart Contract Security](/elysia-perps/risk-and-security/smart-contract-security.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://elysia.gitbook.io/elysia-perps/reference/network-and-contracts.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.