Ethereum Debates

We track the issues on which Ethereum core developers and researchers publicly disagree on X (Twitter) and the forums. For each debate we lay out what is contested, who stands where and on what grounds, and how the exchange unfolded.

Debates

• In the Binance hack, is EIP-7702 responsible for making the damage worse, or is it just a neutral tool and the real problem is the key leak? — Protocol design · 7 participants · 2026-10-30
  decentrek, an account abstraction contributor, said EIP-7702 itself is not broken, but its batching feature did help the hacker drain 64 tokens including ETH and USDT in a single transaction and so made the damage worse. They urged improving operational practices and moving to endgame account abstraction such as EIP-8141 frame transactions. FigoETH, AzianMike, ETH_MAXER and others countered that 7702 is a safe, neutral UX tool and that the problem is the private key leak and Binance's sloppiness.
• Can Ethereum sustain core development through patronage and ETH asset marketing alone, with 'no dev tax' as its strength? — Governance & community · 3 participants · 2026-10-27
  lex_node argued that having no protocol-level developer tax (dev tax) is Ethereum's huge strength and that patronage and ETH asset marketing can sustain core development. Geth's lightclients countered that they have never seen Ethereum run without the remnants of a dev tax, so it cannot be asserted as a strength, and that a plan to sustain tens of millions of dollars a year in funding must come first. Protocol Guild's trent_vanepps added that existing compensation is already sufficient and that people should deliver results before asking for more funding, while also saying the transition should be planned in advance in case the EF shrinks.
• Should ETH be a store of value (SoV) asset, and should the 'forces' that do not want that be defeated? — Governance & community · 3 participants · 2026-10-27
  lex_node argued that there are influential people inside Ethereum who actively hope ETH does not become an investment asset, that this is a coherent view, but that the ETH investment thesis must defeat them to win. The EF's Tim Beiko countered that if one values Ethereum's impact on the world, that is not a coherent view, since without mainnet everything drifts away from Ethereum, and ETH is the most important thing mainnet guarantees.
• Can decentralization be a business model in itself, or is it only a mission? — Governance & community · 2 participants · 2026-10-27
  binji_x of Optimism and EthLabs wrote that the era when VCs threw money at anything named 'crypto' gave room to pursue decentralization without worrying about a sustainable business, and that not everything needs a business model. lex_node countered that decentralization is a great mission but cannot be a business model in itself, and that it is also doubtful whether crypto makes sense as a 'business'.
• Should we accept L1 gas repricing repeatedly breaking L2 stacks and immutable contracts? — Protocol design · 2 participants · 2026-10-26
  donnoh_eth of L2BEAT said the EIP-8037 repricing breaks most OP Stack chains again, expressing frustration that L1 keeps breaking the stacks above it. The EF's nero_eth answered that this is not about accepting breakage but a trade-off, where the sweet spot lies between the flexibility to reprice for future demand and the certainty that the foundation will not change.
• Does state gas repricing (EIP-8037, EIP-8038) solve the state growth problem? — Protocol design · 7 participants · 2026-10-25
  Geth's lightclients posted a public retro arguing that EIP-8037 and EIP-8038 only make it possible to raise the gas limit and do not solve the underlying problem of ever-growing state, and that breaking deployed contracts should be a last resort. Dankrad of the EF countered that pricing state more accurately is itself an improvement. Developers calling for state expiry and a process overhaul sided with lightclients.
• Is the minimal CREATE2 factory EIP-7997 worth including in a fork? — Protocol design · 8 participants · 2026-10-21
  pcaversaccio criticized EIP-8037 and EIP-8038 for repricing all three elements of onchain privacy without analyzing the impact. fradamt of the EF, a co-author of EIP-8037, countered that the repricing is only a neutral correction based on resources. nero_eth found from measurements that gas usage rises, but that the larger gas supply could actually lower absolute costs.
• Was rejecting EIP-8025 (opt-in execution proofs) correct? — Protocol design · 6 participants · 2026-10-16
  The day after ACDC #189 rejected including EIP-8025 (opt-in execution proofs) in Hegotá, a second round of debate broke out over which governance track it should take. donnoh_eth and ivanlitteri criticized the decision as a mistake that discarded ready-made work with no consensus change and therefore no risk, while lightclients countered that early adoption bypasses deliberation and erodes the barrier to inclusion, and that 8025 fits an informational EIP rather than a core EIP to be scheduled into a hard fork.
• Is Balaji's Farcaster acquisition the next chapter of decentralized social, or a corruption of it? — Governance & community · 8 participants · 2026-10-16
  After Jason Chaskin of the EF welcomed Balaji Srinivasan's acquisition of Farcaster as the next chapter of decentralized social, arguing that 'it is a centralized app, but it sits on a decentralized protocol, so the key is whether you can keep your following and build apps with different rules,' donnoh and many users pushed back, saying 'the next chapter is techno fascism' and that banning people from day one of launch is far from decentralized.
