Ethereum's core development ecosystem remained highly active this week, with protocol contributors advancing Glamsterdam testing, refining Hegota's early upgrade scope, discussing FOCIL specification changes, reviewing client readiness, and tracking a fresh wave of EIP and ERC activity.

This edition of Ethereum Core Development Monitor brings together key updates from All Core Developers calls, Fellowship-style research discussions, client repositories, Ethereum research forums, and standards activity. The goal is to provide a weekly view of how Ethereum's roadmap is evolving across governance, implementation, and research.

For readers following Ethereum's upgrade pipeline, this monitor connects closely with EtherWorld's broader coverage, including State of Upgrade – Glamsterdam Edition #1, State of Upgrade – Hegota Edition #1, and recent All Core Developers Consensus Call summaries.

• Glamsterdam Remains the Immediate ACD Priority
• Hegota Begins Moving From Research to Proposal Evaluation
• FOCIL Development Advances Through Specification Changes
• Client Repository Activity and Interoperability Updates
• EIP and ERC Activity Snapshot
• Research Forum Highlights and Upcoming Topics

Glamsterdam Remains the Immediate ACD Priority

The dominant theme across Ethereum's All Core Developers discussions this week was clear: Glamsterdam remains the immediate delivery priority.

Developers continue preparing for Glamsterdam Devnet-6, which is expected to become an important checkpoint for testing the upgrade's remaining protocol changes. Devnet-5 has reportedly stabilized with strong participation, but some client-specific issues remain unresolved. This reflects Ethereum's normal upgrade process, where devnets are used not only to test new features but also to expose edge cases across client implementations.

A major point of discussion was EIP-8282, which introduces builder execution requests through a system contract. The proposal separates validator and builder deposit flows, improving how the protocol handles builder-related execution requests. Core developers broadly agreed that the design is directionally correct, but they also emphasized that correctness matters more than rushing inclusion.

This is especially important because Glamsterdam is expected to include major infrastructure work connected to proposer-builder separation and execution-layer coordination. EtherWorld has been tracking this closely through its Glamsterdam upgrade coverage, where the upgrade is framed as a key step in Ethereum's post-Pectra roadmap.

Other Glamsterdam-related discussions included EIP-8037, which updates state gas refund behavior, and EIP-7928, which focuses on BAL state access restructuring. Developers are still reviewing implementation details for EIP-7928, showing that even seemingly narrow execution-layer changes can require careful cross-client coordination.

Another notable development was EIP-7904 being converted into an informational EIP after benchmarks showed that current clients already exceed targeted compute thresholds. This suggests that not every proposed repricing change needs to become part of a fork when empirical data shows the network can already handle the relevant workload.

Overall, Glamsterdam's current development phase reflects Ethereum's upgrade philosophy: test aggressively, avoid unnecessary changes, and keep client teams aligned before finalizing fork scope.

Hegota Begins Moving From Research to Proposal Evaluation

While Glamsterdam remains the near-term focus, Ethereum developers are already beginning to shape Hegota, the next major network upgrade expected after Glamsterdam.

EtherWorld's State of Upgrade – Hegota Edition #1 described Hegota as still being in its early design phase, with developers evaluating proposals related to censorship resistance, validator efficiency, transaction inclusion, and execution-layer improvements.

This week, two proposals stood out in Hegota discussions:

EIP-7645: Alias ORIGIN to SENDER

EIP-7645 proposes aliasing ORIGIN to SENDER, addressing long-standing technical debt in the EVM. The ORIGIN opcode has historically been discouraged because it can create unsafe assumptions in contract logic. By aligning it more closely with SENDER, Ethereum could simplify old behavior while reducing risks associated with legacy usage patterns.

This proposal also fits into Ethereum's larger account abstraction roadmap. As smart wallets and delegated execution patterns become more important, removing outdated assumptions from the EVM becomes increasingly valuable.

EIP-8304: Trustless Log and Transaction Index

EIP-8304 introduces a trustless log and transaction indexing mechanism using sorted SSZ tables and system-contract commitments. The goal is to allow users and applications to prove log or transaction inclusion without relying entirely on centralized indexing services.

