Archived content — no longer updated since July 2026. See Reports for the latest research.
Ethereum Weekly Report
← Archive

May 2026 — Week 4

· @r2jamong .md

Weekly Ethereum Research Report (2026-05-18 ~ 2026-05-22)

TL;DR

  • Bottom line: After ACDE #237, the Hegota track formally appeared in the data layer, while Glamsterdam devnet-5, BAL execution semantics, and Lido operational risks were all realigned in the same week.
  • Numbers: The 5/22 snapshot normalized to 557 EIPs, Lido CSM reached 7.05%, the Kelp DAO deployment was 2,644 ETH, and the SDVTM wind-down was recorded for 72 regular clusters.
  • Action: Operators and researchers should prioritize tracking ACDC #179 on 5/28, final EIP-7904 benchmarking, EIP-7928·EIP-8246 implementation tags, and Lido Snapshot vote entry in June.

Top 3 Takeaways

  1. HIGH The Hegota track became formally visible within a single week -- EIP-7805 FOCIL CL Headliner Scheduled + EIP-4758 SELFDESTRUCT Deactivation Proposed + EIP-8246 Draft→Review.

At ACDE #237 (5/21), the STEEL team (@petertdavies) officially requested Hegota CFI status for EIP-4758 (SELFDESTRUCT Deactivation) → the 5/22 EIP upgrade status snapshot listed Hegota proposed=[4758, 7709, 7716, 8025, 8182, 8188, 8205, 8253] and scheduled=[7805] for the first time, marking the track's first formal appearance in the data layer. In the same week, Paweł Bylica promoted EIP-8246 (Remove SELFDESTRUCT Burn) from Draft → Review via commit 45b443d at 5/21 18:47 UTC, creating a decisive signal for Glamsterdam devnet-5 scoping. The official FOCIL #034 notes (published 5/21) confirmed disabling IL enforcement during non-finality (2-epoch non-finality) and fixed-index validation for EIP-7702 frame transactions, with Hegotá devnet-0 explicitly given an ETA of release within 1~2 weeks based on Glamsterdam-devnet-4. New EIP-8188 State Tiering (@weiihann) + EIP-8182 Private ETH/ERC-20 Transfers (@RogerPodacter) proposals appeared simultaneously.

  1. HIGH The convergence axis for the EIP-7928 BAL spec moved from the "type/field stage" to the "execution semantics stage" + three follow-up EIPs, EIP-8268 / EIP-8256 / EIP-7954, entered simultaneously.

EIP-7928 BAL received two commits within five hours on a single date (5/21). Toni Wahrstätter's 07:57 UTC commit 4675100 clarified the "EIP-7702 insufficient gas edge case", and Holger Drewes's 12:56 UTC commit 1505de0 clarified "CREATE inclusion and storage no-op handling". Following the sequence of 4/19 lightclient uint16→uint64, 4/20 Toni W. uint32 readjustment, and 4/20 per-dimension gas + frame-scoped refund flow, the convergence axis moved from type width / field structure to execution semantics for CREATE pre-declaration, SSTORE no-op, and delegated EOA gas insufficiency. In the same week, CPerezz introduced EIP-8268 'Storage roots in BAL' (eth-magicians 28585, 5/21 08:29 UTC), mariosioannou-create introduced EIP-8256 'Blob Streaming' (eth-magicians 28586, 5/21 13:36 UTC), and Giulio Rebuffo introduced EIP-7954 'Raise Contract Code Size to 64KiB' via commit 1dc9bc8 at 5/21 16:40 UTC.

  1. HIGH Lido Q1 2026 quarterly report + the official Kelp Post-Mortem were published — the quantitative peak of both governance and operations tracks.

@LidoFinance 5/20 11:19 UTC published Validator & Node Operator Metrics: Q1 2026 — simultaneously signaling four quantitative improvements: CSM reached 7.05% of Lido + "validator set decentralization strengthened further" + "client diversity improved" + "resilience improved". Since this approaches the staged stake share cap after CSMv2 launch (currently 7.5%, planned increase to 10%), a significant share of remaining new key allocation is moving to the permissionless track, creating seat-congestion pressure for Curated Module entry candidates. On 5/21, lidolabs-operations Lido Research 11579 published the official comprehensive Kelp incident review. Confirmed financial impact: total DAO deployment of 2,644 ETH (≈$6.3M) — (a) 2,500 ETH rsETH-level rescue, (b) 143.98 ETH EarnETH First-Loss direct cover (below the 1% threshold, but approved by the DAO as a "Kelp-specific one-off" exception), and (c) maximum exposure of ~9,000 ETH.

1. Roadmap / Upgrade Change Highlights

Hegota Track Officially Visible (8 proposed + 1 scheduled first listed)

