EIP Fun Weekly #82: Guidelines for Finalizing ERCs, Pectra Upgrade Timeline Confirmed
A weekly resource exploring the latest EIPs, ERCs, key updates in the Ethereum protocol.
Welcome to read the 82th issue of EIP Fun Weekly. Let's take a look at what happened in the EIP community last week.
Meeting Updates
Ethereum All Core Developers Consensus Call #149
Pectra Upgrade
Devnet 5 Bugs: Gas estimation bug caused a three-way chain split, with ongoing bug fixes from client teams.
Devnet 6 Launch: Developers agreed to launch Devnet 6 after addressing bugs on Devnet 5 and completing hive testing.
Public Testnet Timeline: Sepolia testnet upgrade on February 12, Holesky on February 19, and mainnet activation on March 11, 2025.
Shadow Fork: A shadow fork will be used to test Pectra by forking a live network to simulate real-world conditions.
Other Information
PeerDAS Development: PeerDAS aims to increase blob throughput by 8x, with testing ongoing but requiring more research.
BPO Fork Proposal: BPO forks are proposed to scale Ethereum’s blob capacity incrementally, though concerns about complexity remain.
Fusaka Fork Planning: Developers discussed improving Ethereum’s fork planning process in preparation for the Fusaka upgrade.
Pectra Testing Call: A testing call on January 27, 2025, will align teams ahead of upcoming deadlines, with less than 100 days left to remove pre-Merge history.
Weekly EIP & ERC Highlights
EIP-7865: Guidelines for Finalizing ERCs
Provides guidelines to help ERC authors create clearer, more testable standards that are easier to adopt and implement, with steps to gather community feedback.
Purpose: Offers practical advice for finalizing ERCs, focusing on user stories, trade-offs, and conformance to ensure smoother adoption in wallets, smart contracts, and decentralized apps.
Key Benefits:
Better Adoption: Clearer, more practical ERCs are more likely to be implemented.
Improved Feedback: Encourages authors to revise with real-world challenges in mind.
Clearer Specifications: Defines specific behaviors, failure cases, and conformance, improving clarity for implementers.
Conformance: Establishes clear expectations for how different roles interact with the ERC.
Key Components:
User Stories: Ensure clear, detailed use cases in the "Motivation" section.
Trade-offs: Be transparent about the pros and cons of the ERC.
Backwards Compatibility: Consider existing solutions and maintain compatibility where possible.
Conformance Definitions: Define expected behaviors and how different participants should conform.
Upcoming EIP Events
RPC Standards Call #0
Date & Time: 2025/02/03 , 15:00 UTC
For more details about the meeting agenda, you can visit here.
PeerDAS Breakout Room #16
Date & Time: 2025/02/04 , 10:00 UTC
For more details about the meeting agenda, you can visit here.
Consensus-layer Call 150
Date & Time: 2025/02/06 , 14:00 UTC
For more details about the meeting agenda, you can visit here.
Stay Up to Date
EIP Fun, co-initiated by LXDAO and PlanckerDAO and operated by ETHPanda, has been launched to act as the 'layer 2' of the EIP ecosystem, simplifying and accelerating EIP adoption.
Please inform us if you have any additional suggestions or feedback. EIP Fun is a fully open-source and community-driven public good! Donate to us here.