Executive Summary JUMPDEST is a way to make EVM feasible for bytecode-compilation (enabling faster JIT or AOT execution) and to avoid certain security risks, which systems like x86 face (code obfuscation, polymorphic code and partially return-oriented programming attacks). History The original EVM design from 2014 didn't have JUMPDEST. It was the minimal change introduced to make the EVMJIT project at least feasible. See the following Yellow Paper changes: Jump destinations defined. JUMPDESTs must be used.
4/29/2025Summary The EXTCODECOPY, EXTCODEHASH, and EXTCODESIZE opcodes are allowed within EOF containers. Their behavior is the same as when called from outside a container. Restrictions on creating EOF contracts from existing facilities remains, with EOFCREATE and TXCREATE opcodes providing contract creation services. The entire "Ban Gas Introspection" theme is removed. The CALL, STATICCALL, DELEGATECALL, and GAS opcodes are allowed within EOF containers. CALLCODE is not allowed as it is a deprecated instruction. ::: spoiler Summary of EOF opcode changes The list of opcodes not permitted in EOF contracts now consists of 9 instructions, down from 16. CODESIZE and CODECOPY instructions, as described in EIP-3540
4/28/2025This document describes EOF's impact on the most popular existing libraries. We prepared prototypes of changes required to compile their source code. We describe unresolved issues and propose possible solutions. "Required changes to the source code" does not contain unresolved issues but sometimes contains TODO comments added to the source code. ⓘ Note: The prototypes make use of local paths in configuration and depend on a local build of the experimental Solidity compiler branch enabling block deduplicator on EOF rebased on the parallel branch enabling the constant optimizer. The first section addresses issues found in specific projects, and is followed by a categorical list of the kinds of changes authors will need to make. This document is based on the EOF scope approved in March of 2025. However, based on the findings of this report and the community feedback aroud these changes, Team Ipsilon recommends changes to the spec to reflect "Option D - Introspecting EOF". The adoption of this option will remove most of the required code changes listed in this report. Uniswap V4 (core) Required changes to the source code:
4/28/2025Danno Ferrin, 25 April 2025 Architectural transitions are a familiar chapter in computing history, from the CPUs powering general-purpose computers to the tightly controlled ecosystems of video game consoles and mobile devices. For Ethereum, a hypothetical shift to RISC-V presents a similar challenge: how to evolve without fracturing its vibrant ecosystem. Two contrasting models define the extremes of this transition: the abrupt generational leap of video game consoles and the seamless, compatibility-focused approach of Apple’s Macintosh transitions. By leveraging the Ethereum Object Format (EOF), Ethereum can chart a sustainable path toward RISC-V execution, emulating Apple’s strategy to ensure continuity for Mainnnet, Layer 2s, and other Ethereum-equivalent chains, maximizing compatibility as well as performance. Lessons Learned From Other Transitions But how do we get to RISC-V bliss? Lets see how two other systems handled such transitions: Video Game Consoles and Macs. The Video Game Console Model: A Hard Break Video game consoles, like the PlayStation or Xbox, epitomize the direct-replacement approach. Each generation marks a sharp divide: games written for one system often won’t run on its successor, even if they share a brand. Backward compatibility when offered is typically limited, relying on emulation for a subset of titles, or requiring an upgrade fee to use the features of the new system. This model prioritizes a clean slate, forcing developers to rewrite software and users to invest in new hardware and games. For Ethereum, adopting this approach would be disastrous, creating high-friction “cleavage planes” where users and developers might abandon the ecosystem, as the cost of staying outweighs switching to competing platforms.
4/27/2025