Partnered With:

Opinion: Ethereum is closer to massive scaling than we think

Read this article in 6 Minutes

EIP-4844 is a game changer for the Rollup-centric roadmap.

Author of the original text: liam.eth, CEO of OP Labs

Compilation of the original text: The Way of DeFi

Ethereum core developers will A conference call will be held on Thursday to discuss whether EIP-4844 should be considered (CFI).

This is a big moment for the many teams working to bring this EIP into production!

Here's why I think EIP-4844 should be taken into consideration.

Reminder: EIP-4844 adds a new fee market for short-term data on Ethereum, which Rollup will use to improve data availability.

This is a game-changer for Rollup-centric roadmaps as fees can be reduced ~100x.

TL;DR Why 4844 should be considered:

Based on withdrawals

Specification ~ completed after 9+ months of iteration

Interop repo with stress test

KZG ceremony specification completed + working Front-end

KZG library supports Node, C#, Rust, Python, etc.

Devnet v3 will support 6/9 major clients

Let me explain each part. First, EIP-4844 is built on top of the withdrawal specification. Both the enforcement layer and the consensus layer work directly on top of the existing withdrawal implementation. No need to rebuild, it's purely additive.

The specification has undergone 9 months of intensive iterations, and the remaining changes have been minimal.

Most client teams have reviewed (and even implemented) it! Additionally, there are complementary consensus layer and engine API specifications.

https://github.com/ethereum/execution-apis/blob/main/src/engine/blob-extension.md

There has been a lot of developer work on interoperability, which has resulted in multiple different devnets and additional network stress testing by Georgios Konstantopoulos. Conservatively, though, we have reduced the blobs parameter for the initial iteration.

https://github.com/Inphi/eip4844-interop

In KZG trusted settings As for the ceremony, we are ready.

There is a completed specification with three front-end implementations, and a sequencer implemented and reviewed.

https://github.com/ethereum/kzg-ceremony-specs

In order to implement Smoother and more reliable, we've also made significant progress in the KZG library. C-kzg-4844 is active and implements the required components using NodeJS, CSharp, Python with Rust bindings in progress. Go-KZG is ready.

https://github.com/ethereum/c-kzg-4844/

We are Great progress has also been made on the developer testnet (devnet).

The next devnet v3 will support 6 of the 9 major clients (not bad) and should be ready by November 30th.

https://notes.ethereum.org/@timbeiko/4844-devnet-3

The community and ecosystem has been keeping up with the ever-evolving public site that contains all this information and has been for almost a year now.

https://www.eip4844.com/

In my opinion, EIP-4844 It is the most promising EIP to contribute to the future of Ethereum after The Merge.

Several L2 teams, various core developers from the Ethereum Foundation, large crypto operations, and major new projects have all contributed to it because We want to see Ethereum win.

Now, I would like to add that CFI is not meant to be "included" in the next hard fork upgrade. The decision on Shanghai's promotion is an independent process.

However, given that both EIP-4844 and the withdrawal involve both the consensus layer and the execution layer, there seems to be good reason to consider it for inclusion in the Shanghai upgrade.

In any case, I hope that in the upcoming ACD conference call, we will be able to understand the status of EIP-4844 and make a strong decision on the justification of CFI status judgment!

If you have any thoughts on this EIP and would like to comment on the next ACD conference call, please check the agenda:

< /p>

https://github.com/ethereum/pm/issues/450