ECH Institute Podcast

The conversation revolves around the upcoming Glamsterdam and Hoodie forks, discussing the implications of validator deposits and the need for consensus on proposed changes to the Ethereum protocol. Key issues include the handling of builder deposits, the potential impact on validator outcomes, and the scoping of EIPs for future forks. The conversation delves into the complexities of protocol development, focusing on the need for clear rules and efficient processes in the Ethereum ecosystem. Key discussions revolve around the implications of upstreaming changes, the importance of client coordination, and the challenges of integrating experimental features into the main protocol. The conversation focused on various Ethereum Improvement Proposals (EIPs) and their implications for client diversity, penalties for inactivity, and withdrawal credential pre-registration. Participants discussed the importance of decentralization, the challenges of implementing changes, and the need for consensus among client teams.

Takeaways

• Glamsterdam and Hoodie forks discussed
• Concerns over validator deposit processes Protocol clarity is essential
• Efficient client coordination needed Client diversity is crucial
• Withdrawal credential issues need addressing

Chapters

• 00:00 Introduction to Glamsterdam and Hoodie Forks
• 21:16 Validator Deposit Processes and Concerns
• 39:31 Discussion on EIP 8365 and Zero Validators
• 45:15 Scoping EIPs and Future Protocol Changes
• 53:44 Streamlining Protocol Development
• 57:30 Establishing Clear Protocol Rules
• 01:01:10 Client Coordination Challenges
• 01:06:53 Debating CFI and DFI Processes
• 01:12:27 Optional Features and Client Support
• 01:17:31 Finalizing Decisions on EIPs
• 01:25:01 Measuring Client Diversity
• 01:26:25 Inactivity Penalties and Decentralization
• 01:37:11 Withdrawal Credentials Pre-Registration
• 01:44:46 Discussion on EIP Implementation Challenges
• 01:56:51 Deferring Decisions for Further Discussion

The conversation covers the successful Lamsterdam fork on the Sopolia test net, discussing builder participation and scheduling for the upcoming Hoodie fork. It also delves into insights from the mainnet shadow fork, EIP complexity assessments, and strategies for accelerating EIP implementations. The conversation focused on the evaluation and prioritization of various Ethereum Improvement Proposals (EIPs) with an emphasis on post-quantum readiness and client collaboration. Participants discussed the urgency of certain EIPs, the importance of addressing technical debt, and the need for consensus among clients regarding the implementation of new features.

Takeaways

• Successful Lamsterdam fork
• Need for better builder participation Focus on post-quantum readiness
• Importance of client collaboration

Chapters

• 00:00 Lamsterdam Fork Overview
• 18:39 Builder Participation Insights
• 20:19 Scheduling the Hoodie Fork
• 30:27 Mainnet Shadow Fork Insights
• 32:36 Hagota and EIP Complexity Assessments
• 47:15 Accelerating EIP Implementations
• 58:45 New EIP Proposals Discussion
• 01:01:51 Finalizing CFI Decisions
• 01:03:07 Transitioning to Post-Quantum Solutions
• 01:04:30 Client Perspectives on EIPs
• 01:06:14 Evaluating Urgency in EIPs
• 01:09:12 Contested EIPs and Client Opinions
• 01:12:25 Addressing Technical Debt
• 01:17:17 Consensus on EIP Prioritization
• 01:27:33 Exploring New EIP Proposals
• 01:34:30 Final EIP Discussions and Decisions

The conversation covers the ACDC 188 meeting, focusing on the upcoming Cepolia upgrade, incident response planning, and the scoping of the Hagoda upgrade. A significant portion is dedicated to discussing the proposal for quick slots, weighing its benefits against potential risks, particularly in relation to post-quantum security. The conversation delves into various Ethereum Improvement Proposals (EIPs), focusing on client perspectives regarding CFIness, concerns over CPU costs, and the implications of proposed changes like Top Up Sync and Execution Proofs. Participants express differing views on implementation challenges, efficiency, and the future direction of Ethereum's protocol.

Takeaways

• Cepolia upgrade is imminent
• Quick slots proposal sparks debate Diverse client opinions on CFIness
• Concerns about CPU costs and efficiency

Chapters

