-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Affected files: cards/Awesome Ethereum.md cards/Awesome Web3Tools.md cards/Rollup.md
- Loading branch information
1 parent
649753c
commit 5182bf4
Showing
3 changed files
with
26 additions
and
4 deletions.
There are no files selected for viewing
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
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
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 |
---|---|---|
@@ -1,3 +1,18 @@ | ||
#explain-card | ||
>[!todo] | ||
> FINISH THIS CARD | ||
#explain-card | ||
|
||
## What is Rollup? | ||
|
||
Rollup is a scaling solution for Ethereum that bundles or "rolls up" multiple transactions into a single transaction on the Ethereum mainnet. These rollup transactions are executed on an off-chain rollup network. To inherit Ethereum's security, the rollup network regularly submits transaction data to the Ethereum mainnet. Once the data is uploaded and stored on Ethereum, reverting a rollup transaction requires reverting the Ethereum transaction. This mechanism allows the single transaction fee on Ethereum to be distributed among many transactions in the rollup network, reducing the overall transaction cost. | ||
|
||
## Types of Rollup | ||
|
||
There are two main popular types of rollup solution: Optimistic rollup and ZK rollup. They differ in how they handle transaction verification and data availability. | ||
|
||
### Optimistic rollup | ||
|
||
Optimistic rollup assumes that transactions are valid by default, the rollup transactions are executed once received and the execution result will be available in the rollup network. Then the rollup operator will bunch these transactions data regularly and submit them to the Ethereum mainnet as calldata or blobs. Optimistic rollup relies on a fraud-proving mechanism to detect the cases that transactions are not executed correctly. There is a time window called challenge period for users to submit fraud proofs to challenge the incorrect rollup transactions. | ||
|
||
### ZK rollup | ||
|
||
### Optimistic rollup vs ZK rollup | ||
|