Infrastructure & Scaling
Share
Vitalik Buterin has proposed a redesign of Ethereum's transaction-processing architecture that separates validation dependencies from state-changing actions, enabling parallel processing and potentially improving scalability without restricting execution flexibility.
Ethereum co-founder Vitalik Buterin has outlined a potential redesign of the network’s transaction-processing architecture that could allow certain validation tasks to run in parallel, potentially improving scalability without sacrificing the flexibility of Ethereum’s execution environment.
The idea centers on separating “actions,” the operations that ultimately change Ethereum’s state, from “dependencies,” the information and conditions that must be checked before those operations can safely execute.
The distinction could allow Ethereum clients to handle predictable validation tasks more efficiently instead of processing every part of a transaction through a single sequential path.
Under Buterin’s proposed model, actions would include operations such as transferring Ether or calling a smart contract. Dependencies, meanwhile, could include digital signatures, Merkle proofs, zero-knowledge proofs and state conditions that must be satisfied when a transaction is included in a block.
The key observation is that not every validation step depends on the final state changes produced by a transaction.
A transaction signature, for example, can be checked independently of validation work associated with another transaction. Where the required dependencies are known in advance, clients could distribute those checks across available processing resources and perform them simultaneously.
That could reduce the computational time and resources required to process transactions, particularly when large portions of the workload can be handled independently.
But the approach becomes more complicated when validation depends on Ethereum’s changing state.
An account balance, for instance, cannot be validated without knowing the relevant state at the appropriate point in the transaction process. Storage access can create similar dependencies.
One possible solution lies in the mempool, the pool of pending transactions waiting to be included in blocks.
If transactions could declare in advance which parts of Ethereum’s state they are expected to access, mempools could use that information to organize and optimize validation before execution takes place.
That creates an interesting possibility for Ethereum’s fee market.
Transactions with clearly defined and predictable dependencies could potentially receive more favorable gas treatment because clients would be able to validate them more efficiently.
More dynamic transactions would not necessarily disappear. Operations requiring unpredictable calls or access to state that cannot be determined ahead of time could remain possible, but potentially at a higher computational cost.
Buterin has estimated that more than 90% of Ethereum activity by volume does not require the network’s full degree of dynamic execution flexibility. He has stressed, however, that this is his own estimate rather than an official measurement of Ethereum activity.
If that assumption holds, Ethereum could theoretically reserve its most flexible execution model for the transactions that actually need it, while processing more predictable workloads through a more efficient path.
The proposal also intersects with Ethereum Improvement Proposal EIP-8141, which introduces a new transaction structure known as “frame transactions.”
Rather than treating a transaction as a single indivisible sequence, the proposal divides it into frames that can separately handle functions such as validation, gas payment and user operations.
Under the proposed design, transaction authorization and fee payment would not necessarily depend solely on the standard signature attached to an externally owned account transaction. Account code could instead define the authorization and payment rules required for a transaction.
The model could support features including paying transaction fees with assets other than Ether, rotating account keys and bundling multiple operations together.
Those capabilities are closely related to the broader push toward account abstraction, which aims to give Ethereum accounts greater flexibility in how transactions are authorized and paid for.
The connection with Buterin’s latest proposal is the separation between what must be checked and what actually changes the network’s state.
Validation frames could handle the conditions required for a transaction to be accepted, while execution frames would carry out the operations that modify Ethereum’s state.
The architecture could also have implications beyond Ethereum itself.
Networks compatible with the Ethereum Virtual Machine could potentially adopt a shared transaction structure while retaining their own validation mechanisms and account-specific features.
That could make it easier for different EVM-based networks to work with a common transaction architecture without requiring every chain to implement exactly the same underlying rules.
But EIP-8141 remains a proposal, not an adopted Ethereum upgrade.
Developers are still considering issues around network security, transaction replacement rules, wallet infrastructure, mempool behavior and the potential effects of the design on block builders.
Those questions will need to be resolved before the proposal can move from an architectural concept toward deployment.
Several steps would be required before a design of this kind could reach Ethereum’s mainnet.
Client implementations would need to be developed and tested, wallets would need to support the new transaction structure, security reviews would have to be completed, and developers would need to examine how the model interacts with smart contracts, fee markets, mempools and block builders.
The proposal has also been discussed alongside FOCIL, another Ethereum proposal focused on censorship resistance and transaction inclusion.
The two address different problems.
Frame transactions are primarily concerned with transaction authorization, fee payment and execution, while FOCIL is designed to strengthen the inclusion of eligible transactions in blocks.
The two mechanisms could potentially work together, but that combination remains part of the research and development process rather than an established commitment in Ethereum’s roadmap.
Buterin’s September 6 comments should therefore be viewed as a possible direction for Ethereum’s transaction architecture, rather than an announcement of a completed upgrade.
They do not establish a launch date, confirm that the proposed system will be deployed, or signal an immediate change to Ethereum’s mainnet gas fees.
The decisive steps will be developer consensus, formal inclusion in a specific network upgrade, implementation across Ethereum clients and extensive testing before any final deployment decision.
The broader significance of the proposal lies in what it attempts to preserve.
Ethereum’s flexibility has been one of its defining strengths, allowing developers to build increasingly complex applications and smart-contract systems. But that flexibility also makes transaction processing more difficult to optimize because the network cannot always predict what a transaction will access or do.
Buterin’s approach is effectively an attempt to make that flexibility more selective.
If predictable validation tasks can be separated from genuinely dynamic operations and processed in parallel, Ethereum could potentially use its computing resources more efficiently without imposing sweeping restrictions on complex applications.
The challenge will be finding the right balance between parallel processing, gas costs, security, developer flexibility and user experience.
And that balance, rather than the transaction format alone, could determine whether the idea ultimately remains a research proposal or becomes part of Ethereum’s next phase of scaling.
Disclaimer of Warranty
The information provided in this article is for general informational purposes only. We make no warranties about the completeness, reliability, and accuracy of this information. Read full disclaimer
Editor's Picks

Why Zondacrypto’s Collapse Would Unfold Differently in the UAE
Walid Abou Zaki
Aug 28, 2026
8 min

The Missing Orchestration Layer Holding Back Institutional Digital Assets
Julian Sawyer
Aug 18, 2026
5 min

Beyond Crypto Access: How ARP Digital Is Building the UAE’s Digital Capital Infrastructure
Anna K.
Aug 17, 2026
8 min
Read More Articles
In the Same Space

UAE's Zand Expands Stablecoin Reach Across Global Markets With New USDC Integration
News Desk
Aug 25, 2026
5 min

UAE Formalizes Digital Currency Valuation Framework for VAT Reporting
Anna K.
Sep 7, 2026
7 min

$320M Exploit Drains Bitcoin From Network Used by Exchanges
News Desk
Sep 7, 2026
4 min

Crypto Companies Push SEC for Faster ETF Approvals and Confidential Drafts
News Desk
Sep 4, 2026
5 min