This could become important for wallets, explorers, bridges, light clients, and rollup infrastructure. If Ethereum can make transaction and log proofs easier to verify, it would improve the trust model for many applications that currently depend on third-party data providers.

Hegota is still far from finalized, but these proposals show that Ethereum's next upgrade may combine neutrality, usability, and infrastructure improvements. For broader context, readers can also explore EtherWorld's guide: All You Need to Know About Ethereum Hegota Upgrade.

FOCIL Development Advances Through Specification Changes

One of the most important long-term research tracks remains FOCIL, or Fork Choice Enforced Inclusion Lists.

FOCIL is widely discussed as a leading Hegota candidate because it directly addresses Ethereum's censorship resistance guarantees. The basic idea is to make it harder for builders or block producers to indefinitely exclude valid transactions. Instead of relying only on block builders to decide what gets included, inclusion lists would give the protocol a stronger mechanism for enforcing transaction availability.

EtherWorld previously highlighted FOCIL's role in Hegota planning in its ACDC coverage, including Highlights from the All Core Developers Consensus Call #175, where FOCIL was selected as a major consensus-layer headliner for Hegota.

This week, FOCIL discussions focused on specification cleanup and enforcement details.

Developers agreed to remove inclusion-list bitlists from the specification because builders could potentially fake them without a reliable enforcement mechanism. This is a useful example of Ethereum's design discipline: if a mechanism creates complexity without enforceable security guarantees, it is better removed or redesigned.

Another major discussion involved payload status reporting. Developers proposed adding a new payload status field to help clarify whether branches satisfy inclusion-list requirements. This would help consensus clients reason more clearly about compliance across competing branches.

The team also discussed a non-finality circuit breaker, which would temporarily disable inclusion-list enforcement after extended periods without finality. This matters because censorship resistance mechanisms should not accidentally worsen chain instability during abnormal network conditions.

FOCIL is not just a technical feature. It represents Ethereum's broader commitment to credible neutrality. As block-building markets become more specialized, Ethereum needs protocol-level safeguards that preserve open access and prevent transaction exclusion from becoming a systemic risk.

Client Repository Activity and Interoperability Updates

Ethereum's upgrade process depends heavily on client diversity. Every protocol change must be implemented, tested, and validated across multiple execution and consensus clients before it can safely reach mainnet.

This week, client teams reported progress across several areas.

Consensus Client Updates

Lodestar rebased its FOCIL work on Glamsterdam Devnet-5 and confirmed that a previous serialization issue had been fixed. Lighthouse also rebased on Devnet-5 and continued testing its FOCIL implementation.

These updates are important because FOCIL touches consensus behavior. Any ambiguity in implementation could lead to interoperability issues, so early testing across clients is essential.

Post-Quantum Interoperability Work

Post-quantum development continued to reveal performance challenges. Several experimental clients reported progress, but proof-generation time and memory usage remain major concerns.

Some implementations are exploring optimizations to keep proof generation within acceptable timing limits. Others are addressing high memory usage and improving block processing. These discussions remain early, but they are important for Ethereum's long-term security research.

Post-quantum readiness is not an immediate mainnet upgrade item, but experimentation today helps Ethereum understand future trade-offs before they become urgent.

Execution API Standardization

Execution API work also progressed. The latest execution-apis v1.0.0 Beta 7 was released, while teams continued cleaning up documentation and aligning client behavior around default block parameters, error codes, and transaction method changes.

Execution APIs may not always receive the same attention as major EIPs, but they are critical for wallets, infrastructure providers, explorers, RPC services, and application developers. A stable v1.0 release would improve consistency across Ethereum's developer ecosystem.

EIP and ERC Activity Snapshot

Ethereum's standards process remained active this week, with several proposals entering Draft, Review, Last Call, Final, or Withdrawn status.

New Draft Proposals

Several new proposals entered Draft status, including:

