{"id":96013,"date":"2026-04-08T15:37:13","date_gmt":"2026-04-08T12:37:13","guid":{"rendered":"https:\/\/forklog.com\/en\/?p=96013"},"modified":"2026-04-08T15:40:17","modified_gmt":"2026-04-08T12:40:17","slug":"ethereums-eip-8142-to-replace-blocks-with-blobs-for-scalability","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/ethereums-eip-8142-to-replace-blocks-with-blobs-for-scalability\/","title":{"rendered":"Ethereum&#8217;s EIP-8142 to Replace Blocks with &#8216;Blobs&#8217; for Scalability"},"content":{"rendered":"<p>Ethereum researchers are <a href=\"https:\/\/ethresear.ch\/t\/blocks-are-dead-long-live-blobs\/24611\">considering<\/a> a proposal to transfer transaction data into <span data-descr=\"large binary data arrays\" class=\"old_tooltip\">BLOB<\/span> objects, which are published alongside blocks. The initiative aims to reduce bandwidth requirements and enhance blockchain scalability.<\/p>\n<p><!--more--><\/p>\n<p>In the article &#8220;Blocks are Dead. Long Live Blobs,&#8221; Tony Warshtetter and other developers outlined a draft of the <a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-8142\">EIP-8142<\/a> standard, also known as Block-in-Blobs. The concept proposes encoding transaction data directly into &#8220;blobs,&#8221; eliminating the need for validators to download and re-execute the full payload.<\/p>\n<p>According to the authors, this approach addresses architectural bottlenecks. Increasing block sizes combined with higher gas limits forces validators to process a growing volume of data, which overloads the network and limits its development.<\/p>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" src=\"https:\/\/forklog.com\/wp-content\/uploads\/img-b042fd32c7cf144e-1252890393302175.webp\" alt=\"gas_limit\" class=\"wp-image-278162\"\/><figcaption class=\"wp-element-caption\">Dynamics of the gas limit in Ethereum. Source: <a href=\"https:\/\/ycharts.com\/indicators\/ethereum_average_gas_limit\">YCharts<\/a>.<\/figcaption><\/figure>\n<p>&#8220;Blobs&#8221; emerged in March 2024 with the activation of the <a href=\"https:\/\/forklog.com\/en\/news\/how-the-dencun-hard-fork-will-change-ethereum\">Dencun<\/a> hard fork as part of the data availability roadmap. Implemented through <a href=\"https:\/\/forklog.com\/en\/news\/how-eip-4844-will-affect-ordinary-ethereum-users\">EIP-4844<\/a> (proto-danksharding), they are designed for the efficient transfer of large data arrays, as opposed to standard transaction calls (calldata).<\/p>\n<p>Unlike on-chain storage of all details, BLOB objects allow for cryptographic fixing and verification of data without full replication across the network.<\/p>\n<h2 class=\"wp-block-heading\">Block-in-Blobs<\/h2>\n<p>EIP-8142 builds on the concept established in Dencun. The proposal transfers the main payload, already encoded in the RLP standard, directly into &#8220;blobs,&#8221; moving away from their use solely as an auxiliary data layer.<\/p>\n<p>Validators will verify cryptographic proofs of BLOB objects and eventually transition to a data availability sampling (DAS) mechanism. This will enable them to verify small fragments to confirm the presence of the entire data array without downloading it in full.<\/p>\n<p>The change is expected to become particularly relevant in the future when systems like <a href=\"https:\/\/forklog.com\/en\/news\/what-is-zkevm\">zkEVM<\/a> will be responsible for transaction execution verification. Zero-knowledge proofs (<a href=\"https:\/\/forklog.com\/en\/news\/what-is-a-zero-knowledge-proof\">ZKP<\/a>) can confirm the correctness of operations processing, eliminating the need for their re-execution.<\/p>\n<p>However, ZKP alone does not guarantee actual data availability. Warshtetter explained that in zkEVM, proofs are verified rather than transactions directly. Without a separate control mechanism, information may be hidden even when consensus is successfully reached. The Block-in-Blobs proposal aims to address this vulnerability.<\/p>\n<p>The update will also affect the fee system. Currently, Ethereum separates gas for operations execution and gas for blob usage. In the new model, they may be combined into a single &#8220;data gas.&#8221; Developers believe this will equalize costs for various forms of data availability and prevent limit overlaps.<\/p>\n<h2 class=\"wp-block-heading\">ERC-8211 by Biconomy<\/h2>\n<p>Parallel efforts are underway to improve the structure of transactions themselves. The Biconomy project, in collaboration with the Ethereum Foundation&#8217;s <span data-descr=\"user experience\" class=\"old_tooltip\">UX<\/span> division, proposed the ERC-8211 standard, which turns transactions into programmable workflows.<\/p>\n<p>Instead of fixing parameters at the time of signing, ERC-8211 allows operations to obtain on-chain data in real-time, check specified conditions, and sequentially execute multiple steps with a single signature.<\/p>\n<p>The main goal is to reduce the number of failed transactions and enable more complex agent interactions in DeFi protocols.<\/p>\n<p>Both initiatives are part of extensive research within the Ethereum ecosystem. Developers have already <a href=\"https:\/\/forklog.com\/en\/news\/ethereum-developers-plan-seven-hard-forks-by-2029\">outlined<\/a> paths for network updates through the end of the current decade.<\/p>\n<p>As reported, Gnosis and Zisk, with support from the Ethereum Foundation, <a href=\"https:\/\/forklog.com\/en\/news\/ethereum-developers-propose-economic-zone-to-address-l2-fragmentation\">developed<\/a> a framework to unify the fragmented ecosystem of <a href=\"https:\/\/forklog.com\/en\/news\/what-is-a-layer%e2%80%912-solution-in-blockchain\">second-layer networks<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ethereum researchers are considering a proposal to transfer transaction data into BLOB objects, published alongside blocks.<\/p>\n","protected":false},"author":1,"featured_media":96014,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"1","news_style_id":"1","cryptorium_level":"","_short_excerpt_text":"Ethereum researchers propose using BLOB objects for transaction data.","creation_source":"","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[3],"tags":[46,277],"class_list":["post-96013","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-and-analysis","tag-ethereum","tag-scaling"],"aioseo_notices":[],"amp_enabled":true,"views":"23","promo_type":"1","layout_type":"1","short_excerpt":"Ethereum researchers propose using BLOB objects for transaction data.","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/96013","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/comments?post=96013"}],"version-history":[{"count":1,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/96013\/revisions"}],"predecessor-version":[{"id":96015,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/96013\/revisions\/96015"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/96014"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=96013"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=96013"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=96013"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}