All Core Devs - Execution (ACDE) #202, December 19 2024

Protocol Calls & happenings
,
1

Agenda

Execution Layer Meeting 202 · Issue #1209 · ethereum/pm · GitHub moderated by @timbeiko

Agenda summary

by @Nixo (Copied from Twitter)

  • Pectra:
    • Testnet update (who: EL & CL devs)
    • New EIP! EIP-7840 introduces a constant blobSchedule in the genesis file, allowing the protocol to define target & max blobs. General support from EL teams. More info in agenda. (who: EL devs)
    • Update EIP-7702 to support uint256 chain IDs. Proposed by @Optimism (who: rollups)
  • AllCoreDev process improvements. Change when we move EIPs from “considered for inclusion” to “scheduled for inclusion” (who: Protocol Support, anyone interested in the process)
  • :mega: Specific ask: Should EIP-4444 bump the protocol version or not? Needs input from execution devs. More info in agenda linked above
  • General update: Progress is being made w some contention on when to target for dropping history & should history be dropped in an update or should node operators be given a flag to drop premerge history? & does it require coordination? Most consensus is ‘probably a good idea’ w minority opposition. Suggested target May 1st.
  • Oppose removal of NewBlock & NewBlockHashes. These removals make the protocol incompatible w blockchains that aren’t PoS (who: @0xPolygon, app devs bridging b/t Ethereum & non-merged networks)
  • EIP-7808: Meta EIP that reserves a range of tx types for Rollup Improvement Proposals (RIPs) to avoid conflicts w EIPs if using the same identifiers

Summary

Recording

Additional info

2 Likes
2

Action Items

Pectra

  • EIP-7840 is SFI’d as a replacement to EIP-7742 (PR)
  • Pectra system contract audits results to be presented in January

Devnet-5 Changes

Other Topics

Call Summary

Pectra Devnets

Pectra Spec

History Expiry

  • @pipermerriam shared updates on EIP-4444’s rollout plan
  • There was general agreement about dropping pre-merge history on May 1st, but a lot of back and forth regarding the implementation and testing details until then. Notably, what eth/ protocols should clients add/change as part of the Pectra hard fork release, if and how to deploy history expiry to testnets prior to mainnet activation, etc.
  • Teams agreed to continue the conversation on the R&D discord and potentially have a breakout room in January if things can’t be resolved async

Decoupling Gas Limit & Payload Size

  • @arnetheduck shared a set of proposals to deal with gossip limitations on the consensus layer, a few of which involve adding additional restrictions to the execution layer.
  • EL developers were generally against adding size restrictions to blocks in addition to the gas limit, or having a per-transaction gas limit, but further conversation is needed. Teams are encouraged to share their thoughts on the issue directly.

eth/69

  • @yperbasis proposed keeping NewBlock and NewBlockHash as part of the eth/69 networking protocol, as they are useful messages for networks who did not go through The Merge. Ethereum doesn’t broadcast these fields post-merge anyways.
  • No objections, OK to merge the PR

EIP-7503

  • Feedback requested on the latest changes to the EIP, no comments on the call.
  • @petertdavies highlighted that there are legal considerations people should be mindful of when engaging with these proposals.

EIP-7508

  • This EIP proposes to reserve a transaction range for L2s to adopt different transaction types than L1, similarly to what EIP-7587 did for precompile addresses. No objections to move from Draft to Review.

EIP-4803

  • Confirmed that this EIP has been retroactively applied by client teams, but not in EL specs yet. @petertdavies to open an issue to track this in EELS, but no objections to considering the EIP “applied from genesis”

Other updates

2 Likes