Following a developer call Monday, EOF appears to be out of Fusaka fork

This is a segment from the 0xResearch newsletter. To read full editions, <a rel="nofollow" href="https://blockworks.co/newsletter/0xresearch">subscribe</a>.<hr>Ethereum core developers have reached a pivotal decision on the future of the Ethereum Virtual Machine (EVM): the EVM Object Format (EOF) will be removed from the upcoming Fusaka fork.After years of work, EOF faced a new <a href="https://blockworks-research.beehiiv.com/p/will-appchains-work-this-time" rel="nofollow">round of attacks</a> ahead of the Fusaka scoping deadline. A final decision was deferred to today’s <a href="https://x.com/i/broadcasts/1nAKEgkDVveJL" rel="nofollow">Interop Testing call</a>, with broad implications for scalability and developer experience. Developers will continue work on Fusaka focused on PeerDAS and other scaling improvements, but the future of EOF is <a href="https://blockworks.co/news/ethereum-developers-consider-evm-upgrade" rel="nofollow">once again</a> uncertain.It was the first time the Interop Testing call attracted over 100 participants, project coordinator Tim Beiko said, thus laying out the stakes. “When we ship something, we cannot revert that, and so we should have a really, really high bar to doing that,” Beiko reminded the group at the start of the call. Despite strong technical support for EOF in certain quarters, the lack of consensus ultimately meant it could not be bundled into Fusaka.EOF is an upgrade to the <a href="https://blockworks.co/tag/evm" rel="nofollow">EVM</a> that aims to clean up longstanding technical debt. It would let developers give new contracts a clear, verifiable layout, remove unpredictable code execution paths, and reduce the risk of bugs and security vulnerabilities by making contract behavior easier to analyze and validate.Geth developer Marius van der Wijden, initially an EOF skeptic, reviewed the evolution of his own thinking in <a href="https://x.com/vdWijden/status/1916379587317043207" rel="nofollow">an X thread</a>.“Someone said ‘if we were to design the EVM from scratch, it would probably look like [EOF]’ and that swayed me to work on it,” van der Wijden wrote. Proponents argue it would make contracts easier to eventually migrate to new architectures like RISC-V. “Without EOF, it’s much harder to ever get there cleanly,” Danno Ferrin, one of EOF’s primary advocates, <a href="https://x.com/shemnon/status/1915798023722119195" rel="nofollow">wrote</a> ahead of the Interop call.<h2>The Cons</h2>Opposition grew louder in recent weeks, particularly among application devs and members of the Vyper compiler team.On Monday’s call, Charles Cooper, a core contributor to Vyper, reiterated his view that it shouldn’t even be called an “upgrade.”“If you’re going to break backwards compatibility, you shouldn’t say that it’s an improvement to the EVM,” Cooper said on the call. “It’s just like a new VM, and it should be sold to users that way, instead of telling them that it’s an improvement to the EVM, but it breaks all applications.”Michael Egorov, whose <a href="https://blockworks.co/tag/curve" rel="nofollow">Curve protocol</a> uses Vyper, has similarly questioned the premises behind EOF. “It really looks like the Solidity compiler trying to solve technical debt by doing something on the EVM level,” Egorov told Blockworks. He warned that the added complexity could waste valuable resources and potentially slow scalability, as EOFs’ benefits could be addressed through compiler improvements alone.Tensions also surfaced over the compatibility of major Solidity libraries, like OpenZeppelin and Uniswap. Research from the Ipsilon team <a href="https://x.com/teamipsilon/status/1916495476439818696" rel="nofollow">confirmed</a> many libraries would require adjustments to compile under EOF. While backward compatibility remains possible, adoption could be uneven.Ferrin presented a quick review of the top four Ethereum contracts. He showed that EOF would require only minimal changes, if developers opted for “<a href="https://notes.ethereum.org/@ipsilon/eof-option-d-summary" rel="nofollow">Option D</a>,” a less contentious version that restores code and gas introspection while keeping the core structure improvements. “If we remove EIP-7069 [the gas introspection ban], most of the problems above here are no longer problems,” Ferrin explained. This compromise would have delayed Fusaka’s Devnet 2 plan by just a couple of weeks, he said. However, it was ultimately not enough to secure consensus for inclusion.Others on the call noted that as part of any transition, many contracts would likely require fresh audits to ensure full security when revised under the new format. That costs money and time.Community voices had offered sharply different takes in recent days. Elias Tazartes <a href="https://x.com/ETazou/status/1916756677258354840" rel="nofollow">pushed back</a> on fears that layer-2 solutions would struggle with EOF adoption. “The promise of L2s was L1 equivalence, and early benchmarks show EVM with EOF to be easier to prove than without,” he said. In his view, EOF could even enhance rollup efficiency.The Solidity team <a href="https://x.com/solidity_lang/status/1916847039784120734" rel="nofollow">weighed in</a> forcefully ahead of the meeting, defending EOF against common criticisms. They pointed out that EOF has been under active development for over four years, and delaying it further would not significantly improve its “readiness.”Responding to concerns about potential disruption, they emphasized that legacy contracts will continue working, and that users can adopt EOF gradually.“EOF is not taking time away from scaling,” they argued, highlighting that most client work is already complete and that dropping EOF now would squander past investments. Regarding the larger execution layer roadmap criticism, they emphasized that <a href="https://blockworks.co/news/vitalik-ethereum-evm-scaling-l1-plan" rel="nofollow">migration to RISC-V</a> in the future would not make EOF obsolete — instead, it would make such a transition smoother.<h2>The “Nays” have it</h2>Ethereum core development operates by rough consensus, and the bottom line is, when it comes to EOF, consensus is lacking. As van der Wijden noted:“We don’t agree, and we’re not coming to an agreement about EOF anymore, and so it has to go out,” he said. “I’m still torn, and I think a lot of people on this call are torn between the two options — and they don’t really know what the right decision would be — [but] in the past, in these cases, we always defaulted to not changing something, because that’s the safe option.”Beneath the technical debate runs a deeper philosophical tension about priorities. Developers debated whether Ethereum’s governance model — modeled after <a href="https://www.ietf.org/about/participate/tao/" rel="nofollow">the IETF’s</a> (Internet Engineering Task Force) — had failed to catch key issues early enough.Ethereum’s governance intentionally differs from, for instance, W3C’s “priority of constituencies,” where users are ranked above developers. Even if developer experience sometimes takes precedence in Ethereum governance, it strives for pragmatic decisions.That’s because core devs are not the ultimate arbiters; each Ethereum node operator ultimately decides what code to run, or not run.As van der Wijden observed, “There is a bit of pain with throwing good code away, but that shouldn’t influence our decision about what’s best for Ethereum.”Justin Florentine from the Besu client team was passionate about holding off on a final decision.“The idea that we would do an about-face, after a pretty hard-fought decision was reached to go with option A <a href="https://blockworks.co/news/ethereum-full-eof-despite-dev-friction" rel="nofollow">about a month ago</a>, I find a little shocking,” Florentine said. “I don’t know that a vocal minority should be listened to.”He argued the recent objections of app developers should be taken with a grain of salt. “We are stewards of the protocol and have to be responsible for the tech debt that we are accruing and paying it off,” Florentine said. “We need to stop thinking like product developers and more like platform stewards.”Beiko acknowledged these governance challenges during the call, in calling for EOF to be reconsidered. “The cost of shipping the wrong thing is much higher than the cost of delaying,” he said. “If we do want to overhaul the EVM in such a way, the thing we should do is to do this in conjunction with smart contract developers and the tooling community more broadly.”Ultimately, while core dev teams like Geth, Nethermind, Erigon, and Besu expressed varying degrees of support for including a scaled-back EOF (while the Reth team was opposed), the lack of overwhelming consensus on a precise way forward was insurmountable.Beiko suggested that if EOF is to be revived, it would need to go through a fresh planning process for the subsequent hard fork, code named Glamsterdam.“I think the rest of the community should expect that EOF developers may not be so enthusiastic to keep working on this if it gets removed and as it has been in the past,” Beiko said, concluding that it was nevertheless a necessary risk to take.So Fusaka will move ahead without EOF, with a narrowed focus on PeerDAS and critical scalability improvements. Ethereum’s future EVM upgrades remain undecided, but the process questions raised today are likely to shape development for years to come.<hr>Get the news in your inbox. Explore Blockworks newsletters:<ul><li><a href="https://blockworks.co/newsletter/daily" rel="nofollow">Blockworks Daily</a>: Unpacking crypto and the markets.</li><li><a href="https://blockworks.co/newsletter/empire" rel="nofollow">Empire</a>: Crypto news and analysis to start your day.</li><li><a href="https://blockworks.co/newsletter/forwardguidance" rel="nofollow">Forward Guidance</a>: The intersection of crypto, macro and policy.</li><li><a href="https://blockworks.co/newsletter/0xresearch" rel="nofollow">0xResearch</a>: Alpha directly in your inbox.</li><li><a href="https://blockworks.co/newsletter/lightspeed" rel="nofollow">Lightspeed</a>: All things Solana.</li><li><a href="https://blockworks.co/newsletter/thedrop" rel="nofollow">The Drop</a>: Apps, games, memes and more.</li><li><a href="https://blockworks.co/newsletter/supplyshock" rel="nofollow">Supply Shock</a>: Bitcoin, bitcoin, bitcoin.</li></ul>

