Ethereum network, ecosystem and market developments.
Separate a proposal from an activated network change. For each development, check which network is affected, whether the change is live, and what the source actually establishes about its effects.
7 distinct developments · 8 Sept 2026 – 9 Sept 2026. Newest first.
EIP-8369's latest discussion evaluates VOPS profiles for FOCIL eligibility, focusing on how to classify frame transactions by their stability against block position changes. The refinement seeks practical, enforceable rules for inclusion guarantees under Ethereum's upcoming FOCIL framework.
A draft of EIP-8298 proposes a SETCODEFROM instruction for the Ethereum Virtual Machine, allowing contracts to adopt code from other live contracts to improve deployment efficiency and enable secure account migration, while maintaining deterministic code availability.
Developers have produced the first proof-of-concept merge proof for Ethereum’s proposed EIP-8304 trustless log and transaction index, demonstrating it is feasible to merge blocks in a verifiable, cost-effective manner using cryptographic proofs. Benchmarks and code compatibility were also confirmed.
The Ethereum Foundation’s Protocol cluster has identified EIP-7805 (FOCIL) and EIP-8141 (Frame Transactions) as essential inclusions for the upcoming Hegotá network upgrade, defining the fork’s scope around censorship resistance and flexible account authentication.
EIP-8411, introduced on September 7, 2026, proposes a new mechanism for broadcasting execution payloads in Ethereum by chunking payloads and using Merkle roots for efficient verification. This design aims to improve scalability and reduce propagation latency as execution payload sizes grow.
A September 7 forum update describes changes to the existing EIP-8148 draft, including setting sweep thresholds during registration and limiting effective balance at the chosen threshold. The current specification covers 0x02 credentials.
Ethereum’s frame-transaction proposal lets validation code inspect planned calls. Execution results remain unavailable until those calls finish.