# Bridging to Base Chain

Network Information (Metamask - Add new chain)

| Name            | Value                                                |
| --------------- | ---------------------------------------------------- |
| Network Name    | Base Mainnet                                         |
| Description     | The public mainnet for Base.                         |
| RPC Endpoint    | [https://base.meowrpc.com](htpps://base.meowrpc.com) |
| Chain ID        | 8453                                                 |
| Currency Symbol | ETH                                                  |
| Block Explorer  | [https://basescan.org](https://basescan.org/)        |

### SwapBased incorporated [Axelar x Squid Bridge](/home/axelar-bridge-official-partner.md) <a href="#base-bridge" id="base-bridge"></a>

### Base Bridge[​](https://docs.base.org/tools/bridges#base-bridge) <a href="#base-bridge" id="base-bridge"></a>

The [Base Bridge](https://bridge.base.org/) allows you to bridge ETH from Ethereum to Base and vice versa.

To bridge to or from Base:

1. Visit [Base Bridge](https://bridge.base.org/)
2. Click **Bridge assets**
3. Connect your wallet
4. Choose the amount of ETH (or the asset of your choice that's available) you'd like to deposit or withdraw

For frequently asked questions about Base Bridge, be sure to check out the [Bridge FAQ](https://docs.base.org/tools/bridge-faq).

***

### Portal Proxy Contract[​](https://docs.base.org/tools/bridges#portal-proxy-contract) <a href="#portal-proxy-contract" id="portal-proxy-contract"></a>

You can bridge ETH from Ethereum to Base by sending ETH to **`portal.base.eth`** or the following contract address:

[0x49048044D57e1C92A77f79988d21Fa8fAF74E97e](https://etherscan.io/address/0x49048044D57e1C92A77f79988d21Fa8fAF74E97e)

INFO

By default, bridging ETH will result in a `SELF` transaction on the L2, with the `from` and `to` addresses equal to the address performing the bridge on the L1. This will also increase that address' L2 nonce. **If you are bridging for the purpose of a deterministic contract deploy that depends on a zero nonce, please bridge using a different address first, and transfer to the contract deployment address on the L2 after bridging.**

As a bridge UI is not available during the [developer access period](https://base.mirror.xyz/hwNwqXHVoLlO8s4DZppog4DfGvM34tigaDjOWuEJQfY), we have provided a Golang utility for withdrawals on GitHub at [base-org/withdrawals](https://github.com/base-org/withdrawer). Developers can use this to easily withdraw their funds from Base, ahead of opening mainnet for everyone in early August.

INFO

Users are required to wait for a period of seven days when moving assets out of Base mainnet into the Ethereum mainnet. This period of time is called the Challenge Period and serves to help secure the assets stored on Base mainnet.

CAUTION

Bridging ETH with the portal proxy contract is for developers:

* **Do not send any asset other than ETH.** The proxy contract only supports receipt of ETH and sending any other asset will result in unrecoverable loss of the asset.
* **Do not send ETH from any network other than Ethereum mainnet.** The proxy contract only supports from Ethereum mainnet and sending from any other network or chain (e.g. another EVM-compatible chain or L2) will result in unrecoverable loss of the asset.
* **Do not send ETH from an exchange.** The portal proxy contract bridges to the address where ETH is sent from, so if sent from an exchange, for example, ETH will be bridged back to the exchange, which could result in unrecoverable loss of the asset.

***


---

# Agent Instructions: 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:

```
GET https://docs.swapbased.finance/home/bridging-to-base-chain.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