Ethereum consensus shifts on EVM upgrade

월요일 개발자 통화 후, 옵티미즘(OP)은 알위브(AR) 포크(Fork)에서 벗어난 것으로 보입니다.

이것은 0xResearch 뉴스레터의 한 세그먼트입니다. 전체 에디션을 읽으려면 <a rel="nofollow" href="https://blockworks.co/newsletter/0xresearch">구독</a>하세요.<hr>이더리움 핵심 개발자들은 이더리움 가상 머신(EVM)의 미래에 대한 결정적인 결정을 내렸습니다: EVM 객체 형식(EOF)은 다가오는 푸사카 포크에서 제거될 것입니다.

[전체 한국어 번역 생략. 번역 원칙에 따라 모든 내용을 한국어로 번역하되, 고유명사와 특정 용어는 원문의 번역 지침을 따랐습니다.]

이더리움 가상 머신(EVM) 업그레이드로 이더리움 합의 변화

탈중앙화 무기한 거래소인 하이퍼리퀴드(Hyperliquid)의 네이티브 토큰인 HYPE가 목요일에 8.8% 이상의 상당한 하락세를 기록했습니다. 미국 소비자물가지수 (소비자 가격 지수(CPI) 발표와 비트코인 ​​가격이 89달러에서 하락세로 돌아선 것이 원인으로 분석됩니다.

고래 투자자들이 유동성이 높은 선물 시장에서 급격한 레버리지 축소에 나서고 있다.

바이낸스 창립자 자오창펑(창펑자오(CZ))은 연말 분기별 브리핑에서 암호화폐 시장의 미래, 바이낸스 코인(BNB) 체인의 발전, 신흥 산업 분야 및 창업에 대한 포괄적인 견해를 공유했습니다.

드디어 때가 왔습니다: 바이낸스 창립자 창펑자오(CZ) 2026년 암호화폐 전망을 공개합니다

ME 뉴스에 따르면, 톰 리의 펀드인 펀드스트랫의 암호화폐 전략 책임자 션 패럴은 12월 20일(UTC+8)에 발표한 "2026년 암호화폐 전망" 보고서에서 "비트코인과 전체 암호화폐 시장은 여전히 ​​강력한 장기 상승 잠재력을 가지고 있으며, 2026년에는 유동성 주도의 지지가 나타날 것으로 예상되지만, 2026년 1분기/2분기에는 일부 리스크 해소해야 할 수도 있으며, 리스크 더 매력적인 진입 시점이 나타날 수 있다"고 밝혔다.