All Core Devs - Testing (ACDT) #90, August 3, 2026

[jtraglia]

UTC Date & Time

August 03, 2026, 14:00 UTC

Agenda

Devnet status updates

• Updates on glamsterdam-devnet-7
• Updates on glamsterdam-devnet-8

Discussions

• An update on repricings.
  • All Core Devs - Testing (ACDT) #90, August 3, 2026 #2174 (comment)
  • Led by @misilva73.

EL breakout

• Proposal to only support discv5 (not discv4) on devnet-8.
  • All Core Devs - Testing (ACDT) #90, August 3, 2026 #2174 (comment)
  • Led by @cskiraly.
• Using BAL data to keep hot state cached after snap sync.
  • All Core Devs - Testing (ACDT) #90, August 3, 2026 #2174 (comment)
  • Led by @jochem-brouwer.

CL breakout

• Open questions around specs for direct builders.
  • All Core Devs - Testing (ACDT) #90, August 3, 2026 #2174 (comment)
  • Led by @nflaig & @JasonVranek.
• Should bids from builders with insufficient balance be ignored or rejected?
  • https://discord.com/channels/595666850260713488/1531600508253372547/1533817848726814970
  • Led by @jtraglia.
• Ignoring parent bids at epoch boundaries.
  • https://discord.com/channels/595666850260713488/1531600508253372547/1533821041346871448
  • Led by @nflaig.

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

[github-actions]

⚡ Protocol Call Resources:

✅ Zoom: Join Meeting
✅ Zoom (CL Breakout): Join Meeting
✅ Calendar: View | Add to Calendar
✅ Discourse: Discussion Topic

[cskiraly]

I would like to propose to make devnet-8 discv5 only (discv4 turned off in clients and in bootnodes) if there are no objections.

[jochem-brouwer]

At EL breakout I want to ask clients about their snap/2 implementation and if clients use the unlocks what BALs give here as extra bonus/benefit: the recent BAL state reads and state writes are the "hot" state, and to "hot sync" the client, client should ensure that this state is in their "hot state", for LSM databases this implies ensuring this state is in L0/L1 or applying some specific algorithm to ensuring this is in L0/L1.

For instance, what could be done is once snap sync is done, triggering dummy writes to this state to ensure it is in L0/L1. CC @rjl493456442, should we add this to https://eips.ethereum.org/EIPS/eip-8189#synchronization-algorithm ?

EDIT: this should be done at end of EL breakout as this is not consensus critical for the execution layer.

[nflaig]

for the CL breakout, would like to quickly talk about

• add per-key builder configuration endpoints keymanager-APIs#88
• Add gloas builder flow: produceBlockV4, builder preferences, block forwarding beacon-APIs#630
• Clarifications on builder spec builder-specs#165

Jason has been doing great job getting the PRs in a good shape but there are few open questions

• (1) per-builder config for p2p bids
• (2) versioning on the keymanager api (fork versioning?)
• (3) keymanager config interchange format for import/export similar to eip 3076

we should aim to get these merged in the next 1-2 weeks ideally

the e2e flow is documented here

• Builder config flow: per-key config across the three specs JasonVranek/epbs-config-flow#1

cc @JasonVranek

[misilva73]

I would like to give an update on repricings

[healthykim]

Sorry for the late comment. I think we need to revisit the discussion about making the EIP-8070 Engine API mandatory, which we decided to discuss here last time after ACDT

[misilva73]

Link to Repricing Update slides