{
  "id": 7692,
  "title": "EIP-7692: EVM Object Format (EOFv1) Meta",
  "status": "Stagnant",
  "type": "Meta",
  "category": "Unknown",
  "summary": "This introduces a new container format for EVM bytecode that enables code versioning, removes complex jump analysis, and paves the way for new execution environments like RISC-V and EVM64 within the same contract. This EIP was Declined for Inclusion from Fusaka on [April 28th](https://blog.ethereum.org/2025/04/29/checkpoint-2#eof) due to a lack of consensus on implementation details and the resulting potential slowdown of shipping PeerDAS. It has been re-proposed as a headlining feature in Glamsterdam with multiple variants to address community concerns.",
  "impacts": [
    "Indirect benefits from improved contract performance and reduced gas costs for computationally intensive operations. Better reliability from enhanced code validation.",
    "Can use multiple execution environments within same contract - write normal logic in EVM and intensive computations in EVM64/RISC-V. Better code analysis tools and function support improve development experience.",
    "Minimal direct impact on wallet development, though improved contract reliability and performance benefit user experience indirectly.",
    "Major updates needed for debuggers, analyzers, and development tools to support EOF containers, multiple execution environments, and new bytecode format. Better analysis capabilities once implemented.",
    "Can leverage more efficient execution environments for proof generation and validation. Better code analysis aids in rollup optimization and security verification.",
    "Reduced computational overhead from eliminating JUMPDEST analysis. Potential increased complexity from supporting multiple execution environments within contracts.",
    "Minimal direct impact on consensus layer operations as this primarily affects execution layer bytecode processing and validation.",
    "Major implementation work for new bytecode container format, multiple execution environments, enhanced validation, and maintaining backwards compatibility with legacy bytecode.",
    "Enables incremental adoption of RISC-V and EVM64 within existing contracts",
    "Removes complex JUMPDEST analysis improving execution efficiency",
    "Provides code versioning for backward-incompatible protocol changes",
    "Enables better code analysis and development tooling",
    "Introduces first-class function support improving analysis opportunities",
    "Addresses multiple EVM pain points through container format",
    "Paves the way for maintaining existing toolchain while adding new capabilities",
    "Enables 'both EVM and RISC-V' rather than 'either EVM or RISC-V' approach"
  ],
  "discussion_url": "https://ethereum-magicians.org/t/eip-7692-evm-object-format-eof-meta/19686",
  "source_markdown_url": "https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7692.md",
  "canonical_url": "/latest/eips/7692.json",
  "markdown_url": "/latest/eips/7692.md",
  "citations": [
    {
      "recordId": "eip-7692",
      "artifactPath": "normalized/7692.json",
      "url": "/records/proposal/eip-7692/normalized/7692.json",
      "label": "EIP-7692: EVM Object Format (EOFv1) Meta",
      "snippet": "This introduces a new container format for EVM bytecode that enables code versioning, removes complex jump analysis, and paves the way for new execution environments like RISC-V and EVM64 within the same contract. This E"
    }
  ]
}