Original source: BLOB
Compiled by: Shenchao TechFlow
Introduction:
Everyone is saying that Dencun upgrade and EIP-4844 may lead the new narrative of Ethereum and L2, but what exactly are Dencun upgrade and EIP-4844?
We’re not trying to be technologists, but having a clear understanding of technology itself helps us put narrative into perspective.
This article provides an in-depth explanation of the concepts of L1 and L2 blockchains, explores how Layer 2 networks operate prior to the Ethereum Cancun upgrade, and how EIP-4844 will improve the data storage and fee structure of L2 networks.
introduce
What is L1?
Layer 1 (L1) is usually used to refer to a blockchain that does not rely on any external network: it can perform all the functions required for a properly functioning blockchain on its own.
Examples of L1 blockchains include:
Bitcoin
Ethereum
Solana
Avalanche
In addition to operating in a completely independent manner, all these networks have one thing in common: other networks or blockchains can use them as service providers to achieve some specific functionality they require!
These networks that rely on L1 blockchains are called Layer 2 (L2) blockchains.
What is L2?
L2 is a blockchain built on top of L1.
L2 blockchains only perform some of the functions required to have a working decentralized blockchain, they delegate certain functions to another L1 network.
Generally speaking, L2 networks propose to undertake computation (roughly equal to smart contract execution) and delegate transaction durability (often called security) to L1.
Therefore, in this case, the L1 network is often referred to as the L2 data availability layer!
What is the data availability layer?
Data availability layer is a term used to indicate that a given L2 writes its own history to the network, making the data of all transactions that occurred available for anyone to read. This is the most important function L1 performs for L2!
Because the L2 network currently does not work with a network of nodes that stores all transactions processed by the blockchain, L2 must store this history somewhere.
For a simpler explanation, think of L1 and L2 as computers:
L1 is the computer's hard drive, where the computer stores transactions that occur on L2 in case anyone wants to view them
L2 is the computer's CPU, where all operations occur and the results obtained by the application's transactions can be seen. However, that could soon change as new deals arrive
Users can send transactions to L2 just like they would using the L1 blockchain! They can also look up the L1 network where L2 transactions are stored to verify what happened on L2!
Layer 2 Network
Two types of L2
You may have heard of two different types of L2 networks, often referred to as "rollups":
Optimistic rollup
ZK rollup
Although it sounds scary and difficult to understand, the difference is very easy to understand! The differences revolve around how both types of rollups write their transactions to L1, and how they give end users confidence that those transactions have been executed correctly.
Optimistic rollup adopts the following "trust me bro" approach:
Execute incoming transactions on L2
Publish the transaction and its execution results to L1 (providing all the information needed to verify that the transaction has been applied correctly)
Within a fixed period of time, they allow anyone to dispute the results obtained. For example: If tomorrow you discover that Arbitrum incorrectly processed your $BLOB transfer, you can report it. As a result, you will be rewarded and Arbitrum's chain will be corrected to reflect the correct expected results!
ZK rollup takes a more “this is the result, here’s the proof (this is the result, this is the proof)” approach:
ZK rollups use a special version of EVM that can
Execute transaction normally
Produce proof of correct execution
Publish the transaction and proof of its correct execution to L1
Now anyone can verify that L2 executed the transaction correctly by simply checking the provided proof (the most important fact here is that verifying the validity of the proof is easier than running all the transactions and comparing L2's results with yours much cheaper)
How do L2 networks work today?
Generally speaking, we can summarize the functions of L2 into the following steps:
L2 users send transactions: wrap ETH, swap on Sushiswap, lend on AAVE, buy $BLOB, etc.
L2 applies them as transactions come in: that's why you receive the tokens after the swap
L2 will periodically create a batch of transactions and publish them to L1, we will discuss this later
Depending on the type of L2, the deal will either be finalized or enter a dispute period. In the second case, after some time they will also be finalized!
Done, continue to repeat this operation.
Now, I want to dig deeper into how L2 delivers batches of transactions to L1 , because understanding this will clearly explain why we need EIP-4844.
Today, on all EVM blockchains there is something called calldata: this is a special space in a user's transaction where he/she can write anything they want.
Since we can write anything in the calldata of the transaction. The L2s had an idea and wrote their transactions, proofs and execution results here!
Since anything can be written in the calldata of a blockchain transaction, the L2 network hit upon the idea of writing their transactions, proofs, and execution results directly into it. This is a brilliant idea because with calldata, L2 networks can now write their history to Ethereum, resulting in extremely high decentralization and security since Ethereum itself is very decentralized and features that are difficult to modify.
However, writing data to calldata implies a problem that is detrimental to all users of L1 and L2: all transactions will compete in the same fee market!
This means that if gas on Ethereum spikes due to NFT minting, the data publishing costs L2 needs to pay will also increase! This will result in an increased cost of sending transactions on L2! Conversely, if the L2 network needs to publish large amounts of data, this will cause harm to Ethereum users who don’t even care about L2 data!
EIP-4844 Come to put out the fire
Due to the above problems, the Ethereum community came up with a very clever way to solve this bad externality problem: create an independent place where L2 can conduct business quietly.
EIP-4844 brings a simple idea: let L2 do their own thing, without disturbing Ethereum users! To achieve this, it introduces a new transaction type that allows L2 networks to publish all the data they need to blobspace: a new part of the Ethereum block that will specifically host L2 data write transactions.
In addition, EIP-4844 will create an independent fee market so that Ethereum users and the L2 network will not interfere with each other and will not make each other's transactions more expensive. This is equivalent to everyone being safe in their own lane without interference. drive on ground.
This upgrade is expected to reduce gas fees for L2 transactions by approximately 10x!
in conclusion
What will be significantly affected by the Cancun upgrade is the way these networks write and submit specific sets of transactions on Ethereum. From a user perspective, the only major changes will be a significant reduction in gas charges on L2, and possibly less gas spikes on L1!
(The above content is excerpted and reprinted with the authorization of partner MarsBit, original text link | Source: Deep Chao TechFlow)
Statement: The article only represents the author's personal views and opinions, and does not represent the objective views and positions of the blockchain. All contents and opinions are for reference only and do not constitute investment advice. Investors should make their own decisions and transactions, and the author and Blockchain Client will not be held responsible for any direct or indirect losses caused by investors' transactions.
〈[Must-read for newbies] EIP-4844 Popular Science: Before Dencun upgrade, what are the problems with L2? 〉This article was first published in "Block Guest".
