Skip to content

All Core Devs - Testing (ACDT) #81, June 1, 2026 #2085

Description

@danceratopz

UTC Date & Time

June 01, 2026, 14:00 UTC

Agenda

Glamsterdam

Heads up: As repricing specs have stabilized, the fortnightly Wednesday Gas Repricing Breakout Calls held by @misilva73 have stopped; any required discussion will happen in ACDT.

Devnet Status and Benchmarking
  • bal-devnet-7, hive dashboard, dora:

  • Benchmarking / repricing status (@misilva73 + client teams):

    • State of client BAL optimizations in bal-devnet-7 branches? Per-client round.
      • ethrex reports ~3x exec speed-up vs devnet-3?
      • Nethermind OOM affecting benchmarking results?
      • Besu (shipped AOT and an OOM fix).
      • Geth BAL opt branch this week?
    • How much of a priority is it to replace the perf-devnet-3 snapshots with ethereum/state-actor? (execution-specs#2916). This can be deferred to tomorrow's Gas Lighting call.
  • glamsterdam-devnet-4 not so healthy as of ~May 25::

    • Chain split ~slot 22800; prysm-nethermind-1 forked on EMPTY after missing the 22800 payload.
    • PR (consensus-specs#5307).
    • Recover the chain or abandon for devnet-5?
Spec Changes
Glamsterdam spec next TODOs
  1. Finalize gas repricings numbers (ongoing on bal-devnet-7).
  2. CL stability; resolve consensus-specs#5307.
  3. Include new EL EIPS:
    i. EIP-8246 (remove self-destruct burn).
    ii. EIP-2780 (intrinsic gas) and EIP-8038 (state-access gas cost update), requires 1., but not 4.
  4. Updated EL EIP: EIP-7954 (increase max contract size w/larger numbers).
  5. EL EIP spec changes as above.
  6. Any other CL changes?

i. EIP-8045: Exclude slashed validators from proposing.
ii. EIP-7688: Forward compatible consensus data structures @etan-status?
iii. ...

Options and scoping of glamsterdam-devnet-5 OR next devnets
  1. Clean glamsterdam-devnet-4 spec relaunch. (CL ask from ACDC #179: stability first, no scope increase for 2 weeks).
  2. glamsterdam-devnet-4 with bal-devnet-7 (with or without some SFId EL EIP spec changes, details below).
  3. As 2. but with bal-devnet-7 with 2780/8038 placeholder numbers.
  4. Launch two devnets simultaneously and merge into later devnet:
    i. glamsterdam-devnet-5 for CL stability.
    ii. bal-devnet-8 for close-to-final EL spec.
    iii. -> merge into glamsterdam-devnet-6.
  • Timing of devnet launch(es)?
Other Topics

Please comment on this issue with other topics!

Last call:

Call Series

All Core Devs - Testing

Autopilot Mode

  • Use autopilot (recommended defaults for this call series)
🔧 Meeting Configuration

Duration

60 minutes

Occurrence Rate

weekly

Use Custom Meeting Link (Optional)

  • I will provide my own meeting link

Display Zoom Link in Calendar Invite (Optional)

  • Display Zoom link in invite

YouTube Livestream Link (Optional)

  • Create YouTube livestream link

Metadata

Metadata

Assignees

No one assigned

    Labels

    ACDType: All Core Dev calls - execution & consensusprotocol-callAutomatically applied by issue template

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions