EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
EIPsInsightEIPsInsight
Sign in

Protocol calls

AllCoreDevs and breakout calls where upgrade decisions happen — agendas from ethereum/pm, recordings, and AI summaries, synced automatically.

Upcoming

Parsed from open agenda issues on ethereum/pm.

Recent calls

Latest calls with recordings and summaries from the ACDbot pipeline — filter by series below.

SSZSSZ Engine API #0022026-07-10
Targets
  • •Next SSZ Engine API call in 2 weeks (approx. July 24, 2026); top-up sync and namespace scoping documents to be circulated beforehand — 00:51:29
Decisions
  • •Agreed SSZ Engine API must specify which ETH-namespace endpoints are available on the engine port, consistent with Beacon API encoding conventions — 00:43:54
  • •ETH-namespace method list for SSZ Engine API should be as minimal as possible; no automatic carry-over from JSON-RPC engine spec — 00:49:50
Highlights
  • Testing Updates:
    • ·SSZ support from project ZKEVM being integrated into EELS Amsterdam branch; reference vectors and REST abstraction to follow — 00:05:05
    • ·EELS planned to eventually serve engine requests as a temporary EL for CL testing; FastAPI/OpenRPC targeted short-term — 00:05:36
  • Ssz Engine Api Design:
    • ·Jacek (Nimbus) proposes REST path alignment with Beacon API namespace for coexistence on same port; especially relevant for unified clients — 00:07:46
    • ·Top-up sync gap identified: current Engine API has no reliable way for a CL to determine where to begin backfilling to an out-of-sync EL head — 00:08:56
    • ·Proposal: expose ETH get-latest-canonical-block (FCU-marked head) on engine port to enable CL-driven top-up sync without EL p2p — 00:36:30
    • ·SSZ REST Engine API currently lacks equivalents for ETH-namespace methods (chainID, syncing, etc.) that existing JSON-RPC engine spec guarantees; needs explicit scoping — 00:43:54
