Ethereum co-founder Vitalik Buterin discussed the proposed EIP-8141 transaction format in a Sept. 5, 2026, post, explaining how it could support further network scaling. Buterin said the approach could help Ethereum increase capacity without sacrificing decentralization by allowing parts of transactions to be processed separately and in parallel.

Recent research into transaction formats — including EIP-8141, UTXOs, PBT, keyed nonces and a recursive STARK mempool — has produced a clearer distinction between transaction actions and dependencies, Buterin said. An action is the effect a transaction has on the network, such as an Ethereum transfer, while a dependency is a condition that must be satisfied for the transaction to remain valid.

Separating actions from dependencies

Buterin identified digital signatures, Merkle proofs for UTXOs, ZK-SNARK or STARK proofs, and network-state data needed to verify a transaction as examples of dependencies.

“Dependencies can be processed in parallel,” Buterin explained.

Dependencies connected to network state could be analyzed at the mempool level, particularly when a transaction declares in advance which state data it will access, according to Buterin. Dependencies that do not interact with state could potentially be verified once in the mempool and then replaced with a STARK proof.

Buterin said this approach could accelerate execution and, in some cases, eliminate the need to process or transmit some data after its correctness has been proved.

EIP-8141 proposes a transaction type that divides a transaction into a sequence of contract calls responsible for validation, gas payments and execution of the user’s operations.

Balancing flexibility and scalability

Buterin said Ethereum did not require such a detailed separation of transaction operations in 2015, when the network handled relatively few transactions and sequential execution was sufficient. Ethereum’s current scaling strategy, however, requires the network to move away from that model, he said.

“Ethereum is beloved by many developers because the execution and state model is so dynamic and flexible. But dynamic and flexible is not friendly to scaling,” Buterin wrote.

More than 90% of Ethereum activity by volume does not require that degree of dynamism, according to Buterin. He said the protocol should require contracts, accounts and transactions to define more clearly which operations are dynamic and which can be analyzed statically.

Lower gas fees could then apply to statically analyzable operations, providing an economic incentive to use transaction structures that are easier to scale, Buterin said.

He described the approach as combining characteristics of early Ethereum with a model closer to Bitcoin, which he said has effectively used what he calls account abstraction from the outset. New state types, keyed nonces and a recursive STARK mempool should all contribute to reducing network load and improving scalability, according to Buterin.

EIP-8141 as a foundation for further changes

Buterin said a universal transaction format could provide a natural interface for future protocol generalizations and linked that role directly to EIP-8141.

“So in that sense, 8141 done well is not just a culmination of 10 years of account abstraction work, it’s also preparation for the next few years of responsible decentralization-friendly hyper-scaling,” he said.

EIP-8141 also supports alternative methods of paying fees without centralized intermediaries and would separate accounts from specific ECDSA keys. Buterin said that would lay the groundwork for replacing those keys and adopting new signature schemes.

According to Buterin, the proposal could help Ethereum move gradually from a universal but difficult-to-scale model toward an architecture that gives simpler, more statically analyzable operations priority in cost and scalability.

Source: Incrypted