# EigenDA Tracker: Data Availability Usage, Operators and Stake > EigenDA data availability tracked from Ethereum: rollups posting certificates, payments, operators by quorum and the restaked ETH and EIGEN securing each. Markdown copy of https://voltfincrypto.com/apps/eigenda-tracker **Question:** Which rollups use EigenDA, how much data do they post and how much restaked stake secures it? - Kind: Dashboard in Voltfin Vantage - Topic: [Layer 2s](https://voltfincrypto.com/topics/layer-2) - Chains: Ethereum, Celo, Multi-chain - Status: Planned. The data is not published yet, so this page states no figure; each figure will open its receipt when it is. EigenDA is a data availability service built on EigenLayer. Rollups send their batches to EigenDA, whose operators store erasure-coded pieces and sign that the data is available, and the rollup then posts a short certificate instead of the data itself. Operators are restakers who serve one or more quorums, each backed by a different asset, such as restaked ETH or EIGEN. This dashboard reads what EigenDA leaves on Ethereum and on the rollups that use it: operator registrations and stake by quorum, payments to EigenDA's payment vault and the certificates rollups post, each naming a blob and its size. Celo's layer 2, for example, posts to EigenDA V2, which arrived in 2025 with faster confirmation and payments through reservations and on-demand deposits. Figures that need the disperser's own records rather than chain data are marked as off-chain, with their source. Everything else is pinned to the Ethereum or rollup block it was read at, so each figure can be checked again. ## Blueprint ### Usage Rollups posting to EigenDA, their data and their payments. - **Data posted** (MB): Blob bytes named in EigenDA certificates posted in the selected period, in megabytes. - **Rollups using EigenDA** (count): Rollups that posted at least one EigenDA certificate in the selected period. - **Payments to EigenDA** (ETH): ETH deposited to the payment vault for on-demand use in the period, shown beside active reservations. - **Certificates, latest day** (count): EigenDA certificates posted to rollup batch inboxes on the latest complete day. - **Data posted by rollup by day** (MB): Megabytes named in certificates each day, split by rollup. - **Rollups and their data**: Each rollup's certificates, data posted, share of all EigenDA data and payment arrangement over the period. ### Operators and stake Who secures EigenDA, and with how much stake in each quorum. - **Operators registered** (count): Operators registered to at least one EigenDA quorum at the latest day's end. - **Stake securing EigenDA** (ETH and EIGEN): Restaked ETH and EIGEN held by operators in EigenDA's quorums at the latest day's end, each shown in its own unit. - **Stake by operator** (ETH): Stake each of the largest operators holds in the ETH quorum, with its share of the quorum. - **Operators by quorum**: Each operator's quorums, its stake in each, its share of each quorum and the date it registered. Filters: Rollup (Every rollup posting EigenDA certificates); Period (Last 7, 30 or 90 days). ## How it will be measured - Operators and their stake are read from EigenDA's registry and stake contracts on Ethereum at each day's last block: the quorums each operator serves and its stake in each, with restaked ETH and EIGEN kept apart. - Usage comes from the EigenDA certificates rollups post to their batch inboxes, which carry each blob's commitment and length, matched to the rollup that posted them. - Payments are deposits to EigenDA's payment vault for on-demand use and the reservations recorded there, in ETH, valued at oracle prices. - Where a figure needs the disperser's records rather than chain data, it is marked as off-chain and its source is recorded beside it. ## Data it needs - `restaking_daily` (to build): Assets restaked per restaking protocol, strategy and operator per day, and what is delegated to each service. - `blob_usage_daily` (to build): EIP-4844 blobs posted per day, blob gas used, blob base fee, and the rollup that posted them. - `native_prices_daily` (to build): Reference prices of major assets read from on-chain oracle feeds (Chainlink latestRoundData) at each day's last block, with each round's update time. - Source: EigenDA registry and stake contracts on Ethereum: operator registrations, quorums and stake updates - Source: EigenDA certificates in rollup batch inbox transactions, with blob commitments and lengths - Source: Deposits and reservations in EigenDA's payment vault contract - Source: Disperser records where chain data does not cover a figure (off-chain, recorded with its source) ## Questions ### What is EigenDA? A data availability service for rollups, secured by stake restaked through EigenLayer. Operators store erasure-coded chunks of each blob and attest that it is available, and rollups post a compact certificate of that attestation instead of the full data. ### How is EigenDA secured? By operators who register for quorums and hold restaked stake in them, such as restaked ETH or EIGEN. A blob is accepted when operators holding enough of each required quorum's stake have signed for it, so the stake behind each quorum is the measure of its economic security. ### Which rollups use EigenDA? Any rollup whose batches carry EigenDA certificates appears on the dashboard, identified from its batch inbox. Celo's layer 2, for example, uses EigenDA V2. The list is read from the chain, so new users show up as soon as they post. ### What changed in EigenDA V2? V2, also called Blazar, cut the time to confirm that data is available from minutes to under a minute for rollups that adopt its recommended integration, and it introduced payments through reservations and on-demand deposits. ### How does EigenDA differ from Ethereum blobs? Ethereum blobs are stored and checked by Ethereum's own validators for a limited window. EigenDA relies on its own operator set and the stake restaked to it, so a rollup trades Ethereum's validator guarantee for more capacity at a different cost. ## Glossary - **AVS**: An actively validated service: a system, such as EigenDA, secured by operators who restake assets through EigenLayer. - **Quorum**: A group of EigenDA operators backed by one kind of stake; a blob needs signatures from enough stake in each required quorum. - **DA certificate**: The short proof a rollup posts in place of its data, showing that EigenDA operators attested the data is available. ## Related apps - [EigenLayer Restaking: TVL, Operators, AVSs and Slashing](https://voltfincrypto.com/apps/eigenlayer-restaking-dashboard) - [Celestia Blobspace: Data Posted, Blob Fees and Rollups](https://voltfincrypto.com/apps/celestia-blobspace) - [Ethereum Blob Fees and Blobs per Block vs Target](https://voltfincrypto.com/apps/ethereum-blob-fees) - [L2 Profitability: Fees Earned vs Costs Paid to Ethereum](https://voltfincrypto.com/apps/l2-profitability) - [Liquid Restaking Tokens: Backing and Exchange Rates](https://voltfincrypto.com/apps/liquid-restaking-backing) - [Ethereum TPS: Mainnet and Layer 2 Transactions per Second](https://voltfincrypto.com/apps/ethereum-tps) Build it in Voltfin Studio: https://app.voltfincrypto.com/signup?next=%2F