Hoskinson Calls UTXO Adoption Talk 'Literally a Crime' as Ethereum Eyes Cardano's Playbook 🃏

Cardano founder Charles Hoskinson accused former colleagues at the Ethereum Foundation of hypocrisy after an Ethereum researcher proposed borrowing elements of Cardano's account-handling architecture to curb runaway database growth. The proposal, EIP-8141, titled "Frame Transactions," was authored by researcher Toni Wahrstätter and has advanced to the Strawman discussion track, which Ethereum co-founder Vitalik Buterin is following.

Under Ethereum's current account-based model, the network must permanently store active balance data for every wallet, even after a single one-time transfer. Wahrstätter's design would mark simple payments as "one-time use," with information verified from blockchain history while leaving only a single spent bit in active memory. The author estimates this would cut unnecessary data growth by 99.8% for basic L1 transfers.

Hoskinson, who left Ethereum in 2014 after a public split with Buterin over the network's commercial direction, took to X on July 7, 2026, to denounce what he described as an ecosystem-wide taboo against crediting his work. Cardano, the third-largest cryptocurrency by market capitalization, was built from inception on a modified Extended UTXO (eUTXO) model designed to address scaling constraints that still challenge Ethereum. "It's not like I've been literally working on this topic for over 10 years of my life and launched a cryptocurrency that was number three on coinmarketcap with millions of users to deploy it," Hoskinson wrote. "It's literally a crime in the Ethereum inner circles to mention Cardano. EUTXO is the…"

The UTXO framework itself originated with Bitcoin, whose network has no smart-contract functionality. Cardano adapted the model into eUTXO to support complex decentralized applications. Ethereum, by contrast, has operated on an account-oriented system since launch. Implementing hybrid UTXO elements now would carry compatibility risks for already-deployed DeFi protocols, leaving the foundation to weigh continued database expansion against a partial architectural reversal that implicitly validates its competitor's design choices.