Item 5/18 (Mon) 5/22 (Fri) Weekly Change
Hegota track EIP upgrade status listing Data not reflected (fetch truncated to 246) proposed=[4758, 7709, 7716, 8025, 8182, 8188, 8205, 8253] + scheduled=[7805] + considered=[8141] + declined=[7807, 8184] + withdrawn=[8105] First normalization of the 5/22 snapshot through fetch_forkcast.py pagination fix (246 → 557 EIPs) + first appearance of the Hegota track in the data layer
EIP-7805 (FOCIL) Glamsterdam CL Headliner candidate Hegota Scheduled (CL Headliner confirmed) Previous week's ACDC #178 agenda advanced two items, "Glam + Hegotá", and this week's 5/22 snapshot reflected the data
EIP-4758 (Deactivate SELFDESTRUCT) -- Hegota Proposed (5/21 ACDE #237 STEEL team CFI request) @petertdavies argument: "extremely low usage + remaining use cases are also unaffected by EIP-4758"
EIP-8188 (State Tiering by Write Age) -- Hegota Proposed (5/21 ACDE #237, first presented by @weiihann) Separate inactive state (~80%) and active state + differentiated gas charges for writes / feedback stage
EIP-8182 (Private ETH and ERC-20 Transfers) -- Hegota Proposed (5/21 ACDE #237, first presented by @RogerPodacter) System-contract-based privacy / concerns raised about prematurely adopting a specific encryption method
EIP-8253 (Upgrade pre-Spurious-Dragon accounts) (listed previous week on 5/12) Hegota Proposed + 5/21 14:45 UTC title edit (Jochem Brouwer) EthereumJS legacy state cleanup track
pre-Spurious-Dragon new EIP -- 5/21 01:35 UTC commit 60ecb84 (Jochem Brouwer) EIP number unassigned / EIP-161 residue cleanup / possible connection to The Purge track

Glamsterdam devnet-5 Scoping + Pre-Spec-Freeze Cleanup

Item 5/18 (Mon) 5/22 (Fri) Weekly Change
EIP-7773 Glamsterdam Meta scheduled (previous week 5/12 SFI 8-item promotion) scheduled=[7708, 7732, 7778, 7843, 7928, 7954, 7976, 7981, 8024, 8037] first data listing 5/21 02:11 UTC commit 8e5113e (nixo) "move PFI above DFI" meta EIP structure reorganization
EIP-8246 (Remove SELFDESTRUCT Burn) CFI / Draft 5/21 18:47 UTC Draft → Review promotion (Paweł Bylica) Entered EIP Editor format review — client-implementable spec completeness + follow-up to ACDT #080 devnet-5 scoping
EIP-7904 (Compute Gas Cost Increase / contract code 64KB) ACDT #080 devnet-5 candidate ACDE #237 removal possibility discussed (decision after end-of-month benchmarking) In three days, moved from devnet-5 inclusion candidate → removal review target / argument that performance target is already achieved / need to verify entity note update or EIP number reassignment possibility (identity with EIP-7954)
EIP-7928 BAL CREATE inclusion + storage no-op -- 5/21 commit 1505de0 (Holger Drewes, 12:56 UTC) Defines CREATE/CREATE2 BAL inclusion criteria + SSTORE no-op handling
EIP-7928 BAL EIP-7702 gas-insufficiency edge case -- 5/21 commit 4675100 (Toni Wahrstätter, 07:57 UTC) Decides the delegated EOA × BAL interaction — reduces possibility of devnet consensus failure
bal-devnet-7 v7.1.1 (previous week v7.1.0) ACDT #080 (5/18) cost_per_state_byte = 1530 confirmed + hive.ethpandaops.io verification completed v7.2.0 in preparation (additional test cases) + Glamsterdam-devnet-4 stable operation (based on consensus-specs v1.7.0-alpha.8)
EIP-7688 (Forward Compatible Consensus Data Structures) Review Four commits in a 3-hour window on 5/19 13:55~18:24 UTC + one accompanying EIP-8070 commit — five commit concentration (i) Validator SSZ Container retention rationale, (ii) cleanup opportunities resolved, (iii) wording/nits, (iv) "Rebase requirements to be based on Fusaka" — explicit movement of EIP-7688 activation timing to the Fusaka baseline — signal of imminent Review → Final promotion

BAL Extension / DA Expansion / EVM Limit Adjustment (3 New EIPs Appearing Simultaneously)

EIP New Appearance Time Core Content
EIP-8268 (Storage Roots in BAL) 5/21 08:29 UTC (eth-magicians 28585, CPerezz) Attach post-block storage trie roots to state-modifying BAL entries → enables partially stateful node verification / practical intermediate step for the stateless client roadmap / enables RPC services to selectively retain state / possible DVT cluster "stateful witness" division-of-labor model
EIP-8256 (Blob Streaming) 5/21 13:36 UTC (eth-magicians 28586, mariosioannou-create) Formal EIP-ization of ethresear.ch 24202 "Scaling the DA layer with blob streaming" research / AOT blobs — pre-acquired through ticket contracts + slot-wide rate-limited propagation / JIT blobs — critical path maintained / reliably expands PeerDAS sampling across the full slot + mitigates the free option problem
EIP-7954 (Raise Contract Code Size to 64KiB) 5/21 16:40 UTC (commit 1dc9bc8, Giulio Rebuffo) EIP-170 (2017) 24KB → 64KiB / first code-size cap change in 9 years since EIP-170 / reduces the burden of single deployment for giant contracts such as Lido stETH·Aave·Uniswap V4 / requires EL client code loading·verification logic buffer-size adjustment
EIP-8266 (Expiring Nonces for Frame Transactions) 5/20 05:56 UTC (eth-magicians 28575) Posted one hour after Vitalik's 5/20 06:55 UTC "Keyed nonces" tweet — prior coordination or coincidence (needs verification) / AA UX supplement

Privacy / Governance Signals

  • Vitalik's short-term privacy roadmap tweet (@VitalikButerin 5/20 06:55 UTC) — "Short-term things being done to shift Ethereum toward native privacy" -- (a) AA + FOCIL — "makes privacy protocol txs first-class with strong inclusion guarantees", (b) Keyed nonces (linked to EIP-8266 above), (c) Access-layer work (Kohaku, private reads).
  • Devcon 8 Mumbai November 2026 announcement (@ethereum 5/20 16:35 UTC + @ethereumfndn 5/20 16:39 UTC) — explicitly states value keywords "open source, privacy, security, censorship resistance" — consistent signal of higher Foundation-level priority for the privacy agenda.
  • RANDAO Breaks at L* (PQ VRF) -- ethresear.ch 24906 (arianaraghi, 5/20 06:02 UTC) — warns that RANDAO completely fails if BLS keys are discarded at the leanSig milestone L*, and proposes a leanSig seed-derived PRF-commitment VRF with WHIR proof attached. Validator implication: PQ transition is not a simple key replacement but a partial modification of the consensus mechanism — an infrastructure burden on a 5~10 year horizon.

2. EIP Status Changes (Monday vs Friday)

Data integrity signal (day of fetch normalization after 18 days of LEVEL 3+): From 5/4~5/21, forkcast snapshots maintained a 246-item capacity for 18 consecutive days + 1~4 EIP rotating drift each day. Pagination fix applied in the 5/22 snapshot — 557 EIPs with +311 catch-up — resolving either scripts/fetch_forkcast.py pagination (per_page=100 + page loop) or accumulated Trees API migration delay at this week's end. Therefore, note that this section's 5/18 (truncated 246) vs 5/22 (full 557) comparison includes many "data restoration" effects rather than actual EIP status changes. Trust only actual changes cross-verified by calls/commits/EF blog across four sources.

5/18 → 5/22 Snapshot Summary Comparison

Hardfork / Stage 5/18 (truncated 246) 5/22 (full 557) Notes
Pectra included [2537, 2935, 6110] [2537, 2935, 6110, 7002, 7251, 7549, 7623, 7642, 7685, 7691, 7702, 7840] 9 catch-up items (actually already Final, data restoration)
Glamsterdam considered [2780] [2780, 7610, 7688, 7904, 7975, 7997, 8038, 8045, 8061, 8070, 8080, 8136, 8159, 8246] 13 catch-up items + first data confirmation of EIP-8246 Considered stage
Glamsterdam scheduled (field absent) [7708, 7732, 7778, 7843, 7928, 7954, 7976, 7981, 8024, 8037] First consistent data-layer reflection of the 5/12 ffebcbc SFI 8-item batch promotion
Glamsterdam withdrawn -- [6873, 7667, 7919, 7999] 4 catch-up items
Glamsterdam proposed -- [8254] EIP-8254 (Cap Deposit Requests per Block) first listed
Hegota overall (field absent) proposed=[4758, 7709, 7716, 8025, 8182, 8188, 8205, 8253] + scheduled=[7805] + considered=[8141] + declined=[7807, 8184] + withdrawn=[8105] Hegota track's first formal appearance in the data layer
Fusaka included -- [7594, 7642, 7823, 7825, 7883, 7892, 7910, 7917, 7918, 7934, 7935, 7939, 7951] 13 catch-up items (included processing after Fusaka activation)

Trustworthy Actual Changes This Week (Cross-Verified by Calls / Commits / External Primary Sources)

Hegota track official listing (5/21 ACDE #237 + 5/22 snapshot)

  • EIP-7805 (FOCIL) -- Hegota scheduled (CL Headliner confirmed)
  • EIP-4758 (Deactivate SELFDESTRUCT) -- Hegota proposed (5/21 ACDE #237 STEEL team CFI request)
  • EIP-7716 (Correlated Downtime Penalties) -- Hegota proposed
  • EIP-8205 (Validator Pre-registration) -- Hegota proposed
  • EIP-8188 (State Tiering by Write Age) -- Hegota proposed (first presented by @weiihann at 5/21 ACDE #237)
  • EIP-8182 (Private ETH and ERC-20 Transfers) -- Hegota proposed (first presented by @RogerPodacter at 5/21 ACDE #237)
  • EIP-8253 (Upgrade pre-Spurious-Dragon Accounts) -- Hegota proposed (5/21 title edit)
  • EIP-8141 (Frame Transaction) -- Hegota considered

Status / lifecycle promotion

  • EIP-8246 (Remove SELFDESTRUCT Burn) -- 5/21 18:47 UTC Draft → Review promotion (Paweł Bylica, commit 45b443d). Review — EIP Editor format review + client-implementable maturity.

New EIP registrations (5/20 ~ 5/21)

  • EIP-8266 (Expiring Nonces for Frame Transactions, 5/20 05:56 UTC)
  • EIP-8268 (Storage Roots in Block Access Lists, 5/21 08:29 UTC, CPerezz)
  • EIP-8256 (Blob Streaming, 5/21 13:36 UTC, mariosioannou-create + bharath-123 PR #11610)
  • pre-Spurious-Dragon new EIP (5/21 01:35 UTC, commit 60ecb84, Jochem Brouwer, number unassigned)

Spec refinement / meta cleanup

  • EIP-7928 BAL -- two items: CREATE inclusion + storage no-op + EIP-7702 insufficient gas edge case (5/21 07:57 + 12:56 UTC)
  • EIP-7954 (Raise contract code size to 64KiB) -- 5/21 16:40 UTC (Giulio Rebuffo)
  • EIP-7773 Glamsterdam Meta -- 5/21 02:11 UTC "move PFI above DFI" structure reorganization (nixo)
  • EIP-7688 -- four commits on 5/19 13:55~18:24 UTC + one accompanying EIP-8070 commit — Review → Final imminent

Glamsterdam devnet-5 scoping change

  • EIP-7904 -- ACDT #080 (5/18) devnet-5 candidate → ACDE #237 (5/21) removal possibility discussion (decision after final end-of-month benchmarking / atmosphere effectively leaning toward removal) / need to verify whether it is identical to EIP-7954

3. Validator / Infrastructure Key Issues

Lido VaNOM Q1 2026 Quarterly Report -- CSM Reaches 7.05% — Quantitative Entry into Four Simultaneous Lido NO Tracks

  • @LidoFinance 5/20 11:19 UTC published Validator & Node Operator Metrics: Q1 2026. Body quote: "Validator set decentralization strengthened further in Q1 driven by substantial growth in permissionless staking through CSM, while resilience and client diversity across the protocol also improved. -- CSM reached 7.05% of Lido". Four simultaneous quantitative progress signals: (a) CSM 7.05% (elevated as a core permissionless staking channel), (b) decentralization strengthened, (c) client diversity improved, (d) resilience improved. Additional verification needed: because the Q1 2026 blog body was not directly checked, detailed figures on SDVTM share, client distribution, and geographic distribution should be supplemented by citing follow-up notes.
  • Lido NO entry four-track mapping: (i) CSM — 7.05% of Lido, staged cap increase plan from 7.5% → 10%, (ii) 31 Curated NOs — four accountability governance tracks (post-mortem + NO compensation + formal verification + SEAL), (iii) Simple DVT Module 72 regular clusters — 7/1 wind-down, (iv) new IDVTC (Identified DVT Cluster) operator type — maintaining a DVT operation path inside CSM. From the perspective of Curated Module entry candidates: a significant share of remaining new key allocation is moving to the permissionless track — CM seats are effectively stagnant + scoring competition intensifies across the six types (especially Decentralization Operator) defined in the CMv2 Type Assessment Framework(output/notes/validator-ops/2026-04-21-cmv2-operator-type-framework-eip7928-uint32-focil33-earneth-quantification.md).

Official Kelp Incident Review Post-Mortem -- 2,644 ETH DAO Deployment + New 4-Axis Risk Framework

  • lidolabs-operations 5/21 Lido Research 11579 — official comprehensive review of the Kelp incident. Financial impact (confirmed figures): ① total DAO deployment 2,644 ETH (≈$6.3M) -- 2,500 ETH rsETH-level root backing shortfall rescue + 143.98 ETH EarnETH First-Loss direct cover, ② EarnETH residual loss of 143.98 ETH arose under "elevated borrow rates, frozen markets, delayed unwind conditions", ③ maximum exposure of ~9,000 ETH net exposure (leveraged rsETH/WETH strategy on Aave Core).
  • First-Loss activation rule change: below the general threshold (1%), but the DAO approved an exception as "Kelp-specific one-off use". The vault resumed after 27 days of halted operations.
  • Four structural risk-framework changes: (1) Supply-side monitoring (mint·total supply·bridge anomalies), (2) Secondary-effect pricing (pricing contagion through Aave market stress), (3) Pre-deployment stress-testing (time-to-exit · cost-to-exit · defend-vs-unwind thresholds), (4) Formalized protection stack (standardizing first-loss activation criteria · curator · DAO intervention scenarios). Compared with scenario B/C estimates in the 4/21 note, the realized loss was closer to scenario A (partial drawdown). Empirically strengthens the Curated Operator sales message ("Pure stETH delegation, unrelated to LRT/restaking") + recursive strategies require deeper pre-deployment review + mandatory curator sign-off.

Simple DVT Module Wind-Down + IDVTC Creation -- Structural Transition in Lido's DVT Strategy

  • research.lido.fi 11571 (KimonSh, 5/18 16:22 UTC) — SDVTM 72 regular clusters wind-down starting 7/1 + continued operation of 10 Super Clusters + creation of IDVTC operator type — Home/Community Stakers + Professional NOs retain a DVT cluster operation path inside CSM / NOM coordination — initial matching only, operations are self-directed. Early termination by roughly one year from the original "up-to-three-year lifetime" announcement (activated 2024/5/1 → ~2027/5).
  • Three reasons for early termination: (1) operational burden (23 operator rotations completed + 11 additional cluster rotations needed), (2) operational economics ("80 validators after 7-way 10% protocol fee split and 1% reward share" / break-even on time and capital), (3) marginal deficit (SDVTM 2.956% DAO fee vs other modules 6%+).
  • Current SDVTM operator statistics (as of 4/30/2026): 31 SDVTM operators already active operating in CSM + 21 with ICS status. Snapshot vote entry ETA — June / wind-down start — July / Grant distribution — August + December (0.175 ETH × 2 tranches, using EGG funds).
  • Message alignment: not "Lido giving up on DVT" but a "DVT model pivot" — end of the protocol-coordinated DVT model experiment + DVT itself becomes permanent through CSM IDVTC — future Lido DVT entry path is unified into CSM IDVTC (excluding 10 Super Clusters) + Obol Network + SSV Network candidate operators are also integrated into IDVTC.

SenseiNode Incident Report -- Promise to Compensate DAO with 1.224 ETH of Own Funds

  • research.lido.fi 11573 (Chitty, 5/19 11:23 UTC) — official incident report from SenseiNode. Body quote: "on April 19, 2026, one of our Lido validator infrastructure servers in the São Paulo region experienced a critical hardware failure affecting the operating system disk... approximately 1.224 ETH in missed rewards. SenseiNode will fully compensate the DAO for the associated loss."
  • Implication: a different pattern from Kelp first-loss (2,644 ETH, DAO capital) — a case of direct NO accountability compensation — practical demonstration of the "NO compensation" track among the four Curated NO accountability governance tracks (post-mortem + NO compensation + formal verification + SEAL). Signal that SOPs for "own-capital compensation when an outage occurs" are becoming standardized for Lido Curated Operator entry candidates.

EL Peer Composition Drift / Client Risk (Continuation from Previous Week)

  • The previous week's 5/12 Stereum Labs 36-node fleet two-week measurement (Besu→Reth ~75%→~96%) naturally aligns with this week's follow-up discussion at P2P Networking #001 on 5/20 around cell-level deltas + sparse blobpool + ethp2p. Decision contents remain unconfirmed because official notes are unpublished.
  • Client release gap entering the 50-day range: Geth v1.17.3 / Besu 26.5.0 / Erigon v3.4.1 / Nimbus v26.5.0 remain cumulative + three HIGH risks (structLog Breaking Change / Besu CVE / Erigon segfault) remain valid. After ACDT #080 (5/18), monitoring GitHub Releases for EL/CL releases supporting Glamsterdam devnet-5 is essential (EIP-8037·EIP-7928 BAL·EIP-8246 implementation tags).
  • PQ Interop #40 (5/20 14:00 UTC) -- leanEthereum devnet5 aggregate block proof PR in progress + leanSpec stabilization + validator-count expansion testing agenda. Official notes unpublished.

4. Protocol Call Key Decisions

Source: output/notes/weekly/2026-05-22-weekly-calls-summary.md (7 total calls, 1 official FOCIL #034 note published + remaining 6 unpublished)

This Week's Call List (7 Total)

Date Call Number Key Topic Status
5/18 (Mon) 14:00 UTC ACDT — All Core Devs Testing #080 bal-devnet-7 v7.1.1 (cost_per_state_byte=1530) confirmed + Glamsterdam-devnet-5 scoping (EIP-8038, EIP-2780, EIP-7904, EIP-8246) + REST-SSZ Engine API comparison (execution-apis#793 vs #764) Notes unpublished
5/18 (Mon) 15:00 UTC RPC Standards #026 EIP-7910 (eth_config) client configuration standardization + uncle method removal (execution-apis#788) + new eth_baseFee (#795) + eth_capabilities (#755) + opcode tracer unification (#762) Notes unpublished
5/19 (Tue) 13:00 UTC FOCIL Breakout #034 Svalbard interop follow-up + EIP-7805 devnet-0 pre-stabilization + non-finality IL deactivation + EIP-7702 fixed-index validation Published 5/21 (@jihoonsong)
5/20 (Wed) 14:00 UTC All Wallet Devs #039 Wallet-side EIP-7702 integration + Frame Transaction UX Notes unpublished
5/20 (Wed) 14:00 UTC Post-Quantum Interop #040 leanEthereum devnet5 aggregate block proof PR + leanSpec stabilization + validator-count expansion Notes unpublished
5/20 (Wed) 15:30 UTC P2P Networking #001 (new series) #001 cell-level deltas (@MarcoPolo / PeerDAS) + sparse blobpool (@healthykim, @kamilsa / EIP-8070 eth/72) + ethp2p updates (@raulk) Notes unpublished
5/21 (Thu) 14:00 UTC ACDE — All Core Devs Execution #237 (90 min) Agenda "Glam + Hegotá" / EIP-7928 BAL spec update / EIP-7904 removal possibility discussion / EIP-4758 Hegota CFI request (STEEL team) / first presentation of EIP-8188 / EIP-8182 Notes unpublished

Key Decision Summary

  1. ACDE #237 (5/21) — peak formal launch of the Hegota track -- STEEL team (@petertdavies) requested EIP-4758 Hegota CFI + two new EIPs were first presented: EIP-8188 State Tiering (@weiihann) + EIP-8182 Private Transfers (@RogerPodacter). EIP-7904 removal possibility discussed — moved from ACDT #080 (5/18) devnet-5 candidate to removal-review target in three days — exposing the gap between ACDT (testing) and ACDE (execution) agendas. Discussion also covered EIP-7928 BAL failed-call handling for EIP-7702 delegation inclusion + EIP-8246·4758 SELFDESTRUCT-linked roadmap (Glamsterdam → Hegotá).

  2. FOCIL #034 (5/19) — official notes published + non-finality IL deactivation + EIP-7702 fixed-index validation confirmed -- Published by @jihoonsong on 5/21. Two key design decisions: (a) disabling IL enforcement during non-finality (2-epoch non-finality) periods — same logic as the proposer-boost circuit breaker + prioritizing network stability, (b) fixed-index-based IL validation — removes the burden of repeated builder execution when EIP-7702 frame transactions are included. Lodestar+Besu local devnet achieved at Svalbard + ethrex onboarding + Hive tests passed + Hegotá devnet-0 target: stabilize within 1~2 weeks based on Glamsterdam-devnet-4, then launch in ~1 week.

  3. ACDT #080 (5/18) — Glamsterdam devnet-5 scoping + bal-devnet-7 v7.1.1 verification completed -- cost_per_state_byte = 1530 (EIP-8037) confirmed + hive.ethpandaops.io verification completed + v7.2.0 in preparation + Glamsterdam-devnet-4 stable operation (consensus-specs v1.7.0-alpha.8). Four devnet-5 candidates: EIP-8038 / EIP-2780 (TX_BASE_COST benchmarking) / EIP-7904 / EIP-8246. Early-stage discussion of REST-SSZ Engine API comparison (execution-apis#793 vs #764).

  4. P2P Networking #001 (5/20) — official launch of new breakout series -- biweekly cadence confirmed / meaningful as a separation of Ethereum's P2P layer into a distinct governance track / naturally aligned with follow-up discussion after the Stereum Labs 36-node fleet two-week measurement / decision contents undisclosed.

  5. RPC Standards #026 (5/18) — six simultaneous EL API standardization agenda items -- EIP-7910 eth_config + uncle method removal (Breaking Change) + eth_baseFee + eth_subscribe/unsubscribe + eth_capabilities + opcode tracer unification. Decision contents undisclosed.

  6. Accumulated official notes unpublished: ACDC #178 (D+8) / ACDT #080 (D+4) / RPC #026 (D+4) / AWD #039 (D+2) / P2P #001 (D+2) / PQI #040 (D+2) / ACDE #237 (D+1) — 6 items. FOCIL #034 publication is the single priority case (timely publication two days before as input to ACDE #237 decisions).

5. This Week's Recommendation Status + Priority Writing Target Selection

Daily Recommendations (Topic Recommender)

Date Recommendation 1 Recommendation 2 Score
5/19 (previous week 5/14 cumulative) Lido May 2026 Snapshot 5-item same-day results analysis -- CMv2 NO Type Assessment + GateSeals→CircuitBreaker Simple DVT Module Wind-Down (research.lido.fi 11571) + new IDVTC operator type --
5/21 Vitalik short-term privacy roadmap + priority elevation just before Glamsterdam -- AA+FOCIL, Keyed nonces, Kohaku access-layer first-class signal + Devcon 8 Mumbai value-keyword alignment Lido Validator & Node Operator Metrics Q1 2026 quarterly report -- CSM reaches 7.05% + Lido NO entry four-track simultaneous-change window (5/21 recommendation body has no explicit score)

No notes were generated on 5/18 / 5/20 / 5/22 (presumed that the daily pipeline recommendation step was not run on those days). This week's recommendations are effectively available only for two dates, 5/19 + 5/21.

Priority Writing Targets (Top 3)

  1. [5/21 Recommendation 2] Lido VaNOM Q1 2026 quarterly report -- CSM reaches 7.05% + Lido NO entry four-track simultaneous-change window -- Category: report, length 3,500~4,500 Korean characters.

    • Reason: (i) 5/20 11:19 UTC @LidoFinance quarterly report publication — two-day analysis window as of 5/22 (golden window for publishing Korean analysis within one week), (ii) 5/21 Tokenholder Call body can be integrated, (iii) four simultaneous quantitative progress signals — "Validator set decentralization strengthened further" + "CSM reached 7.05%" + "client diversity improved" + "resilience improved" — directly usable as cited quantitative data in Curated Operator entry material v2, (iv) absence of Korean quarterly-report analysis + CSM 7.05% quantitative signal directly affects decisions by Korean institutional investors / staking operators.
    • Differentiation: separated from 5/20 recommendation 1 (previous-week cumulative qualitative Lido security-governance four-track) along the quantitative quarterly data axis.

  2. [5/21 Recommendation 1] Vitalik short-term privacy roadmap + priority elevation signal just before Glamsterdam -- AA+FOCIL, Keyed nonces, Kohaku access-layer first-class -- Category: issue, length 2,800~3,500 Korean characters.

    • Reason: (i) 5/20 06:55 UTC Vitalik direct tweet, two-day elapsed primary analysis window as of 5/22, (ii) same-day Devcon 8 Mumbai explicitly includes "privacy" value keyword — aligned signal from both foundation/Foundation channels, (iii) six days before 5/28 ACDC #179 "Glam / Hegota" and just before Glamsterdam CL specs freeze — decisive moment to position priority elevation, (iv) EIP-8266 (Expiring Nonces) at 5/20 05:56 UTC, one-hour gap — unique insight window to analyze potential linkage with Vitalik's "Keyed nonces" tweet.
    • Differentiation: zero Korean integrated analyses + first-class interpretation of the censorship-resistance meaning of the AA+FOCIL combination is not yet organized even in English materials.

  3. [5/19 Recommendation] Simple DVT Module Wind-Down (72 regular clusters ending 7/1) + new IDVTC operator type -- structural transition in Lido DVT strategy -- Category: article, length 4,000~5,000 Korean characters.

    • Reason: (i) research.lido.fi 11571 proposal at 5/18 16:22 UTC, four days elapsed as of 5/22 and entering the late golden window, (ii) Lido DVT strategy pivot from "protocol-coordinated → permissionless self-coordinated (CSM)" is a key moment requiring correction of the external narrative misconception that "Lido is abandoning DVT", (iii) Snapshot vote entry ETA June — narrative-alignment window just before the July wind-down, (iv) Obol Network + SSV Network candidate operators also integrated into IDVTC — zero Korean analysis + redefinition of the DVT operator ROI equation.
    • Differentiation: Recommendation 1 (Q1 quarterly report) + Recommendation 3 (DVT transition) can form a series — integrated analysis of the Lido NO entry four-track simultaneous-change window.

Recommended series continuity: Recommendation 1 (Lido Q1 quantitative) + Recommendation 3 (SDVTM Wind-Down) — Lido NO entry four-track series v1/v2 + 5/28 ACDC #179 results + June Snapshot vote results naturally align as this series' v3 update window. Recommendation 2 (Vitalik privacy) is an independent issue, with v2 publication naturally fitting immediately after 5/28 ACDC #179.

6. Major Schedule for Next Week (2026-05-25 ~ 2026-05-29)

Protocol Calls

Date Call Number Key Observation Points
5/26 (Tue) FCR — Fast Confirmation Rule #008 (estimated) Client / Spec / Research / Testing updates
5/27 (Wed) (estimated) Glamsterdam Repricings #008 (estimated) EIP-8037 follow-up + EIP-8038 devnet inclusion decision + EIP-2780 TX_BASE_COST benchmarking results
5/28 (Thu) 14:00 UTC ACDC — All Core Devs Consensus #179 (90 min) Agenda "Glam + Hegota" / EIP-7805 FOCIL Hegotá devnet-0 launch ETA confirmation / EIP-7716 / EIP-8205 CFI decisions / EIP-8188 / EIP-8182 CFI discussion
5/28 (Thu) (estimated) ACDT — All Core Devs Testing #081 (estimated) Glamsterdam devnet-5 launch follow-up + bal-devnet-8 transition + EIP-7904 final benchmarking results input

Devnet / Spec Milestones

  • Glamsterdam devnet-5 launch possibility -- bal-devnet-7 v7.2.0 + EIP-8037/EIP-7928 BAL/EIP-8246 Review + EIP-7708 dependency patch integration. Immediately after ACDT #081 (5/28 estimated) or early June.
  • Hegota devnet-0 launch -- FOCIL #034 note explicitly states "stabilizing on Glamsterdam-devnet-4 basis within 1~2 weeks then ~1 week launch" — 5/26 ~ 6/2 window. First official devnet for EIP-7805 CL Headliner.
  • EIP-7904 final benchmarking result -- explicit end-of-month (5/29~5/31) deadline. Depending on the result, Glamsterdam devnet-5 inclusion will be finalized.
  • PQ Devnet-5 progress -- PQI #040 (5/20) result undisclosed / if the aggregate block proof PR passes, discussion of mainnet transition schedule accelerates.

Governance / Operations

  • 5/28 ACDC #179 — full Hegota track specification decision call -- officialization of EIP-7805 FOCIL CL Headliner devnet-0 launch ETA + follow-up decisions on EIP-7716·EIP-8205·EIP-8188·EIP-8182 CFI + AA track unification scenario (EIP-8141 Hegota considered).
  • Lido Snapshot vote June entry ETA -- SDVTM Wind-Down main Snapshot entry (quorum/approval ratio undisclosed) + timing of IDVTC operator type ICS score framework integration. Lido X pre-amplification expected at the end of May.
  • Follow-up on the Kelp-specific one-off use case -- monitor whether the DAO threshold 1% exception approval case enters the stage of codifying future first-loss activation rules.
  • EarnETH Vault unfreeze confirmed on day 30 (Kelp 4/22 freeze → 5/22 — day 30) -- explicit resumption after 27 days of operational suspension (Kelp post-mortem body) — effectively resolved by the end of this week.

Monitoring Bulk Resolution of Official Note Publication Delays

ACDC #178 (D+8) / ACDT #080 (D+4) / RPC #026 (D+4) / AWD #039 (D+2) / P2P #001 (D+2) / PQI #040 (D+2) / ACDE #237 (D+1) — 6 unpublished items. The single FOCIL #034 publication (5/21 @jihoonsong) is an exemplary case of timely publication two days earlier as input to ACDE #237 decisions. Bulk publication may occur immediately after the 5/25~5/29 call window. Immediately read the ACDE #237 body for the EIP-7904 removal decision + official EIP-4758 CFI record + EIP-8188/EIP-8182 presentation text.

Technical Risk Monitoring

  • Client release gap entering the 50-day range -- accumulated Geth / Lighthouse CRITICAL advisories + monitor GitHub Releases for EL/CL releases supporting Glamsterdam devnet-5 after ACDT #081 (5/28 estimated) (EIP-8037 / EIP-7928 BAL / EIP-8246 / EIP-7708 implementation tags).
  • EIP upgrade status (forkcast) data integrity pagination normalization on 5/22 after 19 days of LEVEL 3+ -- follow-up verification of fetch logic fix required (consistency of daily automatic fetch results from 5/23~5/29). Confirm whether the first normal 5/22 snapshot (557 EIPs) remains stable afterward.
  • EIP-7904 vs EIP-7954 identity verification -- at this week's note time, the EIP-7904 entity note records 'Compute Gas Cost Increase', but the 5/21 call note describes 'contract code size' — possibility of entity note update or EIP number reassignment. Monitor clarification at 5/28 ACDC #179 or the next ACDT.
  • EL peer composition drift follow-up -- when the 5/20 P2P Networking #001 notes are published, closely read cell-level deltas / sparse blobpool decision content + possibility of Stereum Labs 36-node fleet week-3 measurement.
  • EIP-1559
  • EIP-4337
  • EIP-4844
  • EIP-6110
  • EIP-7251
  • EIP-7594
  • EIP-7610
  • EIP-7732
  • EIP-7778
  • EIP-7843
  • EIP-7851
  • EIP-7892
  • EIP-7976
  • EIP-7981
  • EIP-8024
  • EIP-8025
  • EIP-8148
  • EIP-8151

Sources

Daily Briefings

  • 2026-05-18 Daily Briefing -- ACDC #179 (5/28) "Glam / Hegota" agenda officialized + Lido Snapshot 5-item close day + ACDT #080 + RPC Standards #026
  • 2026-05-19 Daily Briefing -- Simple DVT Module Wind-Down (72 regular clusters 7/1) + IDVTC creation + Mini-Blocks SSV-Backed Sub-Slot Auctions + SenseiNode Incident Report 1.224 ETH
  • 2026-05-20 Daily Briefing -- EIP-7688 five-commit concentration (Fusaka rebase + Validator Container retention) + Lido Q1 2026 quarterly report (CSM 7.05%) + first P2P Networking #001 meeting
  • 2026-05-21 Daily Briefing -- Vitalik short-term privacy roadmap tweet + Devcon 8 Mumbai "privacy" keyword + ACDE #237 same day + Kelp post-mortem follow-up

This Week's Analysis Notes

  • 2026-05-22 Roadmap Analyst -- EIP-7928 CREATE/no-op + EIP-8246 Review + EIP-8268 / EIP-8256 / EIP-7954 / new pre-Spurious-Dragon EIP
  • 2026-05-22 Validator Ops -- Lido VaNOM Q1 2026 (CSM 7.05%) + Kelp Post-Mortem (2,644 ETH + 4-axis risk framework) + EIP-8268 / EIP-8256 + EIP-4758 Hegota Proposed
  • 2026-05-22 Infra Monitor -- EIP-7928 BAL CREATE edge case + PQ Interop #40 devnet5 + EIP-8256 Blob Streaming + EIP-4758 Hegota Proposed + EIP-7954 64KiB

Protocol Calls / Recommendations

Key External Sources

Previous Weekly Report

  • 2026-05-15 Weekly Report -- Svalbard Interop recap + EIP-7773 SFI 8 items + EIP-8261 24h promotion + Lido May 2026 Snapshot 5-item proposal

Written by: @r2jamong | 2026-05-22 (Friday ACDE #237 day 1 · weekly comprehensive report · 6 days before ACDC #179 on 5/28 · Hegotá devnet-0 launch ETA expected 5/29~6/5 · SDVTM Snapshot vote June expected 5/29~6/12)