Devcon Archive logo
Devcon Devconnect Forum Blog
  • Watch
  • Event
    Event: background logo
    • Devcon 7
    • Devcon 6
    • Devcon 5
    • Devcon 4
    • Devcon 3
    • Devcon 2
    • Devcon 1
    • Devcon 0
    • Devconnect ARG
  • Categories
    Categories: background logo
    • Cryptoeconomics
    • Devcon
    • Developer Experience
    • Coordination
    • Core Protocol
    • Layer 2s
    • Real World Ethereum
    • Cypherpunk & Privacy
    • Security
    • Applied Cryptography
    • Usability
  • Playlists

Suggested

Loading results..

View all

About Devcon —

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.

An intensive introduction for new Ethereum explorers, a global family reunion for those already a part of our ecosystem, and a source of energy and creativity for all.

  • Watch
  • Devcon
  • Devconnect
  • Forum
  • Blog

Get in touch

devcon@ethereum.org

Subscribe to our newsletter

Crafted with passion ❤️ at the Ethereum Foundation

© 2026 — Ethereum Foundation. All Rights Reserved.

devcon8 / eip 7923 a sparse page based memory model for the evm

  • YouTube
EIP-7923: A Sparse-Page-Based Memory Model for the EVM preview
  • Details

EIP-7923: A Sparse-Page-Based Memory Model for the EVM

Duration: NaN:NaN:NaN

Speaker: Qi Zhou

Type: Lightning Talk

Expertise: Deep prior knowledge

Event: Devcon

Date: Nov 2026

EIP-7923 enables 64MB of memory allocation per transaction through a sparse-page-based memory model with linearized gas costs. Today, the EVM’s quadratic memory pricing — designed to prevent DoS attacks — limits memory usage to about 3MB per transaction and lacks modern memory management features like stack and heap allocation, resulting in real inefficiencies for compute-heavy contracts. EIP-7923 replaces quadratic pricing with a linear model, unlocking up to 64MB of memory per transaction. We explain how this is achieved through a virtual memory system implemented using POSIX mmap, present gas-cost measurements from real-world hardware benchmarks, and justify the 64MB cap as a security-critical balance that prevents DoS risk, particularly in concurrent eth_call scenarios.

Categories

Core ProtocolRoadmapEVMSecurity