• 00:00 Introduction to ACDC 188 and Agenda Overview
• 08:09 Cepolia Upgrade and Fork Details
• 10:10 Incident Response Plan and Coordination
• 15:07 Hagoda Scoping and EIP Updates
• 24:49 Discussion on Quick Slots Proposal
• 51:03 Concerns and Considerations for Quick Slots
• 52:55 Client Perspectives on CFIness
• 57:40 Concerns Over CPU Costs and Implementation
• 01:01:26 Consensus on CFI and Future Steps
• 01:04:15 Introduction to Top Up Sync EIP
• 01:10:49 Debate on Control and Efficiency in Syncing
• 01:18:52 Discussion on Execution Proofs EIP

The conversation focused on updates regarding the DevNet, discussions on the upcoming Sepulia fork, and adjustments to gas limits. Additionally, there were in-depth discussions on performance issues, client retention windows, and various EIPs that are being considered for future implementation. The conversation focused on the decision-making process for Ethereum Improvement Proposals (EIPs), emphasizing the importance of community feedback and collaboration among stakeholders. Various EIPs were discussed, with decisions made on their classification and prioritization based on client input and technical considerations.

Takeaways

• Successful testing of fork transition
• Discussion on gas limit adjustments Decisions on EIPs are crucial
• Collaboration is key for progress

Chapters

• 00:00 DevNet Updates and Fork Transition
• 14:17 Gas Limit Discussions for Sepulia
• 16:18 Performance Issues and Benchmarking
• 31:01 Client Retention Windows and Adjustments
• 48:29 EIP Discussions and Future Proposals
• 59:44 EIP Decision-Making Process
• 01:03:18 Community Feedback and Support
• 01:07:02 Opcode Discussions and Proposals
• 01:16:08 Evaluating EIPs and Client Input
• 01:25:05 Finalizing EIP Recommendations

The conversation covers the topics of DevNets, network testing, protocol upgrades, and fork dates. It also addresses the issues related to P2P circuit breakers and the need for client releases. The discussion explores the challenges and considerations for scheduling the Cepolia and Hoodie forks, as well as the testing of direct connections to builders for mainnet readiness. The conversation covers the testing and integration of software on DevNets, the planning and scoping of EIPs for upcoming forks, and the discussion around the scope of EIP 8365. The scoping of EIPs involves client rankings, technical discussions, and considerations for future forks. The conversation also delves into the deprecation and force exit of zero validators and the implications of these actions. The conversation focused on the discussion and decision-making process for various EIPs, including forced exits, issuance changes, and broader community impact. The core developers emphasized the need for a comprehensive and inclusive decision-making process, considering the impact on stakeholders and the broader community.

Takeaways

• DevNets activation and testing
• Protocol upgrades and deprecation of network protocols
• Scheduling of fork dates and client releases
• Importance of P2P circuit breakers for network security
• Testing direct connections to builders for mainnet readiness DevNets play a crucial role in testing and integrating software for upcoming releases.
• The scoping and planning of EIPs for upcoming forks involves client rankings, technical discussions, and considerations for future forks. Inclusive decision-making
• Community impact

Chapters

• 00:00 DevNets and Protocol Upgrades
• 15:01 Scheduling Fork Dates and Client Releases
• 19:47 P2P Circuit Breakers and Network Security
• 29:46 Testing Direct Connections to Builders
• 32:06 Testing and Integration on DevNets
• 35:15 Planning and Scoping of EIPs
• 55:42 Discussion on EIP 8365 Scope
• 01:05:58 Forced Exits and EIP 8365
• 01:06:35 EIP Scope and Community Consensus
• 01:09:03 PQ Roadmap and EIP Prioritization
• 01:10:37 DFI and CFI Decisions
• 01:11:40 Issuance Changes and Community Impact
• 01:20:26 Governance and Decision-Making Process
• 01:28:30 Future EIP Discussions and Community Engagement

Execution Layer Meeting 245 [2026-09-10] | ACDE 245

The meeting covered updates on DevNet 9 and DevNet 8, consensus spec changes, EIP discussions, engine API SSZ migration, and setting testnet times. The meeting concluded with a reminder about EIP tier rankings.

Takeaways

