Skip to main content

Migrating your Orbit Chain to use EigenDA

Defined below is the process for which you can use to migrate your vanilla Arbitrum sequencer using native Arbitrum DA (i.e, Ethereum calldata, 4844 blobs, anytrust) to one using high throughput and low cost via EigenDA. This procedure is identical regardless of your parent chain context (e.g, Ethereum, Arbitrum One) with varying security implications based on the depth of your deployment.

Procedure

  1. Ensure your node software is on the latest vanilla Arbitrum Nitro version. This can typically be found via referencing the Offchain Labs nitro github releases or Arbitrum developer docs.

  2. Perform node upgrade to use latest EigenDA x Nitro version. Please ensure that the fork version is equivalent to the nitro reference. The EigenDA x Nitro fork is designed to be backwards compatible with the latest Arbitrum release and should operate using native Arbitrum DA without any liveness compromises.

  3. Invoke the eigenda v2.1.3 migration action to upgrade the parent chain contracts to use EigenDA ones. Instructions can be found here onto how to do this. This will apply necessary eigenda contract upgrades and update the wasmModuleRoot to the one necessary for the new replay script used for performing validations with the EigenDA batch destination type. This action must be ran before enabling EigenDA feature flags on the node backend configs.

  4. Update your Arbitrum node configs to enable EigenDA. This includes changes to your batch posters, validators, and sequencer node configs; i.e:

  • Update node json config to use eigenda-proxy configuration; ie:

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

  1. Verify your deployment. Steps on how to do this can be found via our developer runbook.