Sending a message from the Ethereum chain (L1) to the Arbitrum chain (L2) does not involve the state challenge period and is as fast as the block confirmation time on L1 and L2 combined.
In this tutorial, you will:
- Deploy greeter contracts on Ethereum and on Arbitrum.
- Send a message from the greeter contract deployed on Ethereum (L1) to the greeter contract deployed on Arbitrum (L2).
- Chainstack account to deploy an Ethereum node and an Arbitrum node.
- MetaMask to fund your account on L2 with GoerliETH.
To get from zero to your first L1 to L2 message, do the following:
- With Chainstack, create a public chain project.
- With Chainstack, join the Ethereum Goerli testnet.
- With Chainstack, join the Arbitrum Goerli testnet.
- Set up your MetaMask to work through the Chainstack Ethereum and Arbitrum nodes.
- Fund your account through a faucet on the Ethereum Goerli testnet and on the Arbitrum Goerli testnet.
- Run the tutorial script to deploy the contracts on L1 and L2 and send the message from L1 to L2.
See Create a project.
Deploy a node on the Ethereum Goerli testnet and a node on the Arbitrum Goerli testnet.
Your account will need Goerli ether on both the Ethereum Goerli testnet and the Arbitrum Goerli testnet as you will deploy a contract on each of the chains.
- Ethereum Goerli faucet: see Chainstack faucet
- Arbitrum Goerli faucet: see Nitro Goerli Rollup in the Arbitrum documentation
The default Arbitrum Goerli faucet may fund your account with 0.001 GoerliETH, which is not enough to deploy the greeter contract on L2.
If you do not have enough GoerliETH on L2, you may bridge some more from the Ethereum Goerli testnet using the Arbitrum bridge.
You will use the Offchain Labs tutorials repository to deploy the contracts and send the message.
Clone the repository:
git clone https://github.com/OffchainLabs/arbitrum-tutorials.git
Install dependencies by running
Set up the
.env file by renaming the sample one in
cp .env-sample .env
.env file, add your account key and the endpoints:
- DEVNET_PRIVKEY — the private key of your account that has GoerliETH both on the Ethereum Goerli testnet and the Arbitrum Goerli testnet.
- L2RPC — the Chainstack HTTPS endpoint of your Arbitrum node deployed on the Arbitrum Goerli testnet.
- L1RPC — the Chainstack HTTPS endpoint of your Ethereum node deployed on the Ethereum Goerli testnet.
You are now all set to run the tutorial script that will deploy the greeter contracts and send a message from L1 to L2.
yarn run greeter
The script will:
- Deploy the L1 greeter contract on the Ethereum Goerli testnet. Example: 0x9B4F541D6A82Beb594Ee2A1EfF14d88f2898176c.
- Deploy the L2 greeter contract on the Arbitrum Goerli testnet. Example: 0x890443aB733bd527F0036aEd3E249358a30Ff3ce.
- On the L1 contract, set the L2 contract address.
- On the L2 contract, set the L1 contract address.
- Retrieve the current gas costs for the transaction off the ArbRetryableTx contract on L2. See also Arbitrum documentation: Messaging Between Layers.
- Using the retrieved gas cost values, submit the message transaction on L1. The transaction will send the message to the inbox contract on L1. See also Arbitrum documentation: Contract addresses.
- The transaction will then be submitted as a retryable ticket by the ArbRetryableTx contract on L2. Example.
- Then the retryable ticket will be redeemed and change the state in the greeter contract on L2 with the message from the greeter contract on L1. Example.
This tutorial guided you through the basics of creating and deploying a simple greeter contract that sends a message from the Ethereum chain to the Arbitrum chain. The tutorial also provided the examples and an explanation of the step-by-step state changes and the contracts involved in the L1 to L2 messaging.
Updated 3 months ago