Vitalik Buterin, the co-founder of Ethereum (ETH) is introducing a new Ethereum Improvement Proposal named EIP-4844, which is based on proto-danksharding, a new way to organize data logistics.
Buterin shared this improvement proposal via his official Twitter handle about two days ago.
As Sharding itself is described as the existence of interconnected sub-blockchains instead of a single one, Buterin says Danksharding is the new sharding design proposed for Ethereum to introduce some notable simplifications compared to previous designs.
Read Also: Ethereum Staking’s Biggest Deposit since December 2020; Over 200,000 ETH Staked in A Single Day
My own EIP-4844 (aka. proto-danksharding) technical FAQ:https://t.co/SlgNERBYVc
— vitalik.eth (@VitalikButerin) March 19, 2022
How Buterin Describes Proto-Danksharding (EIP-4844)
According to Vitalik Buterin, Proto-danksharding (aka. EIP-4844) is proposed to implement most of the logic and scaffolding, e.g. transaction formats, verification rules, which make up a full Danksharding spec, but not yet really implementing any sharding.
Buterin added that in a prototype implementation, all validators and users still have to directly validate the availability of the full data.
Proto-danksharding can also be described as a scenario of data verification focused on blob-carrying transactions that cannot be executed by Ethereum Virtual Machine (EVM).
Buterin says Proto-danksharding creates “a separate transaction type that can hold cheaper data in large fixed-size blobs, with a limit on how many blobs can be included per block. These blobs are not accessible from the EVM (only commitments to the blobs are), and the blobs are stored by the consensus layer (beacon chain) instead of the execution layer.”
The new development shows that Proto-danksharding is set to replace dansharding, a sharding technique in which only one proposer chooses all transactions.
However, the proposed solution could be short-term because it includes the implementation of a number of danksharding elements. It can also lead to an increase in data usage due to the need for a much bigger block size.
So, in order to prevent the network from having too much data to deal with, the Ethereum co-founder proposes to auto-delete blob data every 30 days.
Follow us on Twitter, Facebook, Telegram, and Google News
