Ethereum co-founder Vitalik Buterin on Aug. 16 gave a shout-out to Bitcoin developers for work on Utreexo while outlining a research-driven path for Ethereum scaling that blends UTXO-style state, today’s account model, and hybrid approaches. Buterin framed the ideas as “the current proposed Ethereum scaling strategy,” stressing they remain under active development and are not protocol decisions. The aim: let most Ethereum activity scale far beyond today’s limits without undermining decentralization, censorship resistance or the ability for ordinary users to run nodes. What is Utreexo — and why it matters here - Utreexo, introduced in 2019 by MIT DCI researcher Thaddeus Dryja, replaces a node’s need to hold the entire UTXO set with a compact hash-based accumulator. Transaction inputs carry inclusion proofs that let nodes validate outputs against the accumulator, which grows only logarithmically with the number of entries. - That same property — massively reducing per-node storage as activity grows — is precisely what Ethereum researchers are trying to capture, even if Utreexo itself remains a Bitcoin-focused project rather than a literal blueprint for Ethereum. A native UTXO proposal for Ethereum - On July 6, Ethereum researcher Toni Wahrstätter (Nero_eth) proposed adding native UTXO-like payments to Ethereum without removing accounts. The focus is “one-shot” payments that don’t require persistent smart-contract state. - Estimated impact: these payment workloads could cut permanent state usage by roughly 99.8% in the model — primarily keeping a compact spent-status bit and proving payment existence from history rather than storing full objects in active state. - Design estimate example: at one billion entries, permanent state could be ≈300 MB vs. 100–150 GB for equivalent account/storage entries. These are theoretical estimates, not mainnet measurements. How recursive proofs and mempool aggregation fit in - Ethereum’s broader Lean/verification work centers on recursive cryptographic proofs. Buterin’s January mempool research explores recursive STARK aggregation to reduce proof bandwidth: instead of attaching a large proof to each object, mempool nodes periodically combine proofs. - His example assumes optimized STARK proofs of about 128 kB and a design where eight peers aggregate every 500 ms — adding roughly 2 MB/s of constant extra bandwidth per node regardless of object volume. - The mempool aggregation and native UTXO proposals tackle different bottlenecks (proof bandwidth vs. state bloat), but researchers are investigating how they could complement one another. Community threads have extrapolated the combination into architectures that could settle huge volumes of UTXO transitions via compact, recursive proofs — though that extrapolation is speculative and not a confirmed throughput target. Protocol timeline and caveats - The native UTXO proposal prefers EIP-8141 (Frame Transactions) as a spending design to handle validation, gas payment and execution. Frame Transactions are currently listed as “Considered for Inclusion” in the Hegotá specification. EIP-7805 (FOCIL) is the only proposal formally scheduled for Hegotá as of now. - Ethereum’s road map puts Hegotá in 2027 after the Glamsterdam upgrade (Q4 2026). Native UTXOs are not currently a scheduled Hegotá feature; the upgrade’s scope is still being narrowed and Frame Transactions remain under consideration. - Important: these are research proposals and design sketches, not approved protocol changes. The assumed STARK sizes, recursive schemes and state-savings figures are working assumptions, not guarantees of future block formats or unlimited transaction capacity. Bottom line Buterin’s citation of Utreexo signals a clear research direction: a hybrid Ethereum that gives different workloads the most appropriate state model, while leveraging cryptographic proofs to dramatically shrink what nodes must store and repeatedly verify. It’s an intriguing roadmap for scaling without centralizing, but it remains exploratory — promising on paper, pending engineering, formal specification and mainnet validation. Read more AI-generated news on: undefined/news