Converting ETH to L2

# Deposits and withdrawals across chains

To start using L2 you will need L2 bridged assets. For this purpose (for making a deposits or withdrawals across L1 and L2 chains) we developed a L1 standard bridge that receives assets on L1 (Ethereum mainnet), and mints the equivalent asset on Patex. When a user wants to withdraw the assets back to L1, the bridge burns the asset on L2 and releases it to the user on L1. If you want to use this bridge automatically, follow this tutorial for ETH (opens new window) or this one for ERC-20 tokens (opens new window).

Note that while L1 to L2 transactions typically take minutes, L2 to L1 transaction on the gateway require a seven day challenge period.

Alternatively, you can use a third party bridge. These bridges usually rely on liquidity pools to allow for faster withdrawals and support multiple L2 chains. However, their token selection might be more limited and they may not be as decentralized as our gateway.

When an ERC-20 token does not have an Patex equivalent you can create one. If there is no need for custom business logic, you can follow the steps in this tutorial (opens new window). If you need to implement some kind of custom logic, see this tutorial (opens new window).

# Simple way to deposit to L2

The Bridge has been deployed to L1 Sepolia Testnet and L1 Ethereum Mainnet to these two addresses: Patex Testnet 0xf0D8C28F3902Fac5b6C2dBc8574339bD84535a01 Patext Mainnet 0xb915E7bcA23e71441131D94f7FA2D95f6211dAf4 The simplest and fastest way to deposit ETH to Patex L2 is to transfer ETH to one of this addresses via your preferred web3 wallet like MetaMask. Just copy the bridge address (0xf0d8c28f3902fac5b6c2dbc8574339bd84535a01 for testnet and 0xb915E7bcA23e71441131D94f7FA2D95f6211dAf4 for mainnet) and past it to the "to" field of your transaction, enter the amount and send the transaction in L1. To see a transaction example click here.

To use it more securely, go to ETH Converter.

Last updated