Ethereum Dencun upgrade has been deployed: Vernacular to help you understand EIP4844

The Ethereum Dencun upgrade was officially deployed on the Ethereum mainnet at 1:00 pm GMT on March 13th, which is 9:00 pm Beijing time last night. We can find the first transaction with Blob data after the upgrade (the core point of this upgrade, which will be discussed in detail later): https://etherscan.io/tx/0x1e3763c5200cd39e70d498accc9be78fa3defca2342383e429f6bb22d714315c

We can see that the Blob data is , after decoding we can see From astaria.xyz with love, Joe Delong, Justin Bram, Wesley Rafuse, Justin Greenberg, Greg Curtis, Mark Lenser, Marco Kaul, Kaloyan Mitev, Chase Hawes, Tim Clancy, obviously this is from astaria pay tribute.

Next let’s take a look at what exactly the Dencun upgrade has upgraded.

The core of Dencun’s upgrade is EIP4844, which supports the Blob information contained in the above transaction. Of course, there are other upgrades, but this article focuses on EIP4844.

For EIP4844, please refer to https://eips.ethereum.org/EIPS/eip-4844 for specific specifications. The details of this specification are very complex and involve other related specifications, so the specific details will not be expanded upon. Next, let everyone understand in plain language what the specification is and what changes it can bring to Ethereum.

To put it simply, EIP4844 enables the Ethereum block to support a newly defined Blob data. You can understand Blob data as a kind of temporary data, which will probably only exist on Ethereum. Store for 18 days. I think most people should have thought about a question: "The data on the blockchain cannot be changed or deleted. This is true as the core value of the blockchain, but in this way the data will become more and more complex." What to do if more and more come? 』

Obviously Blob is intended to partially solve this problem, because in fact there is no need for a lot of data to be stored on Ethereum for a long time. For example, the data generated by L2 can be stored at most once a consensus is reached on Ethereum. After waiting for a period of time to accept the "fraud proof" challenge, the data will no longer exist.

Blob can open up a temporary space to store temporary data like this when initiating a transaction. Obviously, the cost of temporary data storage will be lower, and the corresponding designed GAS will also be lower, so that Let the transaction gas fees generated by some transactions, especially L2, be reduced. This is of great significance to Ethereum and many L2s on Ethereum. For example, the author compared the GAS difference of L2 Starknet before and after the Dencun upgrade. The difference is as much as a hundred times:

After upgrade

Before upgrade

It is also a transfer of STRK, which was consumed before upgrade 0.467 STRK, only 0.005 STRK required after upgrade. Of course, this data will be affected by various other factors. It is shown here for reference only. For more specific data, you can follow up on more related reports.

Let’s take a specific look at the performance of Blobs on Ethereum. We can see Blob-related information in a relatively new block 19430289. 128 kiB corresponds to 1 blob, and the Gas Price is only 1wei.

After entering the Blob transaction point, you will find that it is a StarkNet transaction:

The corresponding data can also be seen:

The link is https://etherscan.io/blob/0x01427b295210a49580d0bf75af2d1a0efcf32a2c686f9b 04f43b6a5e531f4788?bid=2067, interested friends can study it.

Among all the transactions after the current upgrade, tx.type = 3 (blob tx) only accounts for 0.3%, but we can see thatthe upgrade has brought immediate results to L2, and it also means a lot to Ethereum It is significant. I believe that with the continuous development of blockchain technology, the performance and cost of blockchain will continue to improve. The day when blockchain will be universally beneficial is getting closer and closer to us.

ZAN Node (https://zan.top/home/node-service?partner=jscj) has successfully completed the upgrade of the Ethereum node and is supporting Integration and exposure of Eth Beacon API interfaces including Blob data query.