Personal scope preference
- Whilst client team & EthPandaOps preferences are all important, the community should also take the opportunity to respond in a structured manner to upgrade scoping.
- I summarized ACD calls async for 3.5 years (former editor of weekinethereumnews.com) and collected summaries/writeups in Protocol Calls & happenings - Fellowship of Ethereum Magicians. The following is my two cents.
Roadmap focus
- The Surge - L2 scaling
EIPs should generally only be considered for inclusion if they significantly move the roadmap forward.
Scheduled for inclusion (SFI)
- EIP-7594 PeerDAS: L2 scaling
Considered for inclusion (CFI)
- EIP-7892 Blob Parameter Only Hardforks: L2 scaling
- EIP-7839 Unified Network Configuration: reduce config complexity
- EIP-7910 eth_config JSON-RPC Method: reduce config issues
Denied for inclusion (DFI)
- EIP-7692 EOF: Geth were against. (Client teams with greater than one third market share & DevOps should have an informal veto. Currently this would be Geth & Nethermind)