TLDR: EIP-4844 and the concept of Data Blobs will improve transaction efficiency and reduce costs for users. By introducing a new transaction type and implementing new data storage mechanisms, Ethereum will enhance its scalability (rollups) and sustainability.
Dencun Upgrade: The Ethereum network will implement a significant upgrade by 03/13 which includes several EIPs. Among these proposals, EIP-4844 stands out as a crucial addition, bringing forth a new transaction type and the concept of "Data Blobs" to the Ethereum ecosystem.
EIP-4844 introduces a new transaction type to Ethereum that allows for the inclusion of "blobs" of data to be stored in the beacon node for a limited period. Unlike traditional transactions, the data stored in these blobs is not directly accessible in the EVM but is instead available only to nodes in the Consensus Layer, reducing costs.
Benefits of EIP-4844:
Lower Transaction Costs: One of the primary benefits of EIP-4844 is the reduction in transaction costs for rollups by addressing the call data fees to Layer 1, which constitute a significant portion of total fees (90-95%). The remaining 5-10% represents the Layer 2 gas fees. Therefore, EIP-4844 aims to make transactions more cost-effective for users.
Introduction of Data Blobs: Data Blobs represent a new way of storing data on the Ethereum network. Essentially, Data Blobs are collections of binary data, such as rollup merkle trees, which are stored in the beacon chain. While working with Data Blobs may present challenges for developers, they offer the advantage of reduced gas fees compared to traditional transaction formats.
Key Characteristics of Data Blobs:
Binary Large Object: The term "Blob" stands for "Binary Large Object," the data is part of the beacon chain rather than the execution layer, and is downloaded by all consensus nodes. It can be deleted after a relatively short period, typically around two weeks, striking a balance between data availability and storage efficiency.
Tech specs: Each Blob consists of 4096 field-elements, with each element being 32 bytes long. The maximum number of Blobs per block is capped at 16, resulting in a maximum block size of 2 MiB.
TLDR: EIP-4844 and the concept of Data Blobs will improve transaction efficiency and reduce costs for users. By introducing a new transaction type and implementing new data storage mechanisms, Ethereum will enhance its scalability (rollups) and sustainability.
Dencun Upgrade: The Ethereum network will implement a significant upgrade by 03/13 which includes several EIPs. Among these proposals, EIP-4844 stands out as a crucial addition, bringing forth a new transaction type and the concept of "Data Blobs" to the Ethereum ecosystem.
EIP-4844 introduces a new transaction type to Ethereum that allows for the inclusion of "blobs" of data to be stored in the beacon node for a limited period. Unlike traditional transactions, the data stored in these blobs is not directly accessible in the EVM but is instead available only to nodes in the Consensus Layer, reducing costs.
Benefits of EIP-4844:
Lower Transaction Costs: One of the primary benefits of EIP-4844 is the reduction in transaction costs for rollups by addressing the call data fees to Layer 1, which constitute a significant portion of total fees (90-95%). The remaining 5-10% represents the Layer 2 gas fees. Therefore, EIP-4844 aims to make transactions more cost-effective for users.
Introduction of Data Blobs: Data Blobs represent a new way of storing data on the Ethereum network. Essentially, Data Blobs are collections of binary data, such as rollup merkle trees, which are stored in the beacon chain. While working with Data Blobs may present challenges for developers, they offer the advantage of reduced gas fees compared to traditional transaction formats.
Key Characteristics of Data Blobs:
Binary Large Object: The term "Blob" stands for "Binary Large Object," the data is part of the beacon chain rather than the execution layer, and is downloaded by all consensus nodes. It can be deleted after a relatively short period, typically around two weeks, striking a balance between data availability and storage efficiency.
Tech specs: Each Blob consists of 4096 field-elements, with each element being 32 bytes long. The maximum number of Blobs per block is capped at 16, resulting in a maximum block size of 2 MiB.
Share Dialog
Share Dialog
Subscribe to al3jandro.eth
Subscribe to al3jandro.eth
al3jandro.eth
al3jandro.eth
<100 subscribers
<100 subscribers
No activity yet