Arbitrum Extension for Scaffold-ETH 2

This extension adds Arbitrum specific features (bridging, address table, forced transactions) to your Scaffold-ETH 2 dApp and can be installed with:

    npx create-eth@1.0.0-beta.5 -e BuidlGuidl/arbitrum-extension:main

If you are not familiar with Scaffold-ETH 2, you can check the docs and the website.

The extension showcases three Arbitrum specific abilities:

• L1 <> L2 Bridging
• The Address Table Precompile
• Forcing a transaction from L1 onto L2

Setup

This extension is meant to be used on testnet/mainnet networks. It will not be able to demonstrate Arbitrum's precompiles if you are running it on a local Hardhat or Anvil(Foundry) node. It defaults to using Sepolia and Arbitrum Sepolia as an L1<>L2 pair.

Deploy Contract

Now in order to deploy you will need to either import a wallet that has funds on the L2 network with yarn account:import or create a new wallet with yarn generate and then fund that wallet (You can view wallet details with yarn account).

Once you have a deployer wallet setup with funds on the L2 network (Arbitrum or Arbitrum Sepolia depending on how you set things up) then you are ready to deploy your contract to the chain using:

    yarn deploy --network arbitrumSepolia

If you are planning to interact with mainnet use arbitrum instead of arbitrumSepolia.

If you hit any hangups, read more in the Scaffold-ETH documentation on deploying contracts.

Start Front End

If you adjusted the deployment from it's default testnet network pair (Sepolia and Arbitrum Sepolia) in the last step then you will need to update the front end by adjusting targetNetworks to [chains.mainnet, chains.arbitrum] in packages/nextjs/scaffold.config.ts.

Next, start the front end by running:

    yarn start

Then open your browser and navigate to http://localhost:3000.

For more details, see the specific Scaffold-ETH docs section.

Now you are ready to use this extension! You can use the provided pages listed in the sections below, to try out the features, or you can view your deployed contract in the 'Debug Contracts' page.

Using the Arbitrum Bridge

Go to the 'Bridge' tab and follow the instructions to bridge some ETH from L1 to L2 or use the other bridge component to move funds from L2 to L1.

Using the Arbitrum Address Table

If you followed the setup instructions and deployed the contract then you can play with the address table precompile by navigating to the 'Address Table' tab above. Go check out the contract so you can see how it works by Arbitrum providing a special "precompile" that allows you to cheaply use indexes that reference addresses instead of the actual address - saving you on gas consumed.

Using Forced Transactions

Go to the 'Forced Tx' tab above. Follow the steps to submit transactions to the Arbitrum Delayed Inbox on L1 - effectively enabling you to post transactions to Arbitrum even if their sequencer would want to censor you. This is one of the key components that makes a layer 2 more than just a sidechain. Typically, the Arbitrum sequencer will not try to censor you and your transaction will post on the L2 within a few minutes of being submitted. If the sequencer does try to censor you, then after 24 hours, you can force the transaction to be included in the L2.