BuildBear Logo Full

EOF Explained: What Developers Need to Know

In the upcoming Pectra upgrade, Ethereum introduces EVM Object Format (EOF) to enhance user and developer experiences.

Written by BuildBear Team on Oct 22, 2024

Introduction

Ethereum has undergone numerous upgrades recently, with the Ethereum Virtual Machine remaining fundamental to its architecture. In the upcoming Pectra upgrade, the core Ethereum team has announced the inclusion of EVM Object Format (EOF), enhancing user experience, developer experience, and performance across both Layer 1 and Layer 2.

In this article, we will learn:

  1. What is EVM Object Format (EOF)?
  2. Why do we need EOF?
  3. EIPs and EOF implementations.
  4. How EOF improves developer and user experience.

What is EVM Object Format (EOF)?

Ethereum uses the EVM to execute smart contracts. Currently, EVM bytecode deployed on-chain has no predefined structure, meaning data and code share the same instructions. For example, constants like fees in Uniswap contracts are embedded within executable bytecode, causing runtime overhead and slower, more expensive transactions.

EVM Illustration Image Source: Ethereum EVM illustrated

Current EVM challenges include:

  • Runtime overhead
  • Limited flexibility and upgradability
  • Restricted static analysis and formal verification

What is EOF and Why do we need it?

EVM Object Format (EOF) is a structured Ethereum bytecode format separating executable code from data, significantly reducing overhead and enhancing efficiency.

EOF introduces structured bytecode that allows Ethereum clients like Geth or Besu to perform one-time validation at deployment rather than every execution. Specifically, it eliminates repetitive JUMPDEST analysis, reducing transaction times and costs.

EOF Version 1 (EIP-3540)

EIP-3540 introduces EOF Version 1, featuring a structured container:

container := header, body
header :=
    magic, version,
    kind_type, type_size,
    kind_code, num_code_sections, code_size+,
    [kind_container, num_container_sections, container_size+,]
    kind_data, data_size,
    terminator
body := types_section, code_section+, container_section*, data_section
types_section := (inputs, outputs, max_stack_height)+

Key Features of EOF v1:

  • Structured Bytecode: Clearly defined sections (headers, code, data).
  • Versioning: Ensures compatibility with future upgrades.
  • One-time Validation: Validation during deployment only.

EOF implementation in the Pectra upgrade includes several EIPs under EIP-7692:

Major EOF Client Support:

Benefits for dApps

EOF provides measurable benefits:

  • Enhanced Security: One-time validation.
  • Faster Transactions: Lower runtime overhead.
  • Improved Efficiency: Reduced gas consumption.
  • Future-Proofing: Version control.

Measurable EOF Benefits (UniswapV3 Example)

MetricLegacyEOFDelta
Init Code Size31,202 bytes29,236 bytes~6.5% smaller
Deployed Code Size7,058 bytes6,388 bytes~10% smaller
Deploy Gas Usage6,832,734 gas5,925,377 gas~14% less gas
Call Gas Usage8,815,561 gas8,094,095 gas~9% less gas
Execution Time (100 calls)18,539 µs13,870 µs~15% faster

Full test details here.

NOTE: Solidity will soon fully support EOF, and frameworks like Hardhat and Foundry are expected to follow.

Conclusion

EOF is a significant EVM improvement, promising increased security, efficiency, and compatibility in Ethereum's evolving ecosystem.

About BuildBear

BuildBear provides developers a platform to create customized Private Testnets across multiple blockchain networks. It offers unlimited minting of Native and ERC20 tokens and rapid transactions (under 3 seconds), greatly enhancing DApp development and testing.

Connect with us: Twitter | LinkedIn | Telegram | GitHub