proposal<\/a>, Ethereum can \u201cenhance its resilience against certain DoS vectors, improve network stability, and provide more predictability to transaction processing costs\u201d by implementing a protocol-level cap on individual transactions.<\/p>\nUnder the current structure, a single Ethereum transaction can theoretically consume the entire block\u2019s gas limit, exposing the network to denial-of-service attacks and potential instability. EIP-7983 addresses the issue by introducing a cap of 16.77 million gas units per transaction, each unit representing a measure of computational work on the Ethereum network.<\/p>\n
This would prevent any single transaction from monopolising block space and ensure a more even distribution of gas consumption across transactions. Transactions that specify a gas limit exceeding 16.77 million would be rejected during block validation, making them ineligible for inclusion in new blocks.<\/p>\n
The proposal does not change the total block gas limit, which remains adjustable by miners and validators under the existing consensus framework. Instead, it introduces a protocol-level restriction designed to limit the gas usage of individual transactions, thereby improving predictability and safety.<\/p>\n
<\/p>\n
Buterin and Wahrst\u00e4tter argue that the 16.77 million cap strikes a balance between accommodating complex use cases, such as DeFi interactions and contract deployments, while reducing operational and security risks.\u00a0<\/p>\n
Most current transactions reportedly fall well below this threshold, meaning the proposal is unlikely to disrupt typical user or developer activity.<\/p>\n
The cap also supports better compatibility with zero-knowledge virtual machines (zkVMs), which benefit from transactions being broken into smaller, more manageable components.\u00a0<\/p>\n
By enforcing per-transaction gas constraints, EIP-7983 encourages the decomposition of large transactions into smaller, modular units. This approach aligns well with the operational requirements of zk-based execution environments and can potentially enable more efficient proof generation and integration at the protocol level.<\/p>\n
EIP-7983 builds on earlier work, including EIP-7825, which similarly sought to improve the predictability of transaction execution. Both proposals reflect a broader movement within the Ethereum ecosystem to address complexity and performance bottlenecks at the protocol level.<\/p>\n
The proposal comes as Ethereum faces mounting competition from faster and more efficient smart contract platforms.\u00a0<\/p>\n
For instance, in June, Solana outpaced Ethereum in terms of decentralized application revenue, generating over $146 million. Solana also retained a higher share of DEX volume, recording $5.78 billion compared to Ethereum\u2019s $4.7 billion.<\/p>\n
Amidst this backdrop, Buterin has called for simplifying Ethereum\u2019s core design to improve security, reduce costs, and make development easier. He argued that a leaner, more accessible Ethereum would lower infrastructure and maintenance costs and also improve decentralization and security.<\/p>\n
Separately, Buterin has proposed reducing node hardware requirements through partial statelessness. In a post published later in May, he introduced a concept where full nodes verify the entire chain but only store the state relevant to the user.<\/p>\n
<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
Ethereum may soon enforce a 16.77 million gas limit on single transactions under EIP-7983, proposed by Vitalik Buterin and researcher Toni Wahrst\u00e4tter to improve performance and reduce attack surfaces. According…<\/p>\n","protected":false},"author":1,"featured_media":5141,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5140","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cryptocurrency"],"_links":{"self":[{"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/posts\/5140","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/comments?post=5140"}],"version-history":[{"count":1,"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/posts\/5140\/revisions"}],"predecessor-version":[{"id":5142,"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/posts\/5140\/revisions\/5142"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/media\/5141"}],"wp:attachment":[{"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/media?parent=5140"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/categories?post=5140"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bitunikey.com\/news\/wp-json\/wp\/v2\/tags?post=5140"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}