• Is Zcash Ethereum's biggest competitor, and should privacy come first? — Protocol design · 12 participants · 2026-10-09
  lex_node publicly urged Justin Drake to focus on what matters, saying his recent public contributions were an issuance-reduction sideshow and the 'crypto-destroying FUD' that Vitalik had to correct. binji_x, LaLiLuLeL0x and others defended him, saying there is no bold research without the freedom to be publicly wrong, while ryanberckmans moved between criticism and defense and settled on a compromise: 'we are lucky to have him, but be aware of the caliber of your gun'.
• Does Ethereum need a dedicated business development (BD) organization to avoid falling behind? — Governance & community · 9 participants · 2026-10-04
  After dankrad, a former EF researcher now at Tempo, claimed that 'nobody is doing business development (BD) for Ethereum, so Ethereum is falling behind', jfab agreed that the absence of BD is a real problem in the competition for off-chain assets, while many others, including Omid Malekan and kenny, countered that BD is not the key to success and that decentralization is Ethereum's strength.
• Do layered scaling and tokenization remove intermediaries, or add them? — Scaling & L2 · 3 participants · 2026-09-29
  After Julian Ma of EF RIG summarized that proper tokenization and layered scaling remove intermediaries and add customizability, donnoh of L2BEAT countered in a single line that 'layers add intermediaries', and the two split over a core premise of the L2 scaling narrative.
• Is potuz's mini payload design an alternative to quick slots, or only a complement? — Protocol design · 4 participants · 2026-09-20
  potuz put forward a design that reveals several payloads sequentially within one slot to reduce inclusion latency, as an alternative to quick slots, and Barnabé Monnot countered that this is a weak preconf and cannot replace the confirmation guarantee quick slots provide, so it is a complement, not an alternative. terence Tsao summarized that the benefits are clear but that loss of fast finality and implementation complexity are the tradeoffs.
• Is privacy dead on Ethereum? — Protocol design · 9 participants · 2026-09-20
  When gakonst said that his main concern is how dead privacy will be going forward, pcaversaccio pushed back that privacy is not dead and that we have only been building the wrong defaults, and that unconditional privacy enshrined in L1 should be deployed. The discussion split between those who say privacy is a lost cause in the age of AI and those who say it is an endless arms race that neither side wins.
• Can formal verification guarantee software security in the age of AI? — Protocol design · 2 participants · 2026-09-18
  Vitalik Buterin argued against the common view that AI hacking will destroy cybersecurity. If AI can prove Navier-Stokes or Fermat's Last Theorem, he said, it can also prove "this program is secure" as a mathematical theorem, so cybersecurity is fundamentally defense-favored. Sam Williams (samecwilliams) of Arweave and AO agreed with the direction but added a caveat: verified models alone are not enough, and the translation gap between the model and the actual code has to be closed with property-based testing.
• Native account abstraction: leave validation open to account code (EIP-8141) or bind it to a protocol-defined set of authenticators (EIP-8130) — Protocol design · 22 participants · 2026-09-15
  Gabriel Shapiro (lex_node) provocatively said that L2s are great for the crypto industry and for those who own sequencers, but for the Ethereum protocol itself they are merely less bad than competing L1s, and that L2s that are not Stage 2 are not true users. Pedro Gomes (pedrouid) fired back that the premise that improving user experience is bad for Ethereum makes no sense, and that Ethereum would not have survived without rollups.
• Is the funding shortage of Ethereum client teams a real constraint on the scope of Hegotá? — Governance & community · 4 participants · 2026-09-11
  Trent Van Epps of Protocol Guild warned that the funding shortage of execution layer (EL) and consensus layer (CL) client teams has deepened since June and that the client landscape could change significantly by year end. Christine D. Kim countered that funding follows the value of Ethereum, so it is a problem for the market to sort out.
• Should Ethereum issuance be reduced by burning validator rewards as staking grows — Protocol design · 36 participants · 2026-09-03
  The authors of EIP-8363 Tapered Issuance Burn (the proposer's tweet on the day of publication listed it as EIP-8361) proposed burning validators' consensus rewards as the staking ratio approaches 50% of the ETH supply, to remove the incentive for stake to grow beyond that. Co-author pintail said the argument that excess issuance leads to capture is not a rhetorical trick, and dapplion said that the operators who object are refusing only because they stand to lose, while this EIP benefits all holders in the long run. On the opposing side, rotki's Lefteris Karapetsas said issuance is not a problem Ethereum should be dealing with now, Aave's Stani Kulechov said Ethereum is still an unfinished product for supporting the financial system, so the protocol-level priority is privacy, and Marc Zeller of Aave Chan Initiative said the current risk-free yield gives wETH its appeal as collateral and there is nothing to replace it. ether.fi's Mike Silagadze said this change, disclosed with only 48 hours for feedback, would push out solo stakers and kill a large chunk of DeFi, and placed a public $1 million bet that the network would become more concentrated. DCinvestor said that, in a situation where staking yield has become a core reason to buy and keep holding ETH, consistency and predictability of policy matter more, and that changing issuance is itself value destroying. Micah Zoltu largely agreed with the authors' argument but opposed the change on the ground that the monetary policy of a live chain should not be changed, and Fundstrat and Lido took neither side, speaking instead about the uncertainty of the optimization curve and preparing for a low issuance regime.