Action Items
  • •Marius Van Der Wijden — Prepare document explaining current ETH-namespace method list on engine port, rationale, and candidates for removal; bring to ACDE and ACDC for broader input — 00:49:11
  • •Tamaghna Chourdhuri / Dustin — Publish public document on top-up sync design (incorporating Jacek's HackMD and chain-following mechanism) to gather input from absent clients — 00:50:08
ACDCAllCoreDevs — Consensus #1822026-07-09
Targets
  • •Glamsterdam devnet-7 launch — early next week (week of July 14, 2026) — 00:23:52
  • •Public Gloas community devnet — early August 2026 — 00:43:37
  • •Hegota non-headliner EIP submission deadline — August 6, 2026 — 01:00:58
Decisions
  • •Tony's block-access-list EIP change included in devnet-7 (not deferred to devnet-8) — 00:22:48
  • •devnet-7 confirmed to include progressive containers — 00:24:08
  • •Blinded execution payload removed from Produce Block v4 stateful flow; PR to be polished and merged — 00:27:01
  • •Public Gloas app-testing devnet targeted for early August — 00:43:37
Highlights
  • Epbs Updates:
    • ·Produce Block v4: blinded execution payload for stateful flow being removed; adds complexity, minimal performance gain; approvals received — 00:25:21
    • ·Beacon API PR #625 (ProduceBlock v4 POST with per-builder auth/config): urgent feedback needed from staking pools, builders, DVT providers, and VC tooling — 00:31:38
    • ·ePBS circuit breakers: Teku and Lodestar implemented builder-index-aware ban/unban logic; Prysm plans trusted-builder fallback before local building to prevent sybil attacks on P2P bids; document forthcoming — 00:44:11
  • Documentation:
    • ·EIP housekeeping: PRs open to move Glamsterdam EIPs from draft to review; EIP-7723 DFI-removal timing and core-EIP-only staging scope need clarification (PRs #11006, #11853) — 01:01:42
  • Fork Status And Schedule:
    • ·Glamsterdam devnet-6 at ~80% participation; Nethermind storage-read disagreement on revert being investigated — 00:14:09
    • ·devnet-7 target: early next week; Prysm/Nimbus/Lodestar passing tests, Teku updating branch (end of day), Grandine ready in a few days — 00:16:29
    • ·Tony's block-access-list change (EIP-11902) agreed to include in devnet-7; EL test release to be tagged by end of day — 00:21:59
    • ·Public/Mekong-style devnet for Gloas app testing targeted for early August; repricings cited as key driver — 00:39:52
    • ·Hegota non-headliner EIP submission window closes August 6; same process as announced on ACDE — 01:00:58
  • Eip8282 Builder Contracts:
    • ·EIP-8282 builder deposit/exit contracts finalized; audit pending; builder exit queue disabled pre-fork, re-enabled post-fork; EIP language needs updating to reflect CREATE2 deployment — 00:27:44
Action Items
  • •spencer / testing team — Tag and release EL test release including Tony's block-access-list change by end of day — 00:23:25
  • •Staking pools (Lido, Rocket Pool), builders, DVT providers, VC tooling teams — Provide feedback on Beacon API PR #625 (ProduceBlock v4 auth config) urgently — 00:38:47
  • •Cayman Nava — Update EIP-8282 language to reflect CREATE2 deployment method — 00:30:40
PQIPQ Interop #0472026-07-08
Targets
  • •Zeam: new image with spec fixes — today or early tomorrow — 00:06:48
Decisions
  • •PQ Interop call skipped next week; resumes in two weeks — 00:23:47
Highlights
  • Cryptography:
    • ·LeanVM binary fields: >500 XMSS aggregations/second achieved with binary fields — 00:14:49
    • ·BN254 circuit-based approach in progress for comparison with binary field approach — 00:15:16
  • Documentation:
    • ·SSZ spec extracted from lean spec into standalone repo; under review with consensus spec team (Justin Traglia); to be transferred to official Ethereum GitHub org — 00:13:36
  • Client Updates:
    • ·Zeam: new image released; spec fixes pending; new image expected today or tomorrow — 00:06:33
    • ·Ream: all 3 Ethlambda optimizations implemented and running against Ethlambda on devnet; stable with low head/finalization lag — 00:07:12
    • ·Lantern: refactoring underway; was tracking stale lean spec commit — now updated; image cache bug fixed (optimizations were not taking effect) — 00:09:17
    • ·Ethlambda: Grafana metrics made public; block-building fix merged; signature aggregation optimization implemented; passing all Hive spec tests — 00:10:46
    • ·Grandine: implementing Ethlambda option 1 & 2 optimizations; lean spec fixes in progress; new image + shadow image coming soon — 00:12:15
  • Organizational:
    • ·No call next week (travel); sync async; next call in two weeks — 00:23:47
  • Testing Progress:
    • ·Finalization instability persists: bursts of 30–45+ min without finality despite optimizations; root causes are hardware limits and delayed aggregates — 00:19:36
    • ·Anchal proposed additive justification workaround (cumulative vote ranges) to reduce finalization lag; trade-off is high memory use during prolonged non-finality — 00:21:24
    • ·Hetzner doubled prices and denied additional server requests; teams exploring alternative hosting for devnets — 00:18:03
Action Items
  • •All lean client teams — All teams: sync async on optimizations; next sync call in two weeks — 00:23:27
zkEVML1-zkEVM Breakout #0062026-07-08
Targets
  • •Recursive proof chain-prefix PoC spec and implementation — Francesco, coming days — 00:31:52
  • •Next zkEVM release to include both test fixtures and Geth-filled benchmark fixtures — 00:15:08
Decisions
  • •ELF loading standard adopts execute-and-read semantics for executable segments; execute-only interpretation is discouraged — 00:21:31
  • •Direction adopted: Ethereum guest programs must be built with unmodified stock toolchains to limit trusted computing base — 00:24:59
  • •Bump allocator not recommended for production guest programs due to OOM liveness risk at higher gas limits; sophisticated allocators preferred — 00:57:10
Highlights
  • Allocator Safety:
    • ·Bump allocator (BAM) is fastest but causes OOM at current ~0.5 GB limit for high-gas blocks; increasing to 1.5 GB bypasses failures but leaves little headroom — sophisticated allocators (e.g., DLmalloc) recommended for safety — 00:53:07
    • ·OpenVM 2.1 will support 4 GB of guest memory (chat: Yi Sun); most other zkVMs may not exceed 1 GB (Marcin) — 00:57:10
  • Spec And Test Updates:
    • ·zkEVM spec v0.50 released: rebased on Glamsterdam and devnet 6; supports external transition tools (Geth) for benchmark fixture filling — 00:07:21
    • ·SSZ max-length refinements in guest input will change hash tree root calculations — all implementers must review and adjust — 00:08:43
    • ·Hive dashboard now tracks ethrex and Besu execution-witness compliance plus first guest program test runs in a single view — 00:13:11
    • ·Bug fixed in Geth execution-witness generation (merged); benchmark fixtures refilled and looking correct — 00:14:04
  • Evm Formal Specification:
    • ·EVM SAIL spec (evm-sail) achieves 100% EAST test compliance; enables extraction to Lean, Isleris/Iris for binary compliance proofs and RISC-V guest program verification — 00:41:44
    • ·Goal: SAIL spec reaches feature parity with Python execution specs, allowing core devs to contribute directly to a single formal specification — 00:43:01
  • Guest Api Standardization:
    • ·8 guest API standards accepted (ISA I/O, crypto accelerators, termination, memory, static library, linker script); ELF loading and accelerated memory operations open for review — 00:19:13
    • ·ELF loading standard: recommendation is execute-and-read semantics for executable segments; execute-only (Zisk current) is discouraged as no toolchain guarantees instruction-only text sections — 00:20:13
    • ·Precompiles in static libraries must not allocate on the guest heap; a separate isolated scratch region is required — other vendors should audit for this collision — 00:24:14
    • ·Direction flagged: Ethereum guest programs should be built with stock unmodified toolchains to minimize trusted computing base — 00:24:59
  • Sync Protocol And Recursive Proofs:
    • ·Weak-subjectivity sync can require up to 113,000 slots (~26.9 GB of proof content); recursive execution proofs (SSZ Merkle tree or MMR) proposed to enable gossip-based chain-prefix authentication — 00:26:56
    • ·Recursive proof approach would simplify consensus clients by eliminating complex request-response sync; proof-of-concept spec and implementation planned imminently — 00:31:44
  • Prover Infrastructure And Benchmarking:
    • ·EF cluster scalability: GPU proving scales near-linearly from 1 to full machine on large blocks; CPU-bound bottleneck observed between 2 and 4 GPUs — 00:34:16
    • ·OOM kills still observed on mainnet EST 6M-gas blocks; root cause under investigation — 00:35:04
    • ·New ZK-Boost release adapts to current compatible input format; proof-request and verification APIs updated to require chain config as public input — 00:35:58
Action Items
  • •All guest program implementers — Review zkEVM spec v0.50 SSZ max-length changes and update hash tree root calculations accordingly — 00:08:43
  • •Nethermind and other EL teams — Add Nethermind (and other clients) to execution-witness Hive dashboard by adding a branch entry to the dashboard repo JSON — 00:18:29
  • •zkVM vendors — Audit precompile static libraries for guest-heap allocation collisions; add isolated scratch region if affected — 00:24:14
FCRFast Confirmation Rule #0102026-07-07
Targets
  • •Cross-client FCR compatibility testing to be coordinated on next FCR breakout call (~2 weeks) — 00:27:13
  • •FCR paper publication pending appendix clarifying pseudocode vs. Python spec differences — 00:31:53
Decisions
  • •FCR must not trigger during node sync; activation deferred until node is fully synced with head (agreed with Nimbus and Lodestar) — 00:14:27
Highlights
  • Client Updates:
    • ·Grandine: FCR-specific tests passing; PR pending review from Thomas — 00:05:00
    • ·Lodestar: FCR shipped in v1.44.0 (experimental flag); epoch-boundary reset fix deployed Friday, no resets since — 00:06:05
    • ·Lighthouse: regression from prior call resolved; fix in progress, mainnet runs show no resets — 00:16:42
    • ·Teku: production-ready FCR implementation underway; Prysm blocked on human review — 00:17:44
  • Research Updates:
    • ·Proof review complete; pseudocode differences from Python spec to be addressed in paper appendix — last blocker before publication — 00:31:02
    • ·Late-block recovery optimization (~1–1.5% more single-slot confirmations, prototyped in Teku) under consideration; proof work costly and may conflict with Casper research — 00:32:23
  • Spec And Testing:
    • ·FCR manual test suite complete; all planned cases covered (PR merged) — 00:28:21
    • ·Mainnet-config test vector generation took ~3 hours per test; minimal preset deemed sufficient — 00:29:02
    • ·FCR metrics PR merged; teams encouraged to implement across all clients — 00:30:10
  • Fcr Behavior And Gloas:
    • ·Decision: FCR should not trigger during node sync; only activate once fully caught up with head — 00:14:27
    • ·FCR on Gloas: confirmed payload from two slots prior (not one) due to Gloas timing change — 00:19:35
    • ·Some clients (e.g., Nimbus) enable FCR by default; others require a feature flag — 00:22:10
    • ·Barnabas: FCR should be tested on Gloas devnet 7; Dora visualization of FCR event stream planned — 00:23:52
Action Items
  • •Nazar Hussain (Lodestar) — Nazar to share epoch-boundary reset analysis and fix details in FCR Telegram group — 00:07:46
  • •Mikhail Kalinin — Mikhail to share Teku late-block optimization code reference in FCR Telegram group — 00:35:05
ACDTAllCoreDevs — Testing #0862026-07-06
Targets
  • •Wednesday July 9 - Glamsterdam devnet-7 launch — 00:20:18
  • •Friday - SSZ Engine API breakout call — 00:26:59
Decisions
  • •Glamsterdam devnet-7 to be the final devnet; mild spec freeze after launch — 00:21:51
  • •Minor parameter-only spec changes (e.g., gas cost tweaks for EIP-8038/2780) acceptable post-freeze; structural changes are not — 00:22:43
Highlights
  • Organizational:
    • ·SSZ Engine API breakout call scheduled for this Friday — 00:26:59
    • ·Breakout room recordings to be captured via OBS; EL session by Pooja, CL session by Justin — 00:27:18
  • Testing Progress:
    • ·Glamsterdam devnet-6 had Besu instability; most nodes recovered, some Teku/Erigon nodes still unhappy — 00:09:01
    • ·Prysm sending multiple new payloads without FCU caused Besu state inconsistency; Prysm will revert, Besu fix likely to be reverted — 00:09:47
    • ·Nimbus fork-choice issue identified with known fix in progress; Nimbus nodes self-building instead of using remote builder — 00:16:33
    • ·All clients now onboarded to devnet-6 — 00:19:56
  • Fork Status And Schedule:
    • ·Glamsterdam devnet-7 targeted for Wednesday; EL spec changes (EIP-2780, EIP-8037, EIP-8282) plus CL breaking changes (stable containers, ~5 others) expected — 00:20:04
    • ·DevNet-7 intended as final devnet; mild spec freeze after launch — 00:21:55
    • ·CL alpha-12 release and updated EL execution-specs required before devnet-7 launch; target today or Wednesday — 00:24:52
Action Items
  • •Besu (Karim) — Revert Besu fix for Prysm FCU behavior; re-investigate if issues persist — 00:09:47
  • •EL teams (Spencer, Mario) — Resolve remaining EL spec changes (EIP-2780 floor gas input, EIP-8037, EIP-8282) in EL breakout; release updated execution-specs by Wednesday — 00:23:31
ACDEAllCoreDevs — Execution #2402026-07-02
Targets
  • •All devnet-7 spec PRs merged by end of week (July 4, 2026) — 00:16:24
  • •Glamsterdam devnet-7 launch targeting week of July 7 (Wednesday ~July 9), pending Alpha 12 release with EIP-7688 and deadline changes — 00:41:14
Decisions
  • •Felix's disable-deposits feature for the ePBS builder deposit contract (sys-asm PR #49) accepted for devnet-7 — 00:28:50
  • •ePBS slot deadlines for devnet-7: attestation = 3s, payload = 6s, PTC = 9s; to be confirmed at ACDT — 00:40:44
  • •Hegota EIP proposal deadline set to August 6, 2026 — 00:44:23
  • •PFI for Hegota: EIP-8250 (Key Nonces), EIP-8272 (Recent Routes), EIP-7862 (Delayed State Root), EIP-8146 (BAL Sidecars), EIP-8298 (SETCODEFROM opcode) — 01:14:59
Highlights
  • Organizational:
    • ·Hegota EIP proposal deadline set to August 6, 2026 (5 weeks, accounting for ACDC offset) — 00:44:23
    • ·Pooja: Meta EIP-7773 out of sync; EIP-7610 confirmed in Glamsterdam (SFI); EIP-8282 HTML fix needed before merge; all Glamsterdam EIP authors should move drafts to Review status — 01:15:46
  • Eip Proposals Hegota:
    • ·EIP-8250 (Key Nonces): multi-lane nonce system via nullifier-keyed nonce pairs in VUBS system contract; enables trustless private tx senders — 00:45:42
    • ·EIP-8272 (Recent Routes): standardized per-block Merkle root buffer system contract in VUBS; enables FOCIL inclusion guarantees for ZK privacy proofs — 00:55:30
    • ·EIP-7862 (Delayed State Root): header carries pre-state root instead of post-state root; reduces builder/prover hashing load across thousands of candidate blocks — 01:02:50
    • ·EIP-8146 (BAL Sidecars): BAL gossiped separately from execution payload; allows EL prefetching before transactions arrive, improving scaling — 01:05:25
    • ·EIP-8298 (SETCODEFROM opcode): copies code hash from existing on-chain contract to current address; reduces duplicate deployment cost vs. CREATE2 or proxies — 01:11:04
  • Fork Status And Schedule:
    • ·Glamsterdam devnet-7 spec finalization primary focus; target launch next week (week of July 7) — 00:06:14
    • ·No new EL EIPs for devnet-7; spec update to follow call; aim to beat ACDT if clients create branches — 00:15:44
    • ·Repricing numbers (EIP-8038, EIP-2780) treated as stable for devnet-7; final confirmation pending full benchmark suite results by next ACDE — 00:29:44
  • Glamsterdam Devnet7 Open Items:
    • ·EIP-8038: additional pre-access check before slot DB read; behavioral spec change needed in EIP or EIP-7928; PR #11854 opened — 00:07:16
    • ·EIP-8037 / EIP-2780 intrinsic gas: Dragan's PR #11844 supersedes PRs #11778 and #3045; clients to review Discord thread before ACDT — 00:11:44
    • ·Felix's deposit contract disable-deposits feature (sys-asm PR #49) accepted for devnet-7; immutable-only option rejected — 00:28:50
    • ·ePBS deadlines for devnet-7 set to 3s attestation / 6s payload / 9s PTC; PR to consensus-specs to be opened and finalized at ACDT Monday — 00:40:44
Action Items
  • •All EL client teams — Review Dragan's EIP-2780 intrinsic gas PR #11844 and weigh in on Discord thread before ACDT — 00:11:44
  • •Justin Traglia / Potuz — Open consensus-specs PR for 3s/6s/9s ePBS deadlines; finalize at ACDT Monday — 00:41:08
  • •Cayman (EIP-8282 author) — Fix HTML issue on EIP-8282 so PR can merge and Meta EIP PR can follow — 01:17:36
PQIPQ Interop #0462026-07-01
Targets
  • •Zeam: shadow sim analysis with 16–32 node network + Camille's visualization tool — presented next call — 00:26:13
  • •Zeam two-level aggregation proposal: tested and results shared by next call — 00:46:59
Decisions
  • •Spec to remain stable (no new features); only bug fixes and performance improvements targeting DevNet 5 readiness — 00:41:03
  • •Continue long-running multi-client devnets (targeting week+ duration) while testing Zeam and Ethlambda aggregation optimizations in coming weeks — 00:50:37
Highlights
  • Devnet Status:
    • ·6-client public devnet (32 nodes, 12h run) achieved consistent justification; finality gaps up to 45 min due to divergent recursive aggregation strategies across clients — 00:49:10
    • ·12 Ethlambda + 12 Ream 24-validator devnet finalized up to 90,000 slots; ~30-slot finalization lag observed — 00:26:47
    • ·Ream ARM compatibility issue and Zeam/Lantern Ziglip P2P interop bug identified; fix applied, devnet restart underway — 00:49:55
  • Client Updates:
    • ·Lantern: early block-build optimization (build in final interval of previous slot) live in public image; shadow simulator image compatible with Camille's lean shadow fuzzer — 00:27:55
    • ·Ethlambda: history pruning reworked (statediff + snapshots every 1,000 blocks); P2P ported to Rust; proposal proof computation disabled to reduce latency — 00:29:01
    • ·Gean: fixed configurable attestation committee count rejection bug; spec synced to lean spec head including attestation source and vote filtering changes — 00:30:33
  • Fast Finalization:
    • ·Anshal proposes implicit vote propagation: validators who voted for block B implicitly voted for ancestor A; modifies process_attestations to credit ancestor targets, reducing finalization gaps — 00:35:41
    • ·Memory tradeoff: accumulating implicit votes scales with justifiable slots (bounded ~O(sqrt)) × validator count; block size impact needs evaluation — 00:37:48
  • Aggregation Proposals:
    • ·Zeam proposes two-level aggregation: Level 1 aggregates raw XMSS only (for safe-target calc); Level 2 aids proposers; removes Type 1 recursive aggregation from proposal pipeline — 00:17:50
    • ·Zeam proposal increases slot intervals from 5 to 8 (×0.8s = 6.4s slots); 4 intervals reserved for block building and Type 2 aggregation — 00:21:30
    • ·Ethlambda doc: first two optimizations are client-side only; third changes SignedBlock format and requires spec update if adopted; achieved 200ms publish time with 3 attestations — 00:47:16
  • Cryptography Binary Fields:
    • ·New 'Flock' paper (Starkware + Benedict Bunz/Espresso): binary field proving system, ~600 Blake3 hashes/sec proved, ~2× slowdown vs Poseidon; candidate to replace Poseidon entirely — 00:43:07
    • ·Thomas working on XMSS circuit throughput in Binius64 repo; Emil working on LeanVM-b (LeanVM with binary fields + Blake3) — 00:44:58
Action Items
  • •Eric (kolby's team) — Investigate and update Hive — currently failing due to old spec version — 00:51:23
  • •Ream team — Confirm availability of official Ream ARM-compatible image for multi-client devnet — 00:50:10
P2PP2P Networking #0032026-07-01
Decisions
  • •Gloas partial column changes to be tested on Gloas devnet 6, not BlobDevNet 0 — 00:08:32
Highlights
  • Client Updates:
    • ·Lighthouse shipped partial columns enabled by default on Hoodi and Sepolia; ~2.5/6 mesh peers upgraded; bandwidth down to 2 MiB/s, DA latency down to ~1.15s avg — 00:03:06
    • ·Prysm: Fulu partial column changes merged to release branch; Gloas partial column changes in review this week; targeting Gloas devnet 6 for testing — 00:11:00
    • ·Teku actively working on PeerDAS with several fix releases; PeerDAS likely in production — 00:19:08
  • Testing Progress:
    • ·Plan to test Gloas partial column changes on Gloas devnet 6 rather than BlobDevNet 0 — 00:07:53
    • ·Sparse blob pool merged in Glamsterdam devnets (Prysm); no EL client has implemented FCU v4 / GetBlobs v4 yet, limiting effective testing — 00:14:35
    • ·Nethermind has a known bug in GetBlobsV4 (issue #12147); Erigon sparse blob pool PR is open for review and expected to ship soon — 00:18:15
Action Items
  • •Bosul Mun — Report Nethermind GetBlobsV4 bug to sparse blob pool channel with FLCL tagged — 00:19:16
FOCILFOCIL Breakout #0372026-06-30
Targets
  • •Engine API PR #609 merge — week of June 30 or following week — 00:09:55
  • •FOCIL Breakout #38 — July 21, 2026 — 00:48:39
Decisions
  • •Payload attributes SSE event: tentatively adopt option 3 — add IL bits as a top-level field; revisit if Engine API changes direction — 00:14:42
  • •IL bit list restored to block container but NOT enforced in fork choice for now; fork choice treatment to be determined after further design work — 00:36:23
Highlights
  • Spec Updates:
    • ·Engine API PR #609 (payload status V2): replaces latest-IL-satisfied hash with a Boolean IL-satisfied flag; EL must retain ILs for accepted payloads to support branch switching; near-final, targeting merge this week or next — 00:07:40
    • ·Consensus spec will add comment clarifying that is_payload_il_satisfied returns true for non-validated payloads; small change, Jihoon to add — 00:10:58
    • ·Payload attributes SSE event: three options discussed for exposing IL bit list to builders; tentatively going with option 3 (add inclusion-list bits as top-level field in the event) as least-invasive CL-only change — 00:11:26
    • ·IL bit list being restored to block container (previously removed); fork choice enforcement deferred pending design exploration of two options: (1) reorg the block, or (2) suppress trustless payment without reorging the block — 00:15:03
  • Client Updates:
    • ·Teku integrated latest Glamsterdam changes into FOCIL branch but couldn't interop with Lodestar due to builder execution requests; old docker image left in place — 00:05:21
    • ·Lighthouse and ethrex both need to rebase on Glamsterdam devnet 6; Lodestar PR #9541 pending merge to unblock rebase — 00:06:06
  • Organizational:
    • ·Next FOCIL breakout pushed one week to July 21 (Jihoon OOO around July 14) — 00:48:39
  • Protocol Design:
    • ·Bit list rationale: prevents honest builders from being penalized when they missed an IL due to network conditions under trustless payment; also aligns proposer incentive to select non-censoring payloads — 00:16:07
    • ·No consensus yet on fork choice enforcement of bit list; near-term plan is proposer SHOULD pick a bit list that is a superset of their local IL view, but this is not checked in fork choice — 00:32:12
Action Items
  • •Jihoon — Merge engine API PR #609 (payload status V2); then source execution spec test resources from Stihl — 00:09:55
  • •Jihoon — Explore candidate spec implementations for bit list in fork choice; present options at next breakout — 00:37:06
1-OFFSubroutines for the EVM #12026-06-30
Decisions
  • •Subroutines EIP (EIP-8173) is PFI for Hegota; Greg to identify current CFI process owners and pursue next step — 00:49:14
Highlights
  • Documentation:
    • ·EIP needs clarification: behavior of RETURNSUB with empty return stack in non-validated (legacy) code; Ben Adams offered to open a PR — 00:47:21
    • ·EIP-8173 rollup/ZK advantages section flagged as uncertain; Vyper validation contract (AI-generated) needs review by a Vyper reader — 00:51:39
  • Organizational:
    • ·Related PR #11800 (set-code-from) proposed: lets a new contract inherit an existing contract's code hash, enabling on-chain libraries without delegatecall overhead — 01:00:55
  • Eip Proposals Hegota:
    • ·Greg Colvin presenting subroutines EIP (CALLSUB/RETURNSUB/ENTERSUB): adds return stack, minimal client debt; opcodes backwards-compatible outside validated magic-header contracts — 00:06:50
    • ·Validation runs once at create time via on-chain Vyper contract; replaces per-call jumpdest analysis; one-pass algorithm on 64KB contracts is negligible overhead — 00:09:39
    • ·Magic header points to on-chain validation function, enabling simple client interpreters without bespoke validation logic; validation algorithm is upgradeable over time — 00:19:32
    • ·Validated contracts enable one-pass CFG/AST extraction and static analysis; key downstream benefit for auditors and formal verification tools that currently cannot handle dynamic jumps — 00:36:58
    • ·EIP currently PFI for Hegota; Greg seeking path to CFI and unsure of current process owners after EF departures — 00:49:14
Action Items
  • •Ben Adams — Open PR clarifying RETURNSUB/CALLSUB behavior in non-validated legacy code (treat as jump per yellow paper rules) — 00:47:21
  • •Kev (async, via note-taker summary) — Review EIP-8173 Vyper validation contract and ZK/rollup advantages section for correctness — 00:51:39
  • •Greg Colvin — Contact EELS/steel group to integrate validation algorithm into executable spec — 00:53:20
ACDTAllCoreDevs — Testing #0852026-06-29
Targets
  • •ACDE this week: finalize devnet-7 EL scope — 00:33:50
  • •ACDC next week: finalize devnet-7 CL scope — 00:34:02
Decisions
  • •EIP-8282 builder deposit contract: keep static constants (no dynamic params); choose values carefully; Felix adds disable-switch for future upgrades — 00:30:26
  • •glamsterdam-devnet-7 adds no new EIPs; EL scope limited to refinements of existing EIPs — 00:33:50
Highlights
  • Testing Progress:
    • ·glamsterdam-devnet-6 launched June 25 with Gloas fork; consolidation testing pending this week — 00:08:26
    • ·Prysm nodes offline; potuz suspects EL-side bug (Nethermind invalid block, ethrex DB issue) rather than Prysm fault — 00:08:51
    • ·Nethermind bug found via execution fixtures; fix in progress; Besu also offline — 00:09:27
    • ·Erigon branch expected tomorrow; Reth branch exists but not yet joined; Grandine joining this week — 00:11:44
  • Fork Status And Schedule:
    • ·glamsterdam-devnet-7 scope: EIP-7688 (forward-compatible SSZ data structures) on CL side; no new EIPs on EL, only refinements — 00:31:05
    • ·Open EL question for devnet-7: how to meter authorizations (EIP-8037 state growth + EIP-2780 transfer) — 00:31:56
    • ·Target: finalize devnet-7 EL scope at this week's ACDE; CL scope at next week's ACDC — 00:33:50
  • Eip 8282 Builder Deposit Contract:
    • ·Per-tx fee merged to sys-asm; bytecode now committed to repo for easy devnet genesis use — 00:13:55
    • ·Nico proposes lowering builder deposit params: target=8, max=64 (from 32/256) to limit validator sweep DOS risk — 00:18:32
    • ·Debate: dynamic params via calldata (PK's PR) vs. deploy new contract at next fork vs. keep constants fixed — 00:20:03
    • ·potuz: no builder churn expected; deploying new contract at next fork is acceptable — 00:23:57
Action Items
  • •Felix (Geth) — Felix to add disable-switch to EIP-8282 deposit contract (easy, low-risk future-proofing) — 00:20:03
RPCRPC Standards #0292026-06-29
Decisions
  • •Glamsterdam/Amsterdam spec changes without tests will use a tracking issue or long-running branch; tests backfilled once fork spec is final — 00:27:52
  • •Byte-type regex PR (#81415) approved to merge — restricting to lowercase aligns with all other byte types in spec — 00:39:32
  • •Error code rework still in progress; no merge of current PR until Sina's updated positive-number proposal is ready; broader ACD discussion planned — 01:00:07
Highlights
  • Pr Reviews:
    • ·execution-apis PR #814 (eth_getRawTransaction endpoints): all clients merged except ethrex (PR approved, not merged); CI spell-check failure is upstream noise — rerun to green, ready to merge — 00:23:13
    • ·PR adding slot number to block header schema (Glamsterdam): marked for Amsterdam label; needs tests deferred until fork spec is final — 00:24:43
    • ·PR adding 3 missing eth_getRaw* endpoints (by hash/block): all EL clients already implement these; blocked on Go Ethereum PR #35227 merge + test regeneration — 00:33:28
    • ·Regex fix for single-byte type (PR #81415): change to allow single zero in decimal numbers is correct; uppercase hex oddity in byte type resolved — approved to merge — 00:37:22
  • Error Codes:
    • ·New error code direction: define all new codes as strictly positive integers; positive = reliable/new, negative = legacy/fuzzy; Go Ethereum considering a legacy-mode mapper for transition period — 00:55:58
    • ·Sina's updated proposal pending; grouping debate: user-friendly categories (gas errors, nonce errors) vs. implementation-layer categories (execution, simulation, validation); to be brought to ACD for broader input — 01:00:16
  • Debug Execution Witness:
    • ·debug_executionWitness has no cross-client spec agreement: Geth uses JSON header with empty key; Reth/Nethermind/Erigon use RLP bytes with populated key; Geth and Reth also expose a separate by-hash method — needs spec decision — 01:06:07
Action Items
  • •Geth (Felix) — Merge Go Ethereum PR #35227, cut new release, regenerate execution-apis I/O tests for eth_getRaw* PR — 00:33:52
  • •Boma — Open a tracked issue for debug_executionWitness wire format disagreement; tag relevant stakeholders (Kev) — 01:08:45
SSZSSZ Engine API #0012026-06-26
Targets
  • •SSZ Engine API enabled on Glamsterdam devnets — as soon as clients default-enable and negotiate — 00:29:50
Decisions
  • •Both JSON-RPC and SSZ Engine API endpoints to coexist; no coordinated rollout required — 00:13:39
  • •SSZ Engine API made mandatory at Hegota; optional with flag until then — 00:16:27
  • •newPayloadWithWitness unified path adopted as default; fork segment removed from URL — 00:22:43
  • •Keep current SSZ types (no EIP-7688 stable containers) for now; reconsider once 7688 is SFI'd — 00:33:23
  • •Breakout call cadence set to bi-weekly — 00:41:56
Highlights
  • Organizational:
    • ·SSZ Engine API breakout cadence changed from weekly to bi-weekly; next call TBD — 00:41:56
  • Testing And Devnets:
    • ·SSZ static test vectors for Engine API containers drafted; full random values for now, hypothesis-based valid-value tests to follow — 00:24:04
    • ·No dedicated devnet needed; SSZ Engine API to be added to Glamsterdam devnets once clients are ready with default-enabled negotiation — 00:29:46
  • Ssz Engine Api Status:
    • ·Consensus: keep JSON-RPC and SSZ channels open simultaneously; clients roll out on own schedule with optional flag — 00:13:39
    • ·Prysm already implements SSZ Engine API with JSON-RPC fallback; Erigon interop confirmed working; ethrex and Nethermind also ready — 00:14:47
    • ·SSZ Engine API to be made mandatory at Hegota; transition window between Glamsterdam and Hegota — 00:16:27
    • ·newPayloadWithWitness path to be unified under /engine/v{1|2}/{fork}/payloads/witness as POST call; fork to be moved out of URL — 00:20:23
  • Stable Containers 7688:
    • ·EIP-7688 stable containers/progressive lists: agreed to keep current types for now and revisit after 7688 is SFI'd — 00:30:44
    • ·Dustin notes progressive lists avoid arbitrary limit mismatches that force new API versions; risk of '7688 too late' pattern flagged — 00:35:41
Action Items
  • •Marius / spec maintainers — Update execution-apis PR #793 (single source of truth for SSZ Engine API spec) with decisions from this call — 00:39:07
  • •CL/EL teams — Discuss Jacek's top-up sync semantic change requests on PR #793 in a future call — 00:39:51
ACDCAllCoreDevs — Consensus #1812026-06-25
Targets
  • •glamsterdam-devnet-7 launch — ~2–3 weeks out (mid-July 2026) — 00:10:42
  • •EIP-8282 external audit — post devnet-7, ~end of July 2026 — 00:47:03
Decisions
  • •EIP-7688 (progressive containers) targeted for devnet-7; not DFI'd; revisit if devnet-6 instability warrants it — 00:34:04
  • •EIP-8080 (consolidation-based exits) DFI'd from Glamsterdam; authors may re-propose for Hegota — 00:36:07
  • •ePBS circuit breakers should track missing payloads (not beacon blocks); no standardization required, client-specific implementations acceptable — 00:17:01
Highlights
  • Client Updates:
    • ·ePBS circuit breakers: Prysm uses consensus-block-based breaker (acknowledged as incorrect for ePBS); needs updating to track missing payloads, not beacon blocks — 00:14:46
  • Organizational:
    • ·Lucid (encrypted mempool EIP-8184) seeking CL spec guidance; Justin Traglia volunteered to help Besu team — 00:50:27
    • ·Glamsterdam mascot vote open; voting closes July 8 — 00:51:37
  • Testing Progress:
    • ·Pre-fork slashing test planned on devnet-6 just before Gloas fork activation — 00:09:20
    • ·EIP-8282 contract constants under discussion: target=8, max=64 preferred over current 32/256; reduces builder withdrawability delay — 00:44:04
  • Fork Status And Schedule:
    • ·glamsterdam-devnet-6 launched hours ago; Gloas fork in ~40 min; EL: Besu, ethrex, Geth; CL: all except Teku — 00:07:25
    • ·glamsterdam-devnet-5 stable for 3 weeks; Lighthouse range-sync bug outstanding; Prysm peering bug resolved — 00:07:33
    • ·Spec bug (consensus-specs #5399) confirmed valid by Terrence; patch targeting devnet-7 — 00:10:24
  • Eip Proposals Glamsterdam:
    • ·EIP-7688 (progressive containers): 3 clients yes (Nimbus, Lodestar, Lighthouse), 3 maybe (Prysm, Teku, Grandine); targeting devnet-7; DFI deferred — 00:26:52
    • ·EIP-8080 (consolidation exit mechanism): DFI'd; authors encouraged to re-propose for Hegota — 00:35:14
    • ·EIP-8282 (builder execution requests): old contract on devnet-6 for workflow testing; updated contract (fee-per-enqueue) targets devnet-7; external audit post-devnet-7 (~end of July) — 00:42:34
Action Items
  • •All CL client teams — Review and approve Beacon API PRs (608, 580, 606, 621) by ACDT — 00:19:28
  • •Nico Flaig / EIP-8282 authors — Open PR against sys-asm repo for EIP-8282 contract constants (target=8, max=64); signal when contract is final for audit scheduling — 00:47:00
PQIPQ Interop #0452026-06-24
Targets
  • •Zeam: begin multi-client DevNets by end of this week — 00:19:34
  • •Goal: run a month-long stable DevNet with 100+ (ideally 1000+) validators before end of year — 00:35:14
Decisions
  • •Zeam (Anshal) will PR to revert Ethlambda's earlier vote-packing spec change, as it is now redundant following the latest-justified store PR merge — 00:20:43
  • •Increase DevNet 5 slot time in the lean spec (currently 4s) to resolve proof aggregation bottleneck on commodity hardware; exact value TBD — 00:48:27
Highlights
  • Client Updates:
    • ·Zeam: 32-node, 4-subnet all-Zeam Shadow network running to finality; QUIC P2P multi-threaded, stabilization expected in 1-2 days — 00:16:31
    • ·Ream: interoping successfully with Ethlambda on one subnet; plan to add Zeam, Lantern, and Grandine for 24-validator DevNet 5 runs — 00:23:30
    • ·Lantern: avg Type 2 proof generation ~2.8s on Xeon/8-core; finality gaps when block building exceeds 10s; adding subnets and clients next — 00:24:09
    • ·Ethlambda: updated attestations to use current head's latest justified as source; added flag to disable Syngate mechanism that caused non-finality; working on pre-build optimization — 00:26:12
    • ·Gean: stable multi-client runs with no SSZ regressions; Shadow Network Simulator integration in progress — 00:27:58
  • Testing Progress:
    • ·Ethlambda: finality lags observed (~30 slots at a time) with 16 nodes on a 32-thread machine; CPU is the primary bottleneck — 00:40:28
    • ·Ethlambda confirmed Shadow-compatible; Zeam will begin interop Shadow sims with Ethlambda before next call — 00:36:33
    • ·Lantern confirmed its new libp2p library is Shadow-compatible; will submit a PR for Shadow simulator support — 00:40:30
    • ·Root cause of finality lag identified as recursive proof aggregation during block proposal, not XMSS row signatures — 00:42:04
  • Spec And Cryptography:
    • ·Lean spec cleanup complete; no major changes expected; internal EF spec review meeting planned for next week — 00:30:04
    • ·Zeam to PR revert of Ethlambda's earlier vote-packing optimization (now redundant after latest-justified store PR merge) — 00:30:54
    • ·EF team exploring binary fields as proving system to potentially replace Poseidon in the future — 00:31:09
    • ·Proposed path: increase slot time in spec (from 4s to 6-8s) to unblock scaling on commodity hardware; revisit in a few months as performance improves — 00:48:27
Action Items
  • •All client teams — Post a DevNet 5 issues list to the DevNet 5 channel: include interop blockers, finality problems, validator counts, and proof aggregation status — 00:49:12
  • •Lantern, Ethlambda, other client teams — Client teams wishing to join Shadow sims should implement sleep/simulated-time config at heavy computation points; contact Zeam (Parthasarathy/Kai) for config details — 00:39:00
PQTSPQ Transaction Signatures #0112026-06-24
Decisions
  • •Priority: proving security assumptions (ground truth strength) ranked higher than completing Yul→bytecode verification gap — 00:51:07
Highlights
  • Formal Verification Progress:
    • ·Ricardo (EPFL student) formally verified Riva Labs' FORS+ verifier contract in Lean4 via EVMYulLean (Nethermind tool), proving correct address recovery for all possible inputs — 00:18:39
    • ·Proof runs on optimized Yul IR, not EVM bytecode — Solidity compiler backend (Yul→bytecode) remains trusted but unverified — 00:21:39
    • ·AI used to write Lean4 proofs and reference model; correctness relies on Lean kernel, not AI output. Riva Labs' reference Lean model also AI-assisted from Solidity + FORS+ context — 00:26:46
    • ·Verity team reportedly achieved full formal refinement of SPHINCS+; separate effort to formally verify SLH-DSA wallet integration is in progress — 00:44:55
  • Verification Scope And Limitations:
    • ·Contract proves which address signed — validity check (recovered address == expected address) must be done by the calling contract; unforgeability not claimed — 00:20:09
    • ·keccak assumed correct (long-standing EVM primitive); not formally verified in this work — 00:34:00
    • ·Ground truth risk: Lean reference model derived from Solidity+AI; manual review needed to confirm it matches NIST/FIPS specification intent — 00:35:09
    • ·Yoichi: security proof anchoring recover function to hash pre-image hardness would strengthen confidence in Lean spec independent of PDF comparison — 00:46:19
    • ·Benedikt: CryptHOL framework (Lean4) enables formalizing asymptotic and concrete security proofs for hash-based signatures; security definition itself still needs human review — 00:47:21
Action Items
  • •Ricardo Perello / Riva Labs — Extend verification to cover EVM bytecode (not just optimized Yul), and add security reduction proof (breaking FORS+ implies breaking keccak pre-image) — 00:50:24
ETMEncrypt The Mempool #0062026-06-24
Decisions
  • •Key release fee to be treated as separate from gas in the spec; wallet-layer responsibility for fee accounting — 00:23:31
  • •Probabilistic front-running optionality accepted as out-of-scope for Lucid; no protocol-level fix possible without threshold encryption — 00:33:03
  • •Optionality deal-breaker question to be escalated to ACD for CFI determination — 00:36:39
Highlights
  • Kurtosis Devenv:
    • ·Kurtosis sandwich-attack demo stack built against Fusaka; Glamsterdam/ePBS not yet stable enough to target — 00:16:05
  • Cl Spec Progress:
    • ·Matt from Lodestar interested in joining; targeting next call in two weeks — 00:02:41
    • ·Lucid PM repo created (jflo/lucid-pm) to track missing CL specs, PRs, and implementation gaps — 00:03:12
    • ·Boma to draft CL spec skeleton: SSZ containers, inclusion list, payload bid extension, LucidKey votes — standalone pieces only, pending EL decryption flow stabilization — 00:04:36
    • ·Erigon (Mark) willing to review CL spec drafts and attempt implementation given Erigon 3 runs both EL and CL — 00:09:38
  • Key Release Fee Design:
    • ·Key publication fee mechanics unclear in spec: fee reduces gas headroom but is not itself a gas fee; needs cleaner separation and documentation — 00:19:08
    • ·Consensus: treat key release fee as a separate object from gas; wallets responsible for accounting, may require new RPC for estimation — 00:23:31
    • ·Key release fee is orthogonal to bundling; factoring out bundles to a separate EIP won't simplify key publication fee handling — 00:29:51
  • Optionality And Lucid Design:
    • ·Probabilistic front-running via self-key withholding is unsolvable without threshold encryption; top-of-block fees and bundling are the only current mitigations — 00:33:03
    • ·Builder optionality (via FOCIL-style PTC vote wiggle room) is partially addressable: penalizing equivocating PTC votes would reduce exploitability — 00:37:50
    • ·Whether optionality is a deal-breaker for Lucid CFI is a question that must go to ACD — 00:36:39
    • ·Lucid cannot be upgraded to threshold encryption if/when it matures — a new scheme would be required from scratch — 00:48:58
  • Threshold Encryption Readiness:
    • ·No threshold encryption scheme currently meets Ethereum's requirements: post-quantum security, low setup cost, scalable committee size, bulk decryption support — 00:51:22
    • ·Ethereum Foundation cryptography team monitoring threshold encryption research; Benedict's requirements list exists and will be shared — 00:53:21
Action Items
  • •Loring + CL contributors — Explore up to $10K ShutterDAO0X36 bounty for CL spec work; need help defining success criteria — 00:13:09
  • •Justin Florentine — Rewrite key publication fee section of EIP-8184 for clarity; coordinate with Anders — 00:30:32
  • •Justin Florentine — Discuss builder optionality and PTC equivocation penalties with Potuz — 00:43:19
  • •Gottfried Herold — Share Benedict's Ethereum threshold encryption requirements list in Telegram — 00:53:21
FCRFast Confirmation Rule #0092026-06-23
Targets
  • •Lodestar public FCR release — this week or start of next week — 00:06:11
  • •FCR edge case tests PR — tomorrow (June 24, 2026) — 00:17:25
  • •FCR research paper publication — this week — 00:19:57
Decisions
  • •EL block tag for FCR will reuse 'safe'; introducing a new tag requires hard fork coordination and is deferred until after Glamsterdam — 00:28:02
Highlights
  • Client Updates:
    • ·Lodestar: FCR deployed to test fleet and RC; public release + blog post expected this week or early next week — 00:05:51
    • ·Lighthouse: investigating likely regression causing reversions to finality; test coverage needed for this case — 00:11:54
    • ·Lodestar passing FCR spec tests for Gloas since alpha.11 (chat) — 00:13:45
    • ·Grandine: metrics PR awaiting maintainer review; blocked on Samas or another core maintainer to merge — 00:12:05
  • Api And Metrics:
    • ·beacon-APIs PR #616 (adds current_slot to event stream) merged — 00:18:41
    • ·beacon-metrics PR #22 (FCR metrics) approved; awaiting merge from Panda/Barnabas — 00:18:57
    • ·Lodestar internal metric shows 3 FCR resets in last 7 days on Nico's node; cause uninvestigated — 00:20:33
  • Research Updates:
    • ·FCR research paper publication expected this week; no blockers identified — 00:19:54
    • ·EL 'safe' block tag discussion: introducing a new fast-confirm tag would require hard fork coordination between CL and EL; deferred until after Glamsterdam — 00:27:41
  • Testing Progress:
    • ·New consensus-specs PR enables FCR tests for loss/hazard cases and disables BLS for stable, fork-independent shuffling — 00:15:12
    • ·Edge case tests in progress; PR expected tomorrow — will complete initial FCR test suite — 00:17:18
Action Items
  • •Mikhail Kalinin — Reach out to Panda/Barnabas to merge beacon-metrics PR #22 — 00:19:06
  • •Nazar Hussain — Investigate cause of 3 FCR resets on Lodestar node; add debug logging for fallback-to-finality events — 00:23:09
  • •Mikhail Kalinin — Investigate current usage of the EL 'safe' block tag by RPC providers — 00:31:13
ACDTAllCoreDevs — Testing #0842026-06-22
Targets
  • •Glamsterdam devnet-6 launch: within 1-2 days (targeting today if 2+ additional ELs ready) — 00:11:13
  • •REST SSZ Engine API breakout call: Friday at 1300 UTC — 00:23:24
Decisions
  • •No decision yet on EIP-7688 for devnet-7; defer to ACDC after observing devnet-6 stability — 00:20:12
Highlights
  • Organizational:
    • ·ACDC this week at 1400 UTC (original time); last week's earlier slot was a one-off — 00:23:12
    • ·New REST SSZ Engine API breakout call this Friday at 1300 UTC — 00:23:24
  • Testing Progress:
    • ·Glamsterdam devnet-5 running; most Prysm nodes offline, Teku and Reth also down — 00:10:48
    • ·devnet-6 targeting launch in 1-2 days; requires at least 3 ELs (ethrex confirmed; Nimbus/Lighthouse branches also now available) — 00:11:13
    • ·glamsterdam-devnet@v6.0.0 EL test release published; another release expected Tuesday with EIP-8037/8038 coverage — 00:13:20
    • ·EIP-8045 slashing-before-fork testing flagged as needed for devnet-6 — 00:13:40
  • Epbs Eip7688 Devnet7 Scope:
    • ·EIP-7688 (SSZ stable containers) proposed for devnet-7; Lodestar, Lighthouse, Nimbus ready today; Teku has prototype needing ~2 weeks to update — 00:13:55
    • ·Arguments for inclusion: ePBS stability broadly achieved; 3 CL clients ready; avoids future awkward workarounds (e.g., attestation count changes) — 00:14:00
    • ·Prysm builder API testing urged at devnet level before any 'final devnet' designation; Besu echoed need for unhappy-path testing — 00:17:47
    • ·PTC security concern (voting on non-canonical forks) raised as potential readiness blocker for ePBS; deferred to CL breakout — 00:21:01
    • ·Barnabas: devnet-7 has a good chance of being the final ePBS devnet — 00:17:32
Action Items
  • •All CL teams — Discuss EIP-7688 inclusion in devnet-7 and builder API scope at ACDC Thursday — 00:20:12
ACDEAllCoreDevs — Execution #2392026-06-18
Targets
  • •glamsterdam-devnet-6 launch — mid-week, week of June 23, 2026 — 00:12:20
  • •Alpha 11 CL specs + EL tests — Monday, June 23, 2026 — 00:12:29
  • •All devnet-6 PRs merged + CL Alpha 11 release — Friday/Monday for Wednesday devnet-6 launch — 01:05:00
Decisions
  • •EIP-8282 added as CFI to Glamsterdam; no objections raised on call — 00:13:17
  • •EIP-7928 soft-committed using Tony's proposal as default; teams to review Dragon's alternative async; final decision by end of week to meet devnet-6 Monday test deadline — 00:25:57
  • •EIP-7937 state gas refund and Create charging changes merged; spec for devnet-6 — 00:30:41
  • •EIP-7645 (alias ORIGIN to SENDER) CFI'd to Hegota; EIP-8304 (Trustless Log Index) PFI'd to Hegota — 00:49:59
Highlights
  • Eip Proposals Hegota:
    • ·EIP-8304 (Trustless Log/Tx Index): sorted SSZ tables per block in system contract; <2% block processing overhead; proof generation ~17ms avg; PFI'd — 00:33:40
    • ·EIP-7645 (alias ORIGIN to SENDER): removes pre-AA tech debt; ORIGIN use being exploited in the wild; CFI'd to Hegota — 00:47:30
    • ·EIP-2488 (deprecate CALLCODE opcode): presenter absent; deferred to next call for presentation — 00:47:30
  • Fork Status And Schedule:
    • ·glamsterdam-devnet-5 at 95% participation; Prysm and Nimbus nodes still offline — 00:11:53
    • ·glamsterdam-devnet-6 targeting mid-next-week; Alpha 11 CL specs + EL tests due Monday; missing stable container/SSZ EIP on CL side — 00:12:14
    • ·EIP-7904 (compute repricing) converted to informational EIP; all clients exceed 100M gas/sec; no repricings needed for Glamsterdam — 00:27:10
  • Glamsterdam Spec Changes:
    • ·EIP-8282 (validator/builder queue separation): 2 CL implementations ready; awaiting 1 EL implementation; CFI added to Glamsterdam Meta EIP — 00:13:17
    • ·EIP-8189 (Snap2 networking): Geth, Besu, ethrex progressing; proposed for inclusion in Glamsterdam or Hegota Meta EIP — 00:16:43
    • ·EIP-7928 (BAL state access restructuring): soft-committed to Tony's proposal; Dragon's alternative (move balance+call-stack check before loading target) also under consideration; decision async by end of week — 00:17:07
    • ·EIP-7937 state gas refund flow updated: refunds now return to gas-left first, then reservoir; Create charging now unconditional with end-of-execution refill; merging today for devnet-6 — 00:28:13
Action Items
  • •All EL client teams — Review Dragan's three-option summary for EIP-7928 BAL state access ordering; respond async by end of day (EU teams by tomorrow morning) — 00:25:57
  • •nixo — Merge EIP-8282 into Glamsterdam Meta EIP (8081) following no objections on call — 00:14:29
PQIPQ Interop #0442026-06-17
Decisions
  • •lean spec PR #791 (optimized block building) will not be merged into spec as-is; clients encouraged to use it as implementation guidance; may be added as a separate named optional function — 00:37:30
Highlights
  • Documentation:
    • ·lean spec simplification nearly complete: unused functions removed, documentation condensed, more tests added; slides being prepared to share with EF this week — 00:30:36
    • ·Plonky3: multilinear proving system skeleton merged; incremental push toward multilinear backend alongside existing univariate FRI system — 00:32:43
  • Client Updates:
    • ·Zeam: proof merging taking too long on normal hardware; i7 (20-core/28-thread) meets 0.4–0.5s target; optimizations and early type-1 aggregation in previous slot being explored — 00:10:51
    • ·Ream: excessive memory usage (up to 28 GB) on DevNet 4; new allocator, improved pruning, and block processing fixes underway before moving to DevNet 5 — 00:15:52
    • ·Lantern: snappy decoding error root cause found and fixed; block building averages 0.9s (aggregation only, excludes final block proof) — 00:17:29
    • ·Ethlambda: unified branch sync, fork-choice/finality alignment with lean spec; Gloas prototype started for DevNet 6 proposal — 00:21:08
  • Testing Progress:
    • ·DevNet 5: type-2 final block proof taking 2.5–2.6s on normal machines; exceeds 4s slot budget for 35% of Grandine's builds, causing late proposals and bumpy finalization — 00:24:10
    • ·Three options discussed to address proof timing: bump machine specs to i7-class, increase slot time to 12s, or optimize type-2 proving; optimization headroom uncertain — 00:26:07
    • ·Current DevNet 5 branch uses full-size XMSS signatures; smaller XMSS variant in progress may improve proving times — 00:29:12
  • Eip Proposals Devnet6:
    • ·Ethlambda proposing Gloas prototype for DevNet 6 consideration — 00:22:00
Action Items
  • •All lean client teams — Client teams review lean spec PR #791 (block building algorithm) for implementation guidance on attestation scoring and proof-aware block construction — 00:35:10
  • •Thomas Coratger — Post async message to channel for Emil on type-2 proof optimization headroom and slot timing options — 00:29:53
FOCILFOCIL Breakout #0362026-06-16
Decisions
  • •IL bitlists removed from spec; engine API kept as-is; EL deduplication of IELTs deferred to future change — 00:20:23
  • •IL enforcement turned off during non-finality (circuit breaker); 1-epoch threshold preferred over 2; final value to be confirmed after broader review — 00:47:03
Highlights
  • Client Updates:
    • ·Lodestar rebased on Glamsterdam devnet-5; bit serialization bug (Gloas version) confirmed fixed — 00:05:23
    • ·Censoring builder branch works; Bharath to retest against latest Lodestar branch tomorrow — 00:05:44
    • ·Lighthouse rebased on Glamsterdam devnet-5; FOCIL implementation still being tested — 00:07:23
  • Focil Spec Changes:
    • ·IL bitlists decided for removal: can be faked by builders; no enforcement mechanism; engine API unchanged for now — 00:09:43
    • ·Payload status V2 proposed: adds 'latest IL-satisfied hash' field to clarify IL compliance across branches — 00:20:37
    • ·Accepted payloads (non-canonical branch) treated as IL-compliant by CL; EL must cache IELTs for head (and possibly parent) payload only — 00:22:03
    • ·Non-finality circuit breaker: rough consensus to turn off IL enforcement after 1 epoch without finality (down from current 2-epoch threshold); to be confirmed via Discord — 00:47:03
Action Items
  • •Jihoon — Open Discord thread on 1-epoch vs 2-epoch non-finality threshold for IL enforcement; gather broader input from client teams — 00:52:40
  • •Jihoon — Prepare write-up and spec PR covering: payload status V2, accepted-payload IL handling, and non-finality circuit breaker; coordinate test case changes with Felix — 00:57:28
ACDTAllCoreDevs — Testing #0832026-06-15
Targets
  • •Test vectors for devnet-6 EIPs — Spencer targeting Monday June 23 — 00:44:26
  • •glamsterdam-devnet-6 launch — targeting Wednesday June 25 — 00:44:37
  • •EIP-8282 go/no-go decision — ACDE Thursday June 18 — 00:16:03
Decisions
  • •Correctness over speed: EIP-8282 will be included in Glamsterdam; formal ratification at ACDE Thursday — 00:25:29
  • •EIP-8282 targeted for glamsterdam-devnet-6 alongside remaining repricing EIPs; devnet-6 target next Wednesday — 00:46:24
Highlights
  • Testing Progress:
    • ·Glamsterdam devnet-5 stable but Prysm has gossip/PeerDAS column issues causing fallback to initial sync; Grandine fixing edge cases — 00:41:30
    • ·No test vectors yet for all remaining devnet-6 EIPs; Spencer targeting Monday for readiness — 00:44:05
  • Fork Status And Schedule:
    • ·EIP-8282 (builder execution requests via system contract) proposed for Glamsterdam; separates builder and validator deposit paths — 00:07:43
    • ·Consensus: EIP-8282 is the right design; correctness over speed; contract audit needed (est. 1-2 months) — 00:23:52
    • ·Splitting EL/CL forks proposed by Dragan; Potuz and Barnabas push back — ePBS needed before gas limit increase due to block propagation constraints — 00:28:10
    • ·Glamsterdam devnet-6 target: next Wednesday (June 25); plan to include EIP-8282 alongside remaining repricing EIPs — 00:36:06
  • Eip Proposals Glamsterdam:
    • ·SSZ Engine API (execution-apis PR #793): 3+ client implementations exist; Prysm nearly ready; not high priority vs. fork work — 00:37:48
Action Items
  • •EL teams — EL teams review EIP-8282 system contract and confirm implementation scope before ACDE Thursday — 00:16:03
  • •CL + EL teams — Review updated execution-apis PR #793 (SSZ Engine API) and align implementations to new spec — 00:39:40
RPCRPC Standards #0282026-06-15
Decisions
  • •Schema version bump PR (831) merged immediately during call — 00:30:36
  • •PR 814 (default block param) to be marked ready for merge; Erigon implementation pending — 00:33:56
  • •v1.0 release to follow resolution of HiveChain deposit contract issue, not tied to Glamsterdam — 00:36:11
Highlights
  • Documentation:
    • ·Error codes overhaul: Sina's draft PR removes redundant JSON-RPC standard errors from per-method listings; near consensus to merge — 00:08:17
    • ·eth_fillTransaction PR (803): raw RLP output removed, JSON-only; stepping stone toward deprecating eth_sendTransaction; awaiting Nethermind sign-off — 00:31:24
    • ·Default block param to 'latest' on state methods (PR 814): merged in all clients except Erigon and ethrex — 00:33:07
  • Testing Progress:
    • ·PR 830 (HiveChain deposit contract address): config mismatch identified; must regenerate HiveChain before merging; Felix to investigate — 00:23:47
  • Versioning And Releases:
    • ·execution-apis versioning released; latest is 1.0.0 Beta 7; v1.0 release timing TBD (possibly tied to Glamsterdam) — 00:04:10
Action Items
  • •Chase Wright — Chase to re-engage Sina and Simpson to finalize error codes compromise; resolve async — 00:16:05
  • •Boma — Tag Nethermind on eth_fillTransaction PR (803) for sign-off before merge — 00:32:53
  • •Erigon (Tullio) — Erigon to review and implement default block param PR (814) — 00:34:07