Ethereum Cat Herders Meeting #139

[poojaranjan]

Date and Time

Oct 09, 2024 at 14:00 UTC

Location

Join Zoom Meeting

Agenda

New users on ECH Discord and/or contributor's introduction

1. ECH updates

ECH Engineering (@geovgy)

• Website
• L2E Page
• Action Items from Last Meeting:
  • Update general stats on the website (followers, subscribers, etc.)- @geovgy
  • Add a disclaimer about educational purposes and not providing financial advice on the website - @geovgy
  • Update copyright on the ECH website and add “A project by ECH institute” - @geovgy

ECH Ops (Pooja, akash, Hgedia, Notes contributors)

• ECH Podcast
• Ecosystem Project Demo
  • EPD #14: Ethereum Follow Protocol with brantly.eth
• Meet The Herders - Need Volunteer
• EIPsInsight
• PeepanEIP
• Grants
• WiEP at EthSingapore
• Others
  • ethereum/pm breakout room & other updates
• Dev meetings notes

2. Ethereum network upgrades

• Pectra Testing call

Summary from the testing call: `pectra devnet-3`: - Lighthouse bug when proposing blocks, there's a PR that is open with the fix: https://github.com/sigp/lighthouse/pull/6464. - Besu bug is still pending to be resolved with an open PR: https://github.com/hyperledger/besu/pull/7717.

pectra devnet-4

• There was a discussion on whether the CL should send back the entire list of requests to the execution layer, the decision at first was to leave the specs as is, which entails sending the full requests list. At a later point on the call, <@755590043632140352> raised concerns regarding the amount of data being serialized and JSON-formatted in Engine API is an unnecessary overhead, and it should be simplified to sending a simple hash that the CLs should compute (not hash-tree-root but a different sha256 commitment). At the end of the call, the sentiment changed to agree that we should apply this change and the CL should simply compute the hash and send it back instead of the full list, therefore the PRs need to be updated. On-going discussion can be found in this thread: https://discord.com/channels/595666850260713488/1288408367068610585

• Open PRs

  • [Beacon API] Update submitPoolAttestationsV2 endpoint decision to skip this for devnet-4 on the grounds that is not ready.
  • [Builder API] add initial electra spec: requires Engine API changes to be merged first
  • [Consensus-specs]: eip7685: Pass execution_requests to notify_new_payload At the time of writing this contains the full requests being sent back to the execution layer, needs a rework to send only the requests commitment hash (as specified in Update EIP-7685: group requests into request-data ethereum/EIPs#8924) instead.
  • [Engine API]: engine: Make execution requests a sidecar, take 2 : At the time of writing this PR is currently specified to send the full requests lists in the engine_newPayloadV4, and needs to be updated to send the requests hash.
  • [Execution EIP] Update EIP-7702: add several clarifications to align spec with tests, no opposition regarding this PR, should be accepted and merged for Devnet-4.
  • [Execution EIP] Update EIP-7702: Do not allow authorization nonce equal to 2**64 - 1, also no opposition regarding this PR, should be accepted and merged for Devnet-4.
  • [Execution EIP] Update EIP-7702: restrict field sizes needs an update to move from draft status and be merged for devnet-4.

eof

• Not many updates from last week, path forward is waiting on devnet-4 to be released and then rebase Osaka (which contains only EOF at the time being) on top of it in order to launch osaka-devnet-0 at some point in the coming weeks.
• feat(forks,tests): Osaka ethereum/execution-spec-tests#869 is an open PR to the execution layer tests that has been prepared to rebase EOF to be in Osaka.

peerDAS

• Devnet-3 was launched with the same spec as devnet-2 in order to have a working devnet, but 14-15 hours ago there was an issue that caused all clients to be on their own different fork, and at the moment there is no lead on the culprit.

• Prague/Electra Network Upgrade Meta Thread
• EIP-7600: Hardfork Meta - Prague/Electra

3. Other Protocol & Application Development

Calls from the last week:
TBA

Playlists:

• ePBS Meeting Playlist
• EOA/AA Breakout Room Playlist
• eth_multicall Meeting Playlist
• Roll Call Meeting Playlist
• EOF Implementers Meeting Playlist
• Sequencing and Preconfirmation Call Playlist
• All ERC Dev
• ECH Meeting Playlist

4. Events, Fellowship, Hackathon

• WiEP @ In The Ether, EthSingapore 2024
• Plans for Devcon 2024? Attendees?

Useful resources

• Prague/Electra Playlist

5. New initiative/association/team discussion

TBA

6. General updates/discussion

• ECH Stats.
  • Warpcast - 9 Followers
  • Twitter - 7044 Followers
  • Discord - 2506 users
  • YouTube - 3443 subscribers
  • LinkedIn - 305 Followers

7. Review of outstanding action items from previous ECH meetings

The date for the next meeting is Oct 22nd, 2023 at 14:00 UTC

(If anything else, leave a comment.)