• DevNet updates revealed issues and the need for further testing.
• Consensus spec changes were discussed and planned for implementation.

Chapters

• 00:00 DevNet Updates
• 10:34 Consensus Spec Changes
• 13:23 EIP Discussions
• 16:27 Engine API SSZ Migration
• 23:22 Setting Testnet Times
• 31:05 EIP Tier Rankings Reminder

The conversation covers various topics including trustless log index, DevNet updates, client preferences, and API specifications. The discussion also delves into the proposed EIPs and their potential impact on the upcoming fork. The conversation covers a detailed discussion on the EIPs 8130 and 8141, focusing on the technical aspects, implementation, and implications for the Ethereum ecosystem. The participants express their views and concerns, leading to a decision to move forward with SFIing frames and continuing with frame updates from the AA breakouts.

Takeaways

• Trustless log index API specifications
• Client preferences for upcoming fork
• Proposed EIPs and their potential impact on the fork EIP 8130 and 8141: The discussion revolves around the technical details and implications of EIPs 8130 and 8141, with a focus on their impact on the Ethereum ecosystem.
• SFIing Frames: The decision to move forward with SFIing frames is made, with a commitment to address concerns and collaborate with L2s and the ecosystem for successful implementation.

Chapters

• 00:00 Trustless Log Index and API Specifications
• 10:15 DevNet Updates and Client Preferences
• 42:47 Proposed EIPs and Their Impact on the Fork
• 52:50 Technical Discussion on EIPs 8130 and 8141
• 01:38:30 Decision to Move Forward with SFIing Frames

The conversation covers updates on DevNet 8, planning for a non-signality network, alignment on TestNet dates, discussions on EIP proposals, and the process of EIP tier ranking and selection.

Takeaways

• DevNet 8 stability and issues
• Planning for non-signality network
• Alignment on TestNet dates
• EIP proposal discussions
• EIP tier ranking and selection process

Chapters

• 00:00 DevNet 8 Status Update
• 10:23 Non-Signality Network Planning
• 27:29 TestNet Date Alignment
• 33:43 EIP Proposals and Discussions
• 55:06 EIP Tier Ranking and Selection

This was Execution meeting #243 on August 13th focused on DevNet 8 updates and EIP proposals for the upcoming Glasgow (Glas) and Hagada forks. Barnabas reported that DevNet 8 (PlatoBerget) launched recently with growth activation planned for the following week, and the Glasgow fork would go live on Thursday at 7:50 AM UTC. Joachim presented final gas repricing results, confirming that broadcast limits could be safely raised to 200 million gas (three times the current limit) without requiring re-release of client specifications. The team discussed EIP 8061 for introducing a new gas limit configuration parameter to allow staged increases, which was approved by consensus layer clients. Kev discussed history expiry requirements for 2TB node operators, with most clients planning to drop history to approximately 5 months or fork minus one. The meeting then moved through 17 EIP proposals for Hagada, covering topics including linear page-based memory costing, refund removal, call-up code optimization, net gas metering for account changes, and precompiles for post-quantum cryptography. The final major discussion centered on Native Account (AA) implementation, where there was debate between EIP 8130 and 8141, with concerns raised about EIP 8141’s impact on L2s and potential incompatibilities across the ecosystem.

Takeaways

• DevNet updates
• Gas repricing results
• History expiry
• EIP proposals Native AA implementation is a topic of discussion
• Different EIPs proposed for native AA
• Concerns about EVM incompatibility and performance
• Desire for consensus and alignment between client teams and ecosystem builders

Chapters

• 00:00 DevNet Updates
• 10:37 Gas Repricing Results
• 20:55 History Expiry
• 27:38 EIP Proposals
• 50:55 Native AA Implementation
• 51:26 EIP 8077: Rational and Messaging Levels
• 52:17 Scaling the Public Mempool
• 54:08 MLDSA Precompiles Proposal
• 54:30 EIP 8355: MLDSA Verification
• 01:02:32 EIP 8372: Normalized State Gas Limit
• 01:06:52 EIP 8375: Mandatory Burn of Execution Rewards
• 01:11:49 EIP 8219: Checked Arithmetic Opcodes
• 01:17:49 Frames and Native AA Decision