• EIP-8256: Blob Streaming
• EIP-8272: Recent Roots for Frame Transactions
• ERC-8047: Forensic Token
• ERC-8290: Shielded Note Teleportation
• ERC-8217: Agent NFT Identity Bindings
• ERC-8100: Representable Contract State
• ERC-8054: Forkable ERC-20 Token

These proposals span data availability, privacy, identity, contract state representation, and token design. Their diversity shows how Ethereum's standards layer continues to evolve beyond only base-layer scaling.

Review and Last Call

A few standards also moved forward in the process:

• ERC-7796: Conditional Send Transaction RPC entered Review.
• ERC-8161: Transferable Tokenized Vault Requests advanced to Last Call.
• ERC-7813: Table-Based Introspectable Storage also moved into Last Call.

Last Call status is especially important because it signals that a proposal is approaching finalization unless major issues are discovered.

Final and Withdrawn Standards

Two notable standards reached Final status:

• ERC-4337: Account Abstraction Using Alt Mempool
• ERC-8126: AI Agent Verification

ERC-4337 reaching Final status is particularly important because account abstraction has become a central part of Ethereum's wallet roadmap. Meanwhile, AI Agent Verification reflects growing interest in verifiable AI execution and agent identity, a theme EtherWorld has explored in articles such as An Overview of WYRIWE – What You Read Is What You Execute.

On the other side, ERC-2770 and EIP-7701 were withdrawn, showing that Ethereum's standards process remains selective. Not every idea becomes a permanent part of the ecosystem, and withdrawal is often a healthy outcome when proposals are superseded or no longer fit current design goals.

Research Forum Highlights and Upcoming Topics

Ethereum research forums remained active across scaling, privacy, identity, gas economics, and AI-related governance.

One major research topic focused on Hegota scaling, including proposals to use the fixed 21,000-gas ETH transfer as an anchor for execution throughput and bandwidth analysis. Researchers discussed higher gas limits, calldata repricing, state growth, and history expiry implications.

Another active area was privacy. The GhostShard concept combines stealth addresses and account abstraction to create ambiguity around ownership and activity patterns without fully hiding transaction data. This type of research reflects Ethereum's search for practical privacy improvements that can work within public blockchain constraints.

Identity research also continued through discussions around DNS and ENS convergence. As institutions increasingly interact with tokenized assets and stablecoins, there may be growing demand for identity systems that bridge traditional internet infrastructure and Ethereum-native naming.

AI also remained a recurring theme. Researchers discussed autonomous agents as untrusted participants, emphasizing that protocols should use incentives, permissions, and constraints rather than assuming that AI agents behave honestly.

Looking ahead, several topics are likely to dominate the next round of Ethereum core development discussions:

• Glamsterdam Devnet-6 launch and stability
• Final decisions around EIP-7928
• Continued EIP-8282 implementation work
• FOCIL specification updates
• Hegota proposal evaluation
• Execution APIs v1.0 progress
• Further research into scaling, censorship resistance, and account abstraction

This week's Ethereum development activity shows a network operating across multiple timelines at once.

In the short term, developers are focused on stabilizing Glamsterdam and preparing Devnet-6. In the medium term, Hegota is beginning to take shape through proposals such as EIP-7645, EIP-8304, and FOCIL. In the long term, Ethereum researchers are exploring post-quantum security, gas-limit scaling, privacy, identity, and AI coordination.

The result is a protocol roadmap that remains both practical and forward-looking. Glamsterdam is about delivery. Hegota is about direction. The broader research ecosystem is about ensuring Ethereum remains neutral, scalable, resilient, and useful for the next phase of decentralized applications.

To promote your Web3 articles, events, and projects, you may reach out anytime via EtherWorld PR for submissions and collaboration.

Related Articles

1. New Leadership at Ethereum: A Fresh Start for the Blockchain Community
2. Hsiao-Wei Wang Joins Ethereum Foundation Leadership Team
3. Highlights from the All Core Developers Consensus Call #180
4. State of Upgrade – Hegota Edition #1
5. Vitalik Buterin’s 2026 Vision for Ethereum Foundation

To follow blockchain news, track Ethereum protocol progress, and read our latest stories, subscribe to our weekly today.