Arbitrum Orbit Deployment

Arbitrum Orbit is a Rollup Development Kit (RDK) developed by Offchain Labs to enable rollup developers to build using the same software that powers Arbitrum One and Arbitrum Nova.

EigenDA Proxy

Arbitrum nodes communicate with EigenDA via the proxy for secure communication and low code overhead. More information can be found here. An instance of proxy must be spun-up to use this integration securely. In your node config, this will look like:

"eigen-da": {"enable": true,"rpc": "http://eigenda_proxy:4242"}

How to deploy a Rollup Creator integrated with EigenDA

1. Assuming you have yarn and hardhat installed.

2. Download the nitro contracts source code from the EigenDA Nitro contracts fork using the latest stable version release.

3. Within the high level directory, create a new deployment config using existing template:

cp scripts/config.ts.example scripts/config.ts

Based on your parent chain level (i.e, L1 vs L2), update the maxDataSize field accordingly. Typically this is set as:

• 117964 for L2s settling to Ethereum
• 104857 for L3s

Please note that this is set in accordance with network specific parameters (i,e tx calldata limits) and may require changing when deploying to novel settlement domains

4. Run command to initiate the deployment:

yarn deploy-factory --network ${NETWORK_ID} 

To see all relevant environment context to understand which env vars to provide, please advise the hardhat.config.ts file for a more in-depth breakdown.

The script will take a few minutes to complete as it prints out the addresses of the deployed contracts along the way. Upon completion, your rollup creator factory is ready to use for new chain deployments!

Since this script is hardhat, there are no state checkpoints that happen if a terminal failure occurs midway through execution. Please use at your own risk and ensure that you're connected to a stable RPC provider and have sufficient funds before beginning the deployment.

Deploy using our hosted Rollup Creators

The Orbit documentation provides a comprehensive overview for how one can trigger new chain deployments using already deployed rollup creators. If you'd like to leverage the orbit-sdk please use our fork here.

Additionally, we maintain the following factories:

contracts version	network	rollup creator address	cert verifier address
v2.1.3	Ethereum Mainnet	0xdD6258539c41687B9afd38983c0456493423C73d	0x787c88E70900f6AE10E7B9D18024482895EBD1eb
v2.1.3	Ethereum Holesky	0x22AaeA3A47d73e9585D0378D1d9e1CeF7Cd8c6a1	0xFe52fE1940858DCb6e12153E2104aD0fDFbE1162
v2.1.3	Arbitrum Mainnet	0x4231Dd9e6717aB9a9ABC5618d8a4Fcf1a432F698	NA
v2.1.3	Arbitrum Sepolia	0x0F7f71c48c6278422736a4a9441cd1d59ba0C2dB	NA
v2.1.3	Base Mainnet	0xcC272c9249d1638B7985eFb84c0E9Cdc001b73F7	NA
v2.1.3	Base Sepolia	0xfc2a0CD44A6CB0b72d5a7F8Db2C044F62db50781	NA

The cert verifier address is necessary for verifying V1 EigenDA blobs within the SequencerInbox to remove a trust assumption on the sequencer. This can be set within the params section of the orbit sdk

As well as Orbit upgrade actions:

action version	network	address
eigenda-v2.1.3	Ethereum Holesky	0x31C2C3dd9C47049a975DFaE804C886333CDCF9BB
eigenda-v2.1.3	Arbitrum Sepolia	0xc5d5c28F94c95D851a42Ff97f1886f8af505BD04
eigenda-v2.1.3	Base Sepolia	0xbda5cff32ce4b2a1e312439e21d1b163d48b0936

How to deploy a Rollup on Testnet using our UI

While you can interact with the deployed Rollup creator directly, we recommend using our orbit chain deployment portal to deploy a rollup for a friendlier devx and easy-to-use configs. Currently, the UI only supports testnets for:

• Ethereum Holesky
• Arbitrum Sepolia

Troubleshooting

If your nitro setup script node encounters a warning error getting latest batch count: no contract code at given address, you should first verify that:

• (1) That the SequencerInbox entry in your /config/orbitSetupScriptConfig maps to a successfully deployed contract
• (2) Your RPC provider is sufficiently reliable. Transient errors are common when leveraging free and public RPC providers

Token Bridge

The Arbitrum token bridge can be enabled to support L1 to/from L2 bridging of ERC-20 assets. Since the token bridge is a wrapper on-top of the existing L1 to/from L2 native bridge, there are no changes necessary to enable it. Additionally, the existing token bridge creators maintained by Offchain labs can be leveraged to deploy token bridges on-top of existing inboxes integrated EigenDA.