Execution Layer Meeting 204

[timbeiko]

Meeting Info

• Jan 30, 2025, 14:00-15:30 UTC
• Stream: https://youtube.com/live/JW2IWwVKRec
• Zoom: shared on #allcoredevs Discord channel shortly before the call
• Ethereum Protocol Calls Calendar subscription

Agenda

• Pectra updates
  • devnet-6
  • Testnet fork slot proposals
    • Holesky:
      • 3620864 (Wed, Feb 12 at 09:32:48 UTC)
      • 3670016 (Wed, Feb 19 at 05:23:12 UTC)
      • 3710976 (Mon, Feb 24 at 21:55:12)
    • Sepolia:
      • 7020544 (Wed, Feb 19 at 15:48:48 UTC)
      • 7061504 (Tue, Feb 25 at 08:20:48)
      • 7118848 (Wed, Mar 5 at 07:29:36)
  • Testnet config updates
    • added electra fields to configuration eth-clients/holesky#120
    • update config with fields required at Electra eth-clients/sepolia#99
  • Delay between picking mainnet slot and network upgrade
  • Audits overview
    • Final system contract addresses
  • Retrospective
• Fusaka planning
  • SFI & devnet inclusion
  • Update EIP-7607: Add EIP-7793 & EIP-7843 to proposed-for-inclusion in Fusaka EIPs#9276
• Hardware & bandwidth requirements
• EIP-7823
• ACDbot
• RPC Standards Call #0 #1261

[axic]

I'd like to put EIP-7823 on the agenda. Either me or @rodiazet will do an introduction.

[timbeiko]

@axic are you looking for feedback or to propose it for inclusion? If it's only feedback, we can have it at the end of the call assuming time permits. If you'd like to formally have it considered for the next fork, can you please open a PR to the fork Meta EIP with some context as well? Here's an example: ethereum/EIPs#9163

[axic]

@timbeiko we want to go for an initial temperature check.

Proposed it for Fusaka here: ethereum/EIPs#9251. The change itself is fairly small, so could fit, if there's consensus. If not for Fusaka, we'd like it for the next.

[kevaundray]

I would like to discuss the hardware and bandwidth requirements, set out here: ethereum/EIPs#9270

• Wanted to confirm that we would create a new EIP for every fork or whenever the specs change
• Call for finalization on the specs and say what the numbers are

[Marchhill]

Hey @timbeiko I'd like to propose EIP-7793 and EIP-7843, made a PR for Fusaka here: ethereum/EIPs#9276

[fredriksvantes]

Re the "audits overview" on the agenda; reports have been uploaded here: https://github.com/ethereum/audits/tree/master/Pectra

What's worth noting is that we ran the audits after one another, and fixes were implemented between each audit, which means that a finding done by Blackthorn was likely fixed by the time Dedaub started their review, and so on.

The audits took place in this order: 1. Blackthorn, 2. Dedaub, 3. PlainShift and then finally 4. Sigma Prime

Daejun from a16z also formally verified this at the same time, using halmos

[abcoathup]

Eth Magicians: https://ethereum-magicians.org/t/all-core-devs-execution-acde-204-january-30-2025/22594

[timbeiko]

@axic @kevaundray I added both of your topics to the agenda. @fredriksvantes thanks for sharing the additional context!

@Marchhill, I also added your PR to the agenda, but before we get into the weeds of Fusaka planning, there are a couple important things we need to discuss:

1. We previously agreed to not SFI more EIPs in forks until the current `SFI' EIPs have been implemented on devnets (Update EIP-7723: CFI/SFI & Devnets EIPs#9126). For Fusaka, this means having EOF + PeerDAS running on devnets smoothly.
2. The Pectra Retrospective, which already includes proposals to change how we think about hard fork scoping.

We can start this conversation on this week's call, but I want to make sure we give everyone the time to chime in on EthMagicians before making final decisions.

[jflo]

Would like to just have this mentioned as a reminder:

RPC Standards Call 0 on Feb 3rd.

#1261

[rolfyone]

Just fyi raised eth-clients/holesky#120 and eth-clients/sepolia#99 which should cover off on the fields other than the fork epoch for electra for sepolia and holesky.
Sepolia would require 97,98,99 to be electra ready IMO
Holesky would need 118,119,120 to be electra ready.
Theres one of those on each dependent on the final testnet dates, the rest cover other changes such as electra parameters and constant rename / removal