Search
Search projects, tokens and protocols by name or address
And more
Pinned
Recently viewed
Pin a project to keep it here. Saved only in this browser.
Data Availability
Others are L2s that either lack a working proof system or don't provide sufficient external DA guarantees (i.e. at least 5 independent attesters, a high enough threshold, or a proper DA bridge). To be listed in this category, the L2 must enshrine deposits from L1.
Columns
Columns
# | name | Past day data posted 7D% | DA Layer | DA Bridge | Type of data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
# | name | Past day data posted 7D% | DA Layer | DA Bridge | Type of data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
# | name | Past day data posted 7D% | DA Layer | DA Bridge | Type of data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |  | No data | The data is custodied by Hyperliquid validators. On Arbitrum there is no direct reference of the data. | There is no bridge that can attest if the data has been made available. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 |  | No data | The data is guaranteed to be available by Polygon proof of stake validators. On Ethereum, the data is indirectly referenced in the signed block header. | The bridge verifies that at least 2/3+1 of the Polygon PoS stake has signed off on the checkpoint. The StakeManager contract is the source of truth for the current validator set. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 |  | 496.88 MiB23.8% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 |  | 116.88 MiB32.7% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
5 |  | No data | The data is guaranteed to be available by Gnosis proof-of-stake validators. On Ethereum, the data is not published or referenced directly. | Transaction data is published to Gnosis Chain and made available by its proof-of-stake validator network. Ethereum contracts do not receive transaction data or data commitments. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
6 |  | No data | The data is posted to EigenDA which is a separate data availability layer developed by the Eigenlayer team. Only commitments to the data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7 |  | 193.25 MiB6.24% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
8 |  | No data | The data is posted to FraxtalDA which is a separate data availability module developed by the Frax Core Team. Data is posted off chain, and only hashes of blob data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
9 |  | No data | Lighter state differences are posted as calldata on Robinhood Chain. Robinhood Chain ultimately posts its transaction data to Ethereum blobs. | The validating bridge has access to all the data, as it is posted onchain. | State diffs | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
10 |  | No data | The data is posted to Celestia. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11 |  | 3.00 MiB4.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
12 |  | 3.00 MiB0.00% | The data is posted to EigenDA which is a separate data availability layer developed by the Eigenlayer team. Only commitments to the data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
13 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
14 |  | No data | ApeX state differences are posted as calldata on Arbitrum One. Arbitrum ultimately posts its transaction data to Ethereum blobs. | The validating bridge has access to all the data, as it is posted onchain. | State diffs | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
15 |  | No data | The data is posted to EigenDA which is a separate data availability layer developed by the Eigenlayer team. Only commitments to the data are published on an onchain inbox. | EigenDA V3 certificates are verified by the proof system through the DACert Verifier contract, which validates certificates against operator signatures and stake thresholds. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
16 |  | 23.00 MiB10.8% | Encrypted data is posted on Ethereum as blobs, and a privacy council of 3 members holds the decryption keys. Users are not able to independetly reconstruct the L2 state without relying on the council members. | There is a threshold of 3/3 members that must sign and attest that the data is correct and available. | State diffs | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
17 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
18 |  | 5.13 MiB4.65% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
19 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | State diffs Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
20 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 |  | 4.50 MiB86.1% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
22 |  | No data | The data is posted to EigenDA which is a separate data availability layer developed by the Eigenlayer team. Only commitments to the data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
23 |  | No data | The data is posted to EigenDA which is a separate data availability layer developed by the Eigenlayer team. Only commitments to the data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
24 |  | 2.63 MiB90.1% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
25 |  | No data | The data is posted to Espresso. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 5/7 members that must sign and attest that the data is correct and available. | Transaction data Compressed | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
26 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
27 |  | No data | The data is posted to Celestia. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
28 |  | 1.00 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
29 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
30 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
31 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
32 |  | 19.88 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
33 |  | 6.13 MiB12.5% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
34 |  | 3.75 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
35 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
36 |  | No data | The data is posted to Celestia. | There is no bridge that can attest if the data has been made available. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
37 |  | 1.00 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
38 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
39 |  | 640.00 KiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
40 |  | No data | The data is posted to an off-chain data availability provider which is tasked to serve data upon request. Only hashes of the data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. However, there is a mechanism that allows users to challenge the unavailability of data. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
41 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 2/2 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
42 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | None | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
43 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
44 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
45 |  | 11.00 MiB3.52% | The data is posted to Ethereum as blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
46 |  | 13.00 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
47 |  | 38.25 MiB0.64% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
48 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
49 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | The bridge verifies that at least 2/3+1 of the whitelisted validators stake has signed off on the checkpoint. The StakeManager contract is the source of truth for the current validator set. The identity of the validators is not public, so it is not possible to verify the presence of sybils, or the number of different entities behind the validators. Since members are whitelisted, the validator set effectively acts as a permissioned DAC. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
50 |  | 1.88 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
51 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 3/5 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
52 |  | No data | The data is posted to Celestia. | There is no bridge that can attest if the data has been made available. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
53 |  | No data | The data is posted to Celestia. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
54 |  | No data | The data is posted to EigenDA which is a separate data availability layer developed by the Eigenlayer team. Only commitments to the data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
55 |  | 1.00 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
56 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
57 |  | 44.75 MiB0.55% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
58 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
59 |  | 896.00 KiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
60 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 3/5 members that must sign and attest that the data is correct and available. | State diffs | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
61 |  | No data | The data is posted to an off-chain data availability provider which is tasked to serve data upon request. Only hashes of the data are published on an onchain inbox. | There is no bridge that can attest if the data has been made available. However, there is a mechanism that allows users to challenge the unavailability of data. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
62 |  | No data | The data is posted to Espresso. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
63 |  | No data | The data is posted to Celestia. | There is no bridge that can attest if the data has been made available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
64 |  | No data | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
65 |  | 2.00 MiB0.00% | The data is posted to Ethereum as calldata or blobs. | The validating bridge has access to all the data, as it is posted onchain. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
66 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | Transaction data | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
67 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | State diffs Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
68 |  | No data | The data is posted off chain and a Data Availability Committee (DAC) is responsible for protecting and supplying it. | There is a threshold of 1/1 members that must sign and attest that the data is correct and available. | Transaction data Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
69 |  | No data | The data is not posted to any data availability layer. | There is no bridge that can attest if the data has been made available. | State diffs Compressed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||