ACDT2026-09-28_098

AllCoreDevs - Testing #098

2026-09-28 3 decisions 396 transcript lines

Transcript

At a glance

200M gas limit remains safe pending devnet retest without debug tracing; no repricing decisions until clean measurement obtained
FCR new block tag to be opt-in only; no change to default FCU behavior; CL+EL pairs that support it coordinate independently
New block tag name preferred: 'confirmed' (over 'fast' or 'fcr')
EOD tomorrow — all client releases due for Sepolia Shadow Fork preparation
~1.5–2 weeks — Sepolia mainnet fork

Detailed notes

Testing Progress

  • •Devnet-8 stable over weekend under three attack variants; most clients processing blocks within ~6 seconds00:12:54
  • •Security team found memory-explosion bug in ethrex on devnet-8; already fixed00:14:12
  • •200M gas limit assessed safe: Pavel's attack peaks at 2.5s execution; Jochem's slow blocks were compounded by debug tracing running simultaneously00:17:41
  • •Significant gap between Benchmarker (~2.5s worst case) and devnet (~5s) for JUMPDEST analysis on 100M gas block; cloud-attached disks and active debug tracing are suspected causes00:46:00
  • •Plan: disable debug tracing on devnet-8, then rerun Pavel's and Jochem's attacks; Besu requests trunk branch be used instead of release for this test00:57:08

Critical Infrastructure

  • •EF bootnodes migrated from EthPandaOps to a new EF team; old nodes remain active until at least mainnet Glamsterdam, then deprecated00:41:17
  • •ELOC keys missing 0x prefix in JSON genesis file; Nethermind fails without it — PR open in eth-clients/mainnet for client approval00:39:46

Fork Status And Schedule

  • •Client release deadline is EOD tomorrow to prepare for Sepolia Shadow Fork00:13:59
  • •Releases confirmed: Teku (out), Lodestar (out), Reth (out), Besu (out), Nimbus (tomorrow), Prysm (tomorrow), Grandine (tomorrow)00:15:28
  • •After Sepolia fork, devnet-8 images will revert to latest trunk branches00:16:23

Fast Confirmation Rule Fcr

  • •Proposal: add a new 'confirmed' block tag (not repurpose 'safe') to enable FCR adoption; backwards-compat concerns from RPCs are blocking uptake00:24:11
  • •Chainlink went live with FCR today; other bridges and L2s want it; RPC providers blocked by needing to serve both safe and FCR simultaneously00:25:42
  • •Does not require a hard fork; consensus that FCR should be opt-in via compatible CL+EL pairs without changing default FCU behavior for all nodes00:33:25

Action items

  • •Disable debug tracing on devnet-8 and rerun JUMPDEST attacks (Pavel's and Jochem's) to isolate tracing overhead; use Besu trunk branchEthPandaOps (Stefan) + Pavel
  • •Open async thread (EF R&D Discord or EF Magicians) on 'confirmed' block tag PR (execution-apis #908)Julian Ma

Agenda

From the call issue #2230Show

Discussions

EL breakout

CL breakout

  • Potential builder payment edge case.
    • Led by @jtraglia

Key decisions

  • 200M gas limit remains safe pending devnet retest without debug tracing; no repricing decisions until clean measurement obtained

    Safety of 200M gas limit confirmed pending further testing without debug tracing.
  • FCR new block tag to be opt-in only; no change to default FCU behavior; CL+EL pairs that support it coordinate independently

    Fast Confirmation Rule will be optional via a new block tag without altering default forkchoice update behavior.
  • New block tag name preferred: 'confirmed' (over 'fast' or 'fcr')

    Preferred naming for the new block tag is 'confirmed'.

AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.