EigenDA Transport Spec

[just-a-node]

Background

Problem: For eigenDA to support L3 rollups (e.g. Arbitrum Orbit), their AVS data on Ethereum L1 needs to be transported to other L2s. They ideally want to do this in a way that is easily extensible to many rollup ecosystems and beyond - once this data is available on a given chain, it becomes possible to build EigenDA-integrated rollups on top of that chain.

Solution: Use Connext's messaging layer (which plugs into the most "native" transport for any given eco) to bridge attestations/data from L1. This is quite straightforward in our system and we've done very similar integrations to bridge oracle prices, attestations, and other relevant data from mainnet in the past.

Open Questions:

1. How does Eigenlayer post AVS data to Ethereum L1? How is this data structured?
2. At what point in the lifecycle should that data be bridged?
3. How does EigenDA consume AVS data? Does it expect data to be posted to it, or does it read from a store?
4. What are the failure modes of the system? How should Connext/Eigenlayer handle these failure modes?

Linked Issues & Documentation

Spec TBD

Tasks

• [ ] Write technical specification of the transport system

[just-a-node]

This will likely become AVS research for Chimera