← Protocols
EigenDA
01Description

Ethereum-restaked data availability service built on EigenLayer. Rollups disperse blobs across operators staking restaked ETH/EIGEN; KZG commitments are posted on Ethereum for verification.

02Best for
  • 01high-throughput L2 DA
  • 02Ethereum-aligned rollups
  • 03EigenLayer-secured AVS DA
  • 04Custom Quorum projects
  • 05OP Stack / Orbit DA backend
03Install
  • go install github.com/Layr-Labs/eigenda/api/clients/v2/disperser@latest
04Environment variables
VariableScopeDescription
EIGENDA_DISPERSER_URLServerEigenDA disperser gRPC endpoint (mainnet or holesky testnet).
EIGENDA_SIGNER_PRIVATE_KEYServerPrivate key used to sign blob dispersal requests (payment account).
05Prompt snippet
Use EigenDA for data availability. Use the EigenDA client (Go) or proxy sidecar to call `DisperseBlob` against the disperser gRPC endpoint; you receive a request ID and KZG blob commitment. Poll `GetBlobStatus` until `CONFIRMED` (operator quorum signed) or `FINALIZED` (batch posted to Ethereum). Persist the BlobHeader + cert; verify on-chain via the EigenDAServiceManager `verifyBlob` or via the EigenDA proxy adapter for OP Stack/Orbit.
06Gotchas
  • Confirmation latency is ~10s for operator quorum but several minutes for Ethereum finalization — pick the right inclusion bar per use case.
  • KZG ceremony trust assumption applies; commitments rely on the trusted setup that backs the Ethereum 4844 ceremony.
  • Custom Quorums let you stake your own token but bootstrapping operator coverage takes time and ops effort.
  • Payment is via on-chain reservation/meter accounts on Ethereum — keep the dispersal account funded or dispersals are rejected.
  • Operator availability is probabilistic; for safety-critical apps, also pin blobs to a redundant DA (e.g., Ethereum 4844) until finalization.
  • Max blob size per dispersal is capped (single-digit MB tier); larger batches must be sharded.
07Alternatives