Data Availability Overview
This page shows an overview of common Data Availability (DA) solutions that are used by Layer 2s. DA is becoming more and more important for the modular Layer 2 architecture. Different solutions have different trade-offs with regards to scalability, costs, and security assumptions.
Top 5 DA Consumers
Learn more about this page
Learn more about the Data Availability Overview page and how it is calculated.
Details
Our Data Availability Overview page breaks down important metrics around DA:
- Data Posted: The amount of data that was submitted to the DA layer. Different DA layers can handle different amounts of data based on their scaling capabilities.
- DA Fees Paid: The fees collected by the DA layer for processing and storing data. This is influenced by the amount of data that was processed but also by the fee market structure and demand that a DA layer experiences.
- Fees/MB: The average cost that a Layer 2 pays per Megabyte of data submitted. This value is important for Layer 2s since it directly influences their costs and with that potentially also the transaction costs that they pass on to their users.
- DA Consumers: The Layer 2 networks that have submitted at least 100MB worth of data to the DA layer. Usually, a Layer 2 uses only a single DA layer. But it is also possible that Layer 2s switch between DA layers if this allows them to save costs.
Important Notes:
- In order to provide this type of analysis, we have to map Layer 2s / DA consumers to their respective onchain identifiers. This effort can easily be accessed in our GitHub mapping file.
- If you identify missing Layer 2s on this page, please head over to our GitHub and create a PR. This will help us to keep this page up-to-date.
Related Quick Bites
See all Quick Bites
More Bites
See related quick bites for this metric. Quick bites are blog-style articles that go in-depth on certain topics, backed by live data.
