Ethereum is proposing EIP-8142 to replace transaction data with BLOB objects to enhance scalability and reduce bandwidth demands.
Ethereum developers are proposing a significant change aimed at boosting the blockchain's scalability by introducing transaction data stored in BLOB objects alongside blocks. This proposal is detailed in a draft standard known as EIP-8142, or Block-in-Blobs, authored by Tony Varshteyter and a team of developers.
The primary goal of this initiative is to alleviate bandwidth demands while enhancing the overall performance of the network. By encoding transaction data directly into BLOBs, validators will be spared the need to download and process large data payloads, which can overwhelm the network.
As stated by the authors, current architectural limitations are exacerbated by increasing block sizes and gas limits, compelling validators to manage more and more data, thus impeding network growth.
The rollout of BLOBs is anticipated to coincide with the Dencun hard fork in March 2024, as part of the data availability roadmap. This feature, enabled by EIP-4844 (proto-danksharding), is designed to improve the efficient transfer of large data sets.
Contrary to traditional on-chain storage, BLOB objects facilitate cryptographic verification of data without necessitating full replication across the blockchain.
Core Concepts of EIP-8142
EIP-8142 expands upon ideas introduced in the Dencun upgrade by moving the primary transaction payload into BLOBs, transitioning from their previous role as mere supplementary data layers. Validators will be able to check cryptographic confirmations of these BLOBs and will adapt to a data availability sampling (DAS) mechanism to verify portions of data without needing the entire dataset.
This transition will be particularly vital for the future integration of zkEVM systems, which utilize zero-knowledge proofs (ZKPs) to verify transaction accuracy without re-execution. Nonetheless, ZKPs do not ensure data availability by themselves, as highlighted by Varshteyter, who pointed out the need for a robust control mechanism to prevent obscured information post-consensus. The Block-in-Blobs proposal aims to mitigate this risk.
The forthcoming changes will also affect the Ethereum fee structure, which currently distinguishes between transaction execution gas and BLOB usage gas. The new model aims to merge these into a unified "data gas," potentially standardizing costs for various data availability methods and preventing conflicting limits.
Collaborative Efforts in Transaction Structuring
In parallel, Biconomy, in collaboration with the Ethereum Foundation's UX team, is pushing forward the ERC-8211 standard. This initiative reimagines transaction structures to create programmable workflows, enabling real-time data retrieval and conditional operation execution, which could greatly reduce failed transactions and streamline interactions within decentralized finance (DeFi) protocols.
These proposals reflect a broader strategy for advancing the Ethereum network, with developers laying out potential upgrade paths through the next decade, including efforts to unify the disparate landscape of second-layer networks with contributions from Gnosis and Zisk, supported by the Ethereum Foundation.
