Title: All_Core_Devs___Execution__ACDE___203__January_16_
Category: Protocol_Calls___happenings

Author: abcoathup
Date: 2024-12-27T02:46:07.726Z

Agenda
Execution Layer Meeting 203 · Issue #1227 · ethereum/pm · GitHub moderated by @timbeiko
Summary




All Core Devs - Execution (ACDE) #203, January 16, 2025 Protocol Calls & happenings


Action Items

Teams should review the EIP-7702 “delegation instrospection” proposal by Monday, with the expectation of making a final spec decision on Monday’s testing call.
Merge the PR adding  baseFeeUpdateFraction to the EIP-7840 configs by Monday
Clarify the EIP-7691 fork boundary behaviour in the EIP by Monday
Update EIP-2537 to mandate the use of integer division for the G2 operation by Monday
Confirm Pectra testnet deployment timestamps on next week’s ACDC
@jflo will coordinate a breakout…
  

Recording



youtube.com


- YouTube
Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.






Additional info

Pectra-devnet-5 live
Ethereum All Core Developers Execution Call #203 Writeup | Galaxy by @Christine_dkim
Highlights of Ethereum's All Core Devs Meeting (ACDE) #203 by @yashkamalchaturvedi

Author: yashkamalchaturvedi
Date: 2025-01-17T04:35:55.533Z

Call Highlights: Highlights of Ethereum's All Core Devs Meeting (ACDE) #203

Author: timbeiko
Date: 2025-01-17T17:37:12.855Z

This is great, @yashkamalchaturvedi! Thank you for putting it together so promptly !
I had a draft summary that I’ll paste here as well, but it’s nice to see others stepping in to recap what happened!

Author: timbeiko
Date: 2025-01-17T17:40:15.520Z

Action Items

Teams should review the EIP-7702 “delegation instrospection” proposal by Monday, with the expectation of making a final spec decision on Monday’s testing call.
Merge the PR adding  baseFeeUpdateFraction to the EIP-7840 configs by Monday
Clarify the EIP-7691 fork boundary behaviour in the EIP by Monday
Update EIP-2537 to mandate the use of integer division for the G2 operation by Monday
Confirm Pectra testnet deployment timestamps on next week’s ACDC
@jflo will coordinate a breakout for client teams to discuss JSON-RPC standadization
@kevaundray will create an informational EIP to document node’s minimum hardware and bandwidth requirements in different contexts, @timbeiko will open a discord channel to discuss the topic
EIP Editor Workshop Jan 17, 16:00 UTC

Call Summary
Pectra
Spec Changes

devnet-5 went live 30 minutes before ACDE’s start, with Pectra activating 4 minutes before.

Erigon encountered a gas estimation issue which is being investigated
The devnet includes recent changes to EIP-7623


Teams agreed to store baseFeeUpdateFraction in the EIP-7840 configs (PR), to be merged by Monday’s testing call
Teams agreed to clarify EIP-7691 to specify that, on the fork block, the Pectra parameters will be used, matching many of the current implementations. The testing team has a PR (ADD LINK) already and one for the EIP will follow by Monday.
EIP-2537 does not currently specify how to handle divisions in the G2 call, causing issues with recent gas pricing changes. Instead of updating the gas costs, as originally proposed, the EIP will be updated to mandate using integer division.
Otim labs proposed adding “delegation instrospection” to EIP-7702, allowing for EXTCODE* opcodes to act on the “delegation designator” rather than just the prefix. Teams were generally positive but some of them needed to review the proposal further and were concerned about the impact on testing. The devops team confirmed this change could be tested in upcoming shadow forks, even if we do not have further devnets. We agreed to make a final decision about the proposal on Monday’s testing call.

Audits

Audit results for Pectra system contracts will be presented on the next ACDE. None of the audits found significant issues in the contracts, and all minor issues have been fixed in the current versions of the contract.

Testnet Deployment

On next week’s ACDC, we plan to finalize the testnet deployment schedule for Pectra. Teams agreed to combine the activation for both Holesky and Sepolia into a single client release. The proposed schedule is:

Feb 3: Client releases deadline
Feb 4-5: Public announcement
Feb 12: Holesky Fork
Feb 19: Sepolia Fork



Gas Limit

Several teams already updated their default configurations to have a 36M gas limit
We agreed to increase the Holesky gas limit to 60M once Pectra is deployed on the network, and then further once Pectra is deployed on mainnet.

JSON RPC Standardization

Felix presented his views on the current state of JSON-RPC standardization
Teams agreed to focus on passing common test suites and to discuss ways to gather input from JSON-RPC users such as L2s, wallets and infrastructure providers to help shape the evolution of the spec.
A first breakout will be organized for client teams to further discuss implementation status, and a second one to bring in non-client teams and gather their input.

Node Requirements

Kev requested feedback on his node requirement (ADD LINK) document, as well as a proposal to specify minimal bandwidth requirements.
We agreed to merge these into a single informational EIP, and create a specific discord channel to continue conversations on the topic.

EIP Editor Workshop

EIP editors are organizing a workshop on Jan 17 to introduce new contributors to EIP reviews and editing: EIP Editors' Workshop · Issue #372 · ethcatherders/EIPIP · GitHub

Author: claravanstaden
Date: 2025-01-21T10:03:58.359Z

Hi Tim! I work on an Ethereum-Polkadot bridge and I have been updating our Ethereum light client with the Pectra updates. Our on-chain code (including fork version config) needs to go through an on-chain governance process that can take up to a month. I would like to ask at least a month’s notice from when mainnet’s Electra epoch is announced, to the actual fork epoch. I remember the Deneb fork epoch was announced 5 weeks or so before the fork epoch, which would be great if the same could be done for Electra.