Vitalik Buterin cites Bitcoin’s Utreexo in Ethereum scaling discussion

Ethereum co-founder Vitalik Buterin credited Bitcoin developers on Aug. 16 for work on Utreexo while outlining a proposed Ethereum scaling direction that could combine UTXO-style state, conventional dynamic state and models between the two.

In an X post, Buterin described it as the “current proposed Ethereum scaling strategy,” making clear that the architecture is still under development.

Buterin said the objective is to let most Ethereum activity scale much further without sacrificing decentralization, censorship resistance or the ability to run nodes easily. His remarks do not indicate that Ethereum has chosen to replace its account model with Bitcoin’s UTXO architecture. The designs he referenced remain research proposals, not approved protocol changes.

Bitcoiners deserve a lot of credit for pioneering many of these ideas (see Utreexo). But yes, this is what the current proposed Ethereum scaling strategy looks like in action. We want Ethereum to have the best of UTXO-style state, dynamic state, and everything in between,… — vitalik.eth (@VitalikButerin) August 16, 2026

Bitcoiners deserve a lot of credit for pioneering many of these ideas (see Utreexo). But yes, this is what the current proposed Ethereum scaling strategy looks like in action. We want Ethereum to have the best of UTXO-style state, dynamic state, and everything in between,…

Bitcoin’s Utreexo offers a model for reducing node state

Utreexo was introduced in 2019 by MIT Digital Currency Initiative researcher Thaddeus Dryja. Rather than requiring a validating node to hold the full Bitcoin UTXO set locally, the design represents that set with a compact hash-based accumulator. Transaction inputs include inclusion proofs that let nodes verify relevant outputs against the accumulator.

MIT DCI’s original paper says the accumulator grows logarithmically with the underlying set. That addresses the same broad challenge Ethereum researchers are examining: increasing network activity without forcing state-storage requirements to grow at the same pace. In practice, that matters because node resource demands shape who can verify the chain independently, and Ethereum’s scaling work has repeatedly tried to preserve that property while expanding throughput. Utreexo remains a Bitcoin scaling project and is not a feature Ethereum is directly copying.

Ethereum’s native UTXO proposal focuses on payment state

A July 6 Ethereum Research proposal from Toni Wahrstätter, writing as Nero_eth, suggests adding native UTXO-like payments without removing Ethereum accounts. The model is aimed at one-shot payments that do not require persistent smart-contract state.

The proposal estimates that these workloads could reduce permanent state usage by roughly 99.8%. Instead of storing the full payment object in active state, Ethereum would prove its existence from history while mainly retaining a compact spent-status bit. At one billion entries, the proposal estimates roughly 300 MB of permanent state, compared with about 100 GB to 150 GB for equivalent account or storage entries. Those figures are design estimates, not measured mainnet results.

The approach fits into Ethereum’s broader effort to reduce verification and storage burdens. As crypto.news previously reported, Ethereum’s Lean rebuild places recursive cryptographic proofs at the center of its proposed verification overhaul, showing that the scaling discussion is not limited to one layer of the stack.

Recursive STARKs address a different bottleneck

Buterin’s January recursive-STARK mempool research focuses on proof bandwidth. His model assumes highly optimized STARK proofs of about 128 kB and proposes that mempool nodes periodically combine validity proofs recursively rather than attaching a separate large proof to every object being propagated.

Using Buterin’s example of eight peers and 500-millisecond aggregation intervals, extra bandwidth would total about 2 MB per second per node and remain constant as more objects are added to the scheme. The mempool research and the native UTXO proposal address different constraints, although researchers are exploring whether the ideas could complement each other.

A community response extrapolated the combination into an architecture capable of settling an “unbounded volume” of UTXO transitions through a compact proof. That is not a confirmed Ethereum throughput target or roadmap commitment. Buterin’s research does not establish unlimited transaction capacity, and the 128 kB figure refers to an assumed STARK proof size in his mempool model, not a confirmed future Ethereum block format.

If we were to synthesize Vitalik’s STARK-aggregated mempool architecture with Toni’s UTXO-oriented execution proposal, we could theoretically construct a recursively STARK-aggregated UTXO transaction fabric at the memory/networking layer, whereby transaction-state transitions are… — Liberty Swap | C.R.O.P.S. on PulseChain 🗽 (@LibertySwapFi) August 16, 2026

If we were to synthesize Vitalik’s STARK-aggregated mempool architecture with Toni’s UTXO-oriented execution proposal, we could theoretically construct a recursively STARK-aggregated UTXO transaction fabric at the memory/networking layer, whereby transaction-state transitions are…

What comes next for Ethereum scaling

The native UTXO proposal assumes EIP-8141, or Frame Transactions, for its preferred spending design. EIP-8141 would introduce programmable transaction frames covering validation, gas payment and execution. The official Hegotá specification currently lists Frame Transactions only as “Considered for Inclusion.” FOCIL, or EIP-7805, remains the only proposal formally scheduled for Hegotá.

Ethereum’s official roadmap places Hegotá in 2027, after Glamsterdam in the fourth quarter of 2026. Native UTXOs are not currently listed as a scheduled Hegotá feature. As crypto.news reported, Hegotá’s 2027 upgrade scope is still being narrowed, with Frame Transactions among the major designs still under consideration.

Buterin’s reference to Utreexo therefore points to a research direction rather than a fixed Ethereum upgrade date. The work suggests a hybrid system in which different types of activity could use different state models, while cryptographic proofs reduce what individual nodes must store or repeatedly verify.