-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
30 changed files
with
113 additions
and
885 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Binary file not shown.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
id: introduction | ||
title: '' | ||
slug: / | ||
hide_table_of_contents: false | ||
--- | ||
|
||
import useBaseUrl from '@docusaurus/useBaseUrl'; | ||
|
||
EthDA is an Ethereum ZK L2 with native EIP-4844 blob-carrying transactions (Blob TX) support. This seamless interface makes EthDA a perfect fit for Alt-DA for Ethereum L2s and dStorage solution for EVM DApps. | ||
|
||
There are various Ethereum scaling solutions like sidechains, rollups, plasma and validium, etc, with different characteristics and trade-offs between security, decentralization, and throughput, etc. One of the most essential differences is Data Availability. Using Ethereum L1 as DA derives security from Ethereum and that's the reason why rollups are widely regarded as the only trustless scaling solution in the medium and long term. But posting L2 transaction data to L1 requires high gas consumption and may cause congestion on L1. This situation becomes even worse as L2 ecosystem prospers. | ||
|
||
The long term and canonical solution to this DA dilemma is Danksharding, and the medium term solution is EIP-4844, or Proto-Danksharding, which the Ethereum community is actively working on as part of the upcoming Cancun-Deneb upgrade. EIP-4844 introduces a new type of Blob TX that rollups could use to post their L2 transaction bundle to L1 in a gas efficient manner. Blob transaction is forwards compatible with Danksharding, and the carried Blobs will be persisted by the consensus layer for a limited period like 4 weeks. | ||
|
||
However, since EIP-4844 takes time to implement and deploy (not to mention the full Danksharding), it's observed that some rollups are opting for Alt-DA solutions like Celestia, and Avail, etc. Both Celestia and Avail are separate blockchains built on top of different technical stacks and providing their own Data Availability interface. | ||
|
||
EthDA, as a contrast, is an Ethereum native Alt-DA solution, in that: | ||
- EthDA itself is an Ethereum ZK validium, and is administered by a collection of smart contracts deployed on Ethereum L1 | ||
- EthDA provides a seamless Data Availability interface as L1 to Alt-DA chain users, allowing their sequencers to pay storage fees with native $ETH |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.