# Jun 2026 — Week 3

*2026-06-15 ~ 2026-06-19*

---

# Weekly Ethereum Research Report (2026-06-15 ~ 2026-06-19)

## TL;DR

- **Bottom line**: ACDE #239 put Glamsterdam and Hegota on the agenda together, tying EIP-8282's entry into Considered, the Hegota PFI bundle, 6 Lido Snapshots, Erigon v3.4.4, and SSZ Engine API #1 into one week.
- **Numbers**: Over the 12 minutes from 6/18 14:40~14:52 UTC, commits landed for EIP-2780, EIP-8038, and EIP-8037, while the 6/18 forkcast dump recovered to 148 entries.
- **Action**: Operators should prioritize upgrading to Erigon v3.4.4 and Besu 26.5.0 or higher, tracking LIP-33/LIP-35 results, and following the 6/26 SSZ Engine API Breakout #1.

## Top 3 Takeaways

1. **[HIGH] ACDE #239 (6/18) carried a joint "Glamsterdam · Hegota" agenda -- closing a 14-day ACDE gap, adding EIP-8282 to Glamsterdam Considered, and triggering a 12-minute multi-EIP commit burst right after the call.**

    6/18 14:00 UTC [ACDE #239 issue 2115](https://github.com/ethereum/pm/issues/2115) (facilitator @nixorokish, 90 minutes) closed the 14-day gap since ACDE #238 (6/4), and put Glamsterdam EL scoping and Hegota EL scoping on the same agenda. The core item was the new entry of EIP-8282 'Builder Execution Requests' into Glamsterdam Considered. After ACDT #83 concluded that the EIP-8254 simple deposit cap was insufficient, ACDE #239 adopted a separate contract-deployment path based on EIP-7685 request types 0x03/0x04. However, Considered is a review stage, not confirmation of inclusion. The call also covered EIP-7928 BAL State-Access Restructuring, the proposal to add EIP-8189 "snap/2 - BAL-Based State Healing" to the Glamsterdam networking section, new Hegota PFI agenda items for EIP-8304 'Trustless log and transaction index' PFI and EIP-2488 CALLCODE deprecation PFI, and feedback on mempool encryption EIP-8105/EIP-8184. On 6/17, [`commit 37c28f7`](https://github.com/ethereum/EIPs/commit/37c28f7661b81585d9015b8bedb38dcd0e3cea3c) added EIP-8131 (Unified Transaction Content Floor), EIP-8146, and EIP-8250 to the PFI list in the EIP-8081 Hegota Meta EIP body, making it first clearly visible that the Hegota EIP candidate set had expanded from a single item (EIP-4758) to 4. EIP-8131 was published on 6/15 and then had its spec fully rewritten in [`commit cf5b8d9`](https://github.com/ethereum/EIPs/commit/cf5b8d9c0fd80dfc9d737135902b149ea64f6061) on 6/17; 'Unified' points to a possible combined floor across calldata + storage writes + initial-actor slot writes. This forms the third-generation track from EIP-1559 → EIP-7623 → EIP-7976 → EIP-8131. Immediately after the call, in the 12-minute window from 14:40~14:52 UTC, commits landed consecutively for EIP-2780 ([`55fda83`](https://github.com/ethereum/EIPs/commit/55fda83), full rewrite as "resource-based intrinsic transaction gas"), EIP-8038 ([`803ee8d`](https://github.com/ethereum/EIPs/commit/803ee8d), preliminary numbers added), and EIP-8037 ([`bee14641`](https://github.com/ethereum/EIPs/commit/bee14641d13e369e1c0418757eedf2eb0f04e0ac), EIP-7928 BAL conflict resolution + state-gas refund origin routing). This is a rare case of call decisions being reflected in the spec immediately, and a signal that the Glamsterdam "gas calculation model realignment" bundle is converging at call cadence.

2. **[HIGH] Lido saw a simultaneous burst of 6 active Snapshots (LIP-35 + LIP-33 + Simple DVT Wind Down + Galaxy v1→v2) plus a 6/25 Community Call announcement -- making the curated operator entry matrix visible in earnest and moving `0x02` credential operations into productionization.**

    On 6/15, the [LIP-35 SRv3 Snapshot](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x8fdec5d2cb70f8a266c4f5a269051fcfa985fab0f66cbe747702719d7433f606) (14:57 UTC, 4th day after 6/15 posting) and [LIP-33 CMv2/CSMv3 Snapshot](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7b07bc31f0b38b69a117473031bc126becc70b9fa37246b53d9fe5a841c814f5) (11:51 UTC, 4th day after 6/15 posting) were posted. LIP-35 reorganizes the Lido Core routing layer and integrated routing across the Curated/CSM/SimpleDVT modules through Staking Router v3. LIP-33 explicitly adopts the `0x02` withdrawal credential and enters EIP-7251 compounding validator operationalization. The key point is consolidated operation of up to 2048 ETH under a single key. The Simple DVT Module Wind Down 72 regular cluster posted on 6/12 matches the hypothesis of a phased shutdown of the existing SimpleDVT track and a transition to IDVTC + cSSV. The first Galaxy NO Curated v1→v2 migration case posted on 6/12 foreshadows the same migration pattern for other Curated operators (~37). Nemo Director and wstETH bridge revoke also remained 7th-day items after 6/12 posting, with wstETH bridge revoke covering revocation of bridge permissions across 9 chains. As a result, the simultaneous rework package across the three Curated/CSM/SimpleDVT modules became visible in earnest; LIP-33/LIP-35 are estimated to close on 6/22, and the four items posted on 6/12 reached their first close-candidate window on day 7. On 6/18 04:59 UTC, [@LidoFinance 2067472274](https://x.com/LidoFinance/status/2067472274366849184) announced the 6/25 Lido Community Call. The agenda is "what's next for Lido staking modules", "Lido's recent Web3SOC certification", and "guest sessions on client diversity". These point respectively to post-result follow-up for LIP-33/LIP-35 plus visibility into the Curated v2 migration roadmap, an institutional trust signal [Web3SOC definition/issuer/scope requires further verification], and an NO-side client-diversity policy baseline. A 7-day connected governance burst window formed from this week, day 4 after Snapshot posting, into next week, 6 days before the Community Call. The research team's entry matrix is reinforced across three windows: July post-case learning from Galaxy, Period 1.5 in October-December, and after full CMv1 termination in 2027 Q1. Daily channels (blog/research) had no new posts across all of W25 for the 7th day, but Snapshot/Twitter channels burst. This is the first confirmation of a dual governance-channel structure, and Snapshot-channel priority should be raised into SOP.

3. **[HIGH] New infra trio -- Erigon v3.4.4 'Splashing Saga' emergency patch for post-reorg gas mismatch + Rocket Pool Smart Node v1.20.4 Flashbots close option + SSZ Engine API Breakout #1 (6/26) confirmed — late-June operations-stack realignment cycle.**

    On 6/18 19:28 UTC, [@ErigonEth 2067690980](https://x.com/ErigonEth/status/2067690980912906603) announced the Erigon v3.4.4 "Splashing Saga" bugfix release. The content is "Another post-reorg gas used mismatch case, by pruning the in-RAM overlay", fixing a gas accounting mismatch after chain reorgs on v3.4.3 and below. It is recommended for all node operators. In the v3.4.x series, state-management bugs were found consecutively from the v3.4.1 segfault to the v3.4.4 gas mismatch, suggesting a structural review is underway, and the 28-day client-release gap also ended. On 6/17 21:01 UTC, [@Rocket_Pool 2067352014](https://x.com/Rocket_Pool/status/2067352014003282059) announced Rocket Pool Smart Node v1.20.4 high-priority. The core items are immediate response for minipool operators, client updates, bug fixes, and a new option to close minipools through Flashbots. This is the first external LST case using a private orderflow path, and the possibility of the same option being introduced on the Lido SimpleDVT/Curated side should be monitored. On 6/18, ethereum/pm PR [#2127](https://github.com/ethereum/pm/pull/2127) created the SSZ Engine API call series, alongside PR #2125 adding RazorClient/Tamaghna membership. On 6/19, [ethereum/pm #2132](https://github.com/ethereum/pm/issues/2132) and [ethereum-magicians 28832](https://ethereum-magicians.org/t/ssz-engine-api-1-june-26-2026/28832) confirmed the first official call for 6/26 13:00 UTC. This is the first official coordination for the REST-SSZ Engine API layer's spec/tests/implementation, and it enters the track of overhauling serialization for core messages such as newPayload/forkchoiceUpdated. Impact is expected for JSON-based block explorers and MEV relay infrastructure. This week's call cluster totaled 5: ACDT #83 and RPC Standards #28 on 6/15, FOCIL Breakout #36 on 6/16, PQI #44 on 6/17, and ACDE #239 on 6/18. Besu CVE-2026-34480/34478 remains unpatched for 29+ days (HIGH ongoing), and accumulating security exposure for nodes below 26.5.0 directly maps to slashing risk for staking operators.

---

## 1. Roadmap / Upgrade Change Highlights

### ACDE #239 handled "Glam · Hegotá" as a joint agenda and closed a 14-day ACDE gap

| Agenda | Result / Status | Source |
|------|-----------|------|
| EIP-8282 CFI (ePBS builder deposit scheme) | New entry into Glamsterdam Considered | ACDE #239 + 6/19 forkcast dump |
| Proposal to add EIP-8189 "snap/2 - BAL-Based State Healing" to the Glamsterdam networking section | Draft (not listed in any fork) | ACDE #239 agenda |
| EIP-7928 BAL State-Access Restructuring discussion | Glamsterdam Scheduled reaffirmed | ACDE #239 + 6/18 [`bee14641`](https://github.com/ethereum/EIPs/commit/bee14641d13e369e1c0418757eedf2eb0f04e0ac) |
| EIP-8037 status + EIP-7904 Compute Gas Cost presentation | Glamsterdam Scheduled (8037) / Considered (7904) | ACDE #239 |
| Hegota EIP-8304 PFI (Trustless log and transaction index) | Newly listed as PFI (no forkcast stage assigned) | ACDE #239 agenda |
| Hegota EIP-2488 PFI (CALLCODE deprecation) | Newly listed as PFI | ACDE #239 agenda |
| Mempool encryption EIP-8105 / EIP-8184 feedback | Feedback stage | ACDE #239 |

- The first ACDE of the week after a 14-day gap ended the longest gap since ACDE #238 (6/4), and handled Glam EL scoping and Hegota EL scoping on the same agenda. This is the first case where the Hegota track entered the main ACDE agenda in earnest.
- The call notes body had not yet been published as of 6/19, so decisions should be checked during the 6/19~21 publication window.

### The 12-minute multi-EIP commit burst after the call suggests faster spec convergence

| Time (UTC) | EIP | Commit | Change Summary | Fork Stage |
|-----------|------|--------|-----------|----------|
| 6/18 14:40 | EIP-2780 | [`55fda83`](https://github.com/ethereum/EIPs/commit/55fda83) | Fully rewritten as "Resource-based intrinsic transaction gas" (decomposes the 21k default) | Glamsterdam Considered (acde/226, 2025-12-18) |
| 6/18 14:45 | EIP-8038 | [`803ee8d`](https://github.com/ethereum/EIPs/commit/803ee8d) | Preliminary numbers added (STORAGE_WRITE +257%, etc.) | Glamsterdam Considered (acde/226, 2025-12-18) |
| 6/18 14:52 | EIP-8037 | [`bee14641`](https://github.com/ethereum/EIPs/commit/bee14641d13e369e1c0418757eedf2eb0f04e0ac) | EIP-7928 BAL conflict resolved + state-gas refund origin routing redefined | Glamsterdam Scheduled (acde/236, 2026-05-07) |

- After the call ended at 14:00 UTC, commits for three EIPs followed over the 12 minutes from 14:40~14:52 UTC. The commit sequence makes explicit that the three EIPs are a Glamsterdam "gas calculation model realignment" bundle, and this is interpreted as the first clear example of a pattern where call decisions are immediately reflected in specs (HIGH confidence).
- The differentiated research topic card is "Glamsterdam gas model realignment bundle: precise decoding of EIP-7928 BAL + EIP-8037 state-gas + EIP-2780 resource-based intrinsic + EIP-8038 state-access". There are 0 Korean-language comprehensive analyses of this spec convergence analysis.

### Hegota track expansion from single item to 10+ items was the largest roadmap change this week

| Stage | 6/15 (Mon) | 6/19 (Fri) | Delta |
|------|-----------|-----------|------|
| Scheduled | -- | **EIP-7805 FOCIL** | **+1 new** (moved from the Glamsterdam Declined track to Hegota Scheduled) |
| Considered | -- | **EIP-8141** | **+1 new** (Frame TX) |
| **Proposed** | EIP-4758 (1 item, alone for 25 days) | **EIP-4758, 7645, 7709, 7716, 8025, EIP-8148, EIP-8182, EIP-8188, EIP-8205, 8253 (10 items)** | **+9 new** |
| Withdrawn | -- | EIP-8105 | +1 (mempool encryption) |
| Declined | -- | 7807, EIP-8184 | +2 |
| PFI (meta EIP body) | -- | **EIP-8131 + EIP-8146 + EIP-8250 + EIP-8304 + EIP-2488** | **+5 new** (no forkcast stage assigned, awaiting ACDE adoption) |

- On 6/17, [`commit 37c28f7`](https://github.com/ethereum/EIPs/commit/37c28f7661b81585d9015b8bedb38dcd0e3cea3c) added EIP-8131/EIP-8146/EIP-8250 to the PFI list in the EIP-8081 Hegota Meta EIP body. The PFI bundle was formally listed right before ACDE #239, and this is the first clear signal that the Hegota EIP candidate set expanded from a single item to 4.
- On 6/17, [`commit cf5b8d9`](https://github.com/ethereum/EIPs/commit/cf5b8d9c0fd80dfc9d737135902b149ea64f6061) fully rewrote EIP-8131 'Unified Transaction Content Floor'. It formed a 3-day flow from 6/15 publication, to 6/17 spec reconstruction, to 6/17 PFI listing, to 6/18 ACDE. 'Unified' is interpreted as a possible integrated floor for calldata + storage writes + initial-actor slot writes (when combined with the EIP-8130 policy clarification + slot-writes charging commit).
- A **third-generation floor track formed from EIP-1559 base fee → EIP-7623 calldata cost increase (Pectra Included) → EIP-7976 calldata floor (Glamsterdam Scheduled) → EIP-8131 unified content floor**.
- EIP-7805 FOCIL surfaced in this week's forkcast dump as Hegota Scheduled after being treated as Glamsterdam Declined at acde/227 in January. This confirms that the FOCIL track was retargeted from Glamsterdam to Hegota, and it is also consistent with the restart of FOCIL Breakout #36 on 6/16 after 14 days.

### New EIPs / retry tracks accumulated post-Pectra Privacy/AA/Index tracks

| EIP | Source | Track / Meaning |
|-----|------|------------|
| **EIP-8304 'Trustless log and transaction index'** | 6/17 [ethereum-magicians #28824](https://ethereum-magicians.org/t/eip-8304-trustless-log-and-transaction-index/28824) Draft | **"much simpler" retry track** for the same project as EIP-7745 (acde/227 2026-01-05 Glamsterdam Declined) — listed as Hegota PFI at ACDE #239 — directly tied to EL client RPC performance (log index change) |
| **EIP-8130 AA direction refinement** | 6/18 [`0b95b99`](https://github.com/ethereum/EIPs/commit/0b95b996513a51b9871cee32e5be31b3b6173dd7) + [`ec10dd9`](https://github.com/ethereum/EIPs/commit/ec10dd9989ebb5698ccb6975a4e6b20a1f2d2450) | (i) self-actor secp256k1 setting stored inline in an account-state slot, (ii) default-EOA revocation folded into a state flag — post-EIP-7702 EOA→AA path — state-tree cost reduction for an account-configuration-based AA model |
| **Block Access List Byte Floor** (number TBD draft) | 6/18 11:03 UTC [`ea5fef0`](https://github.com/ethereum/EIPs/commit/ea5fef04d97b7ba3349dc87196cff01fe97169dc) | EIP-7928 BAL follow-up / sister proposal — may supplement gas/size constraints for the Glamsterdam BAL package |
| **EIP-8189 "snap/2 - BAL-Based State Healing"** | ACDE #239 agenda (Draft) | Signal that EIP-7928 BAL is expanding from a single EIP into a wire-protocol (snap/2, eth/71) family |

---

## 2. EIP Status Changes (Monday 6/15 vs Friday 6/19)

> Data integrity signal: this week the Forkcast dump went through a 3-day sawtooth → full-scale restoration cycle: 6/12 14 entries → 6/15 19 entries → 6/16 14 entries → 6/18 148 entries (+134 jump). The 6/15 dump was a partial fetch only for EIPs at or below 6466, and the 6/16 dump was a partial fetch at or below 6188. Therefore, the 6/18 baseline (148 entries) is adopted as this week's official baseline, and the 6/15 baseline is downgraded due to the history-fetch range limit. Since most surface changes are byproducts of dump-build normalization, the cross-check result isolating only substantive stage changes is as follows:

### 6/15 (Mon) → 6/19 (Fri) `summary` substantive changes

| Track / Stage | 6/15 (Mon, partial fetch) | 6/19 (Fri, full 148 entries) | **Substantive Change (Interpretation)** |
|------------|--------------------------|---------------------------|---------------------|
| Dencun Included | [4844] | [4844] | Same |
| Pectra Included | [2537, 2935] | [2537, 2935, 6110, 7002, 7251, 7549, 7623, 7642, 7685, 7691, 7702, 7840] | Dump normalization byproduct (already mainnet-active EIPs) |
| **Fusaka Included** | Not exposed in dump (6466 or lower) | **[7594, 7642, 7823, 7825, 7883, 7892, 7910, 7917, 7918, 7934, 7935, 7939, 7951]** | Dump normalization + **reconfirmation of EIP-7934 / EIP-7935 Final status** |
| **Glamsterdam Scheduled** | Not exposed in dump | **[7708, 7732, 7778, 7843, 7928, 7954, 7976, 7981, 8024, 8037] (10 items)** | Dump normalization + 0 substantive changes |
| **Glamsterdam Considered** | [2780] (1 item) | [2780, 7610, 7688, 7904, 7975, 7997, **8038, 8045, 8061, 8070, 8080, 8136, 8159, 8246, 8282**] (15 items) | **EIP-8282 newly entered Considered (ACDE #239)** + the rest are dump normalization byproducts |
| Glamsterdam Declined | [2926, 5920, 6466] (3 items) | 38 items (large expansion, EIP-7805 excluded after moving to Hegota Scheduled) | Dump normalization + **EIP-7805 FOCIL move (actual change)** |
| Glamsterdam Withdrawn | Not exposed in dump | [6873, 7667, 7919, 7999] (4 items) | Dump normalization byproduct |
| Glamsterdam Proposed | Not exposed in dump | **[8254]** (1 item) | Dump normalization byproduct (EIP-8254 was effectively replaced by EIP-8282 after ACDT #83 concluded that the simple deposit cap was insufficient) |
| **Hegota Scheduled** | -- | **[7805]** | **New EIP-7805 FOCIL move, the biggest substantive change this week** |
| **Hegota Considered** | -- | **[8141]** | New Frame TX listing |
| **Hegota Proposed** | [4758] (1 item) | [4758, **7645, 7709, 7716, 8025, EIP-8148, EIP-8182, EIP-8188, EIP-8205, 8253**] (10 items) | **+9 substantive expansion — first signal of full Hegota track expansion** |
| **Hegota Withdrawn** | -- | **[8105]** | Mempool encryption track cleanup |
| **Hegota Declined** | -- | **[7807, EIP-8184]** | Partial cleanup of mempool encryption LUCID follow-ups |

### This week's reliable actual stage changes (cross-verified across calls / commits / external primary sources)

**Substantive EIP track changes (HIGH confidence)**

1. EIP-8282 'Builder Execution Requests' newly entered Glamsterdam Considered at ACDE #239 (6/18). The decision trajectory from ACDT #83 to ACDE #239 resolves as confirmation of EIP-8254's limitations followed by adoption of the EIP-7685 0x03/0x04 separate-contract path.
2. EIP-7805 FOCIL moved from Glamsterdam Declined (acde/227, 2026-01-05) to Hegota Scheduled. This explicitly retargets the FOCIL track and is consistent with FOCIL Breakout #36 on 6/16 closing a 14-day gap.
3. Hegota Proposed expanded from only 4758 to 1 → 10 items after +9 additions. With Considered EIP-8141 and PFI meta listings EIP-8131/EIP-8146/EIP-8250/EIP-8304/EIP-2488, the Hegota EIP candidate set took formal track shape for the first time this week.

**EIP meta / body changes (reconfirming the meta EIP commit > forkcast dump authority pattern)**

- 6/17 [`commit 37c28f7`](https://github.com/ethereum/EIPs/commit/37c28f7661b81585d9015b8bedb38dcd0e3cea3c) added EIP-8131 + EIP-8146 + EIP-8250 to the PFI list in the EIP-8081 Hegota Meta EIP body.
- 6/17 [`commit cf5b8d9`](https://github.com/ethereum/EIPs/commit/cf5b8d9c0fd80dfc9d737135902b149ea64f6061) fully rewrote EIP-8131 'Unified Transaction Content Floor'.
- In the 6/18 12-minute commit burst, EIP-2780 + EIP-8037 + EIP-8038 were updated together.
- 6/18 [`commit 0b95b99`](https://github.com/ethereum/EIPs/commit/0b95b996513a51b9871cee32e5be31b3b6173dd7) + [`ec10dd9`](https://github.com/ethereum/EIPs/commit/ec10dd9989ebb5698ccb6975a4e6b20a1f2d2450) reflected EIP-8130 secp256k1 inline storage + EOA flag fold.

**New EIP registration / Draft**

- EIP-8304 'Trustless log and transaction index' is a 6/17 ethereum-magicians #28824 Draft and a retry of EIP-7745. It was listed in Hegota PFI at ACDE #239.
- EIP-8189 "snap/2 - BAL-Based State Healing" is a Draft from the ACDE #239 agenda and a BAL wire-protocol expansion.
- **Block Access List Byte Floor** (6/18 [`ea5fef0`](https://github.com/ethereum/EIPs/commit/ea5fef04d97b7ba3349dc87196cff01fe97169dc), number TBD).
- **Lean Staking EIP PR [#11500](https://github.com/ethereum/EIPs/pull/11500)** (EIP Editing Office Hour #102 agenda, awaiting EIP number assignment, ACDE #239 follow-up).

---

## 3. Validator / Infra Key Issues

### Lido Snapshot 6-item simultaneous burst made the curated operator entry matrix visible in earnest

| Snapshot | Posted | Estimated Close | Core | NO Entry Implication |
|----------|------|----------|------|-------------|
| **[LIP-35 SRv3](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x8fdec5d2cb70f8a266c4f5a269051fcfa985fab0f66cbe747702719d7433f606)** | 6/15 14:57 UTC | 6/22 (4th day after 6/15 posting) | **Staking Router v3** — Lido Core routing layer rework + integrated routing changes for Curated/CSM/SimpleDVT modules | For new entry, stake allocation model baseline may change + need to check the body for module priority / stake share cap / withdrawal queue model |
| **[LIP-33 CMv2/CSMv3](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7b07bc31f0b38b69a117473031bc126becc70b9fa37246b53d9fe5a841c814f5)** | 6/15 11:51 UTC | 6/22 (4th day after 6/15 posting) | **Explicit adoption of `0x02` withdrawal credential — EIP-7251 compounding validator operationalization** (consolidated operation of up to 2048 ETH under a single key) | **Fundamental infra/operations-structure change** for Curated operators (validator count decreases + ETH operated per single key increases + slashing exposure concentration changes [further verification]) — mandatory pre-verification for new Curated entry candidates (devnet/testnet operating experience) |
| **Simple DVT Wind Down 72 cluster** | 6/12 08:47 UTC | 6/19 (7th day after 6/12 posting, first close candidate) | Phased wind-down of existing SimpleDVT track → matches IDVTC + cSSV transition hypothesis | Full reconfiguration of the Lido DVT track matrix — transition matrix from existing cluster → IDVTC (lido-research 11649) + cSSV Syndicate Boost + CMv2 3 tracks |
| **Galaxy NO Infrastructure Update** | 6/12 07:31 UTC | 6/19 (7th day after 6/12 posting) | **First Curated v1→v2 migration case** | Signals the same migration pattern for other Curated operators (~37) + moment when NO entry candidates should prepare the v2 infra baseline in advance + learning window for validator + signing stack reconstruction patterns |
| Nemo Director | 6/12 | 6/19 | General governance | New director appointment — follow-up from the 6/5 weekly report |
| wstETH bridge revoke | 6/12 | 6/19 | Revocation of bridge permissions across 9 chains | General governance |

- The simultaneous rework package across the three Curated/CSM/SimpleDVT modules became visible in earnest. The first verification of the 6/5 weekly report ETA (July mainnet / October-December Period 1.5 / 2027 Q1 full CMv1 termination) has begun.
- The dual governance-channel structure was confirmed for the first time. Daily channels (blog/research) had no new posts across all of W25 for the 7th day, but Snapshot/Twitter channels showed a burst. The 6/16 note's "possibility of a new burst in late W25" materialized on the Snapshot channel, so monitoring-channel priority should be realigned and Snapshot-channel priority escalation should become SOP.

### Lido Community Call 6/25 announcement connects this week's burst into next week

6/18 04:59 UTC [@LidoFinance 2067472274](https://x.com/LidoFinance/status/2067472274366849184):

- (1) "what's next for Lido staking modules" points to post-result follow-up for LIP-33/LIP-35 Snapshot results and visibility into the Curated v2 migration roadmap.
- (2) "Lido's recent Web3SOC certification" is an institutional trust signal [further verification needed: Web3SOC definition/issuer/scope/evaluation criteria].
- (3) "guest sessions on client diversity" is an NO-side client-diversity policy baseline signal, leaving open the possibility that client-diversity SLA will be added to future entry evaluations.

A 7-day connected governance burst window formed from this week (4th day after 6/15 Snapshot posting) to next week (6 days before the 6/25 Community Call). NO entry candidates should start preparing in advance.

### Client / operations stack changes

| Component | This Week's Change | Impact | Recommendation |
|---------|----------|--------|------|
| **Erigon v3.4.4 'Splashing Saga'** | 6/18 19:28 UTC release | **HIGH new** | Fixes post-reorg gas used mismatch (in-RAM overlay pruning timing). **Recommended for all node operators**. State-management bugs have been found consecutively in the v3.4.x series (v3.4.1 segfault → v3.4.4 gas mismatch). Structural review is presumed necessary |
| **Rocket Pool Smart Node v1.20.4** | 6/17 21:01 UTC high-priority | HIGH | Immediate response for minipool operators + new Flashbots minipool close option is the first external LST case using private orderflow. Possibility of same option being adopted by Lido SimpleDVT/Curated |
| **SSZ Engine API Breakout #1 (6/26 13:00 UTC)** | 6/18 PR #2127 new call series + 6/19 #2132 / ethereum-magicians 28832 first call schedule confirmed | HIGH | First official coordination of EL-CL JSON → SSZ serialization transition. It is a track for a full change to serialization of core messages such as newPayload/forkchoiceUpdated, with impact on JSON-based block explorers/MEV relays/monitoring infrastructure. RazorClient/Tamaghna in charge |
| **execution-apis v1.0.0-beta.7** | 6/15 RPC Standards #28 release result | MEDIUM | txpool namespace standardization PR #353 + engine_forkchoiceUpdatedV4 PR #608 + JSON-RPC error code PR #823/#784 + eth_baseFee PR #795. Track spec adoption by the 4 EL clients (Geth/Nethermind/Besu/Erigon) |
| **EF Clear Signing official launch** | 6/15 17:06 UTC | MEDIUM | HW/SW wallet integration + structural blocking of blind-signing attack vectors, raising the UX baseline for stakers/institutions. 0 direct EL/CL node impact, but possible medium-term design impact on MEV pipelines/transaction-simulation infrastructure |
| **Besu CVE-2026-34480/34478** | 29+ days unpatched (W25 +5 days) | **HIGH ongoing** | Security exposure is accumulating for nodes below 26.5.0, exploitation likelihood rises, and this directly maps to staking-operator slashing/double-sign risk. **Immediate upgrade to 26.5.0 or higher required** |
| **EL client baseline** | Geth v1.17.3 / Nethermind v1.37.2 / Besu 26.5.0 / **Erigon v3.4.4 new** / Reth | MEDIUM | Need to monitor each client's implementation schedule following SSZ Engine API #1 results |
| **CL client baseline** | Lighthouse v8.1.3 / Prysm v7.1.3 / Teku 26.4.0 / Nimbus v26.5.0 / Lodestar v1.42.0 | MEDIUM | No new releases. SSZ Engine API #1 (6/26) results directly affect CL Engine API receiver implementations. Lodestar QUIC UDP port 9001 open recommendation continues |

---

## 4. Protocol Call Key Decisions (5-call cluster this week)

This week's call cluster consists of 5 calls: ACDT #83 (6/15), RPC Standards #28 (6/15), FOCIL Breakout #36 (6/16), PQ Interop #44 (6/17), and ACDE #239 (6/18). This was the highest monitoring-load window for the research team.

### ACDE #239 (6/18 14:00 UTC, [issue 2115](https://github.com/ethereum/pm/issues/2115), facilitator @nixorokish) -- notes unpublished as of 6/19

- **Public agenda**:
  - Glamsterdam devnet update status (@barnabasbusa)
  - **EIP-8282 CFI final review** (ePBS builder deposit scheme)
  - Proposal to add EIP-8189 to the Glamsterdam networking section
  - EIP-7928 State-Access Restructuring discussion
  - Gas repricing update: EIP-8037 status, EIP-7904 Compute Gas Cost presentation
  - **Hegota agenda: EIP-8304 PFI + EIP-2488 PFI**
  - Mempool encryption EIP-8105 / EIP-8184 feedback
- In post-call EIP repo updates (14:40~14:52 UTC 12-minute burst), EIP-2780 / EIP-8038 / EIP-8037 were updated together. This is a case of immediate spec reflection of call decisions.

### ACDT #83 (6/15, [issue 2116](https://github.com/ethereum/pm/issues/2116)) -- notes partially public

- Glamsterdam-devnet-5 completed peering + fork-choice bug fixes.
- Glamsterdam-devnet-6 is planning toward large-scale EL EIP integration.
- bal-devnet-7 is for EL benchmarking and is a v7.3.2 release with Prague included.
- EIP-8282 includes a separate builder deposit path based on EIP-7685 0x03/0x04, need for Engine API extension, system contracts, and vanity address decision discussion. EIP-8254 (simple cap) was concluded to be insufficient and was handed off to the ACDE #239 CFI decision.
- SSZ Engine API (EL side) is identifying blockers to implementing execution-apis PR #793, and a 3rd CL volunteer is needed.
- **Gas repricing discussion**: EIP-2780 rework (decomposition of the 21k default) + EIP-8037 status (block-gas inclusion check needed) + EIP-8038 initial state access costs (STORAGE_WRITE +257%, etc.).
- **ePBS CL fork choice**: `get_proposer_head` ForkChoiceNode handling + interop impact from PENDING parent-support calculation logic.

### RPC Standards #28 (6/15, [issue 2120](https://github.com/ethereum/pm/issues/2120)) -- partially public

- **execution-apis v1.0.0-beta.7 release**.
- **Scheduled to close**: txpool namespace standardization PR #353 + engine_forkchoiceUpdatedV4 PR #608.
- **In progress**: JSON-RPC error-code consistency PR #823 / #784 + `eth_baseFee` PR #795 + `testing_commitBlockV1` spec + `debug_trace` method opcode tracer standardization.

### FOCIL Breakout #36 (6/16 13:00 UTC, [issue 2121](https://github.com/ethereum/pm/issues/2121)) -- notes unpublished

- Closed a 14-day gap after Breakout #35 on 6/2, and checked three axes of EIP-7805 FOCIL Development / Spec / Testing updates.
- EIP-7805 had Glamsterdam Declined (acde/227, 2026-01-05) status, but Breakout continued operating. Its surfacing as Hegota Scheduled in this week's forkcast dump is a substantive change.

### PQ Interop #44 (6/17 14:00 UTC, [issue 2128](https://github.com/ethereum/pm/issues/2128)) -- notes unpublished

- The public agenda is discussion of devnet5 + leanspec refactor.

### ACDC #180 (6/11) -- previous call just before this week, notes unpublished for 7 days cumulatively

- **Glamsterdam devnet-5 + Deathstar bug + Devnet-6 plan**.
- **QUIC mandate** (consensus-specs PR #5330) + Lighthouse Mplex disabled.
- **Proposer Preferences API** (beacon-APIs PR #608).
- **Hegota EIP-8243**: source-stage attestation batching.

---

## 5. Recommended Topic Status This Week (8 items) + Priority Authoring Selection

This week's 8 daily recommendations (2 per day × 4 days):

| Day | Recommendation 1 | Recommendation 2 |
|---|--------|--------|
| 6/15 (Mon) | RPC Standards #28 D-Day (txpool standardization) | Develp Post-Mortem 11603 D+17 |
| 6/16 (Tue) | FOCIL Breakout #36 D-Day | EF Clear Signing official launch |
| 6/18 (Thu) | Lido Snapshot 4-item simultaneous burst | ACDE #239 'Glam · Hegotá' + Hegota PFI bundle |
| 6/19 (Fri) | **EIP-8282 Builder Execution Requests** precise decoding | **Lido LIP-33 `0x02` credential (EIP-7251 compounding)** |

### Priority authoring selection (combined timeliness / uniqueness / institutional / info_gap weighting)

**Tier 1 -- 4 items directly tied to this week ~ next week window**:

1. **"LIP-33 + LIP-35 package analysis: impact of simultaneous Lido Core routing + Curated/CSM module upgrades on NO entry"** ([6/18 recommendation 1 + 6/19 recommendation 2 combined])
      - **Timing rationale**: 4th day after Snapshot posting → estimated 6/22 close + just before the 6/25 Lido Community Call, so this is the authoring point for result capture + post-result decoding.
   - **Category**: Report (in-depth report) -- 4,500~5,500 characters / high difficulty.
   - **Owner**: Validator Ops primary draft + Roadmap Analyst (EIP-7251 compounding alignment supplement).

2. **"EIP-8282 Builder Execution Requests + ePBS builder deposit scheme: ACDT #83 → ACDE #239 decision trajectory"** ([6/19 recommendation 1])
      - **Timing rationale**: 24-hour window the day after ACDE #239 + just before the estimated 7/2 ACDE #240 EIP-8282 CFI follow-up decision, so pre-alignment is needed.
   - **Category**: Issue (key issue) -- 3,500~4,500 characters / high difficulty.
   - **Owner**: Roadmap Analyst + Validator Ops (NO/builder perspective) + Protocol Calls Tracker (decision-trace reinforcement).

3. **"Learning from the first Galaxy Curated v1→v2 migration case + v2 infra baseline checklist for NO entry candidates"** ([6/18 recommendation 1 follow-up])
      - **Timing rationale**: Galaxy Snapshot reached the first close-candidate window on day 7 after posting, and the same migration pattern for other ~37 Curated operators was foreshadowed.
   - **Category**: Comment (weekly operations checklist) -- 2,500~3,500 characters / medium difficulty.
   - **Owner**: Validator Ops + Infra Monitor (signing stack reconstruction pattern).

4. **"First visibility of Hegota hard fork EIP scope: PFI cluster (EIP-8131 / EIP-8146 / EIP-8250 / EIP-8304 / EIP-2488) + Proposed 1→10 expansion analysis"** ([6/18 recommendation 2 expanded])
      - **Timing rationale**: 6/19~21 ACDE #239 call-note publication window + pre-alignment before 7/2 ACDE #240.
   - **Category**: Issue (key issue) -- 3,500~4,500 characters / high difficulty.
   - **Owner**: Roadmap Analyst + Protocol Calls Tracker.

**Tier 2 -- 3 items for next week's pre-publication window**:

5. "SSZ Engine API transition: JSON → SSZ serialization changes the EL-CL communication layer + impact on MEV relay/block explorers" ([6/19 recommendation 1 support)
   - **Timing rationale**: 6/26 Breakout #1 D-7 pre-analysis window.
   - **Category**: Issue / Comment -- 3,000~4,000 characters.

6. **"Glamsterdam gas model realignment bundle: precise decoding of EIP-7928 BAL + EIP-8037 + EIP-2780 + EIP-8038"** (post-call 12-minute commit burst analysis)
   - **Timing rationale**: Pre-analysis just before 6/22 ACDT #84 + 7/2 ACDE #240.
   - **Category**: Report -- 4,000~5,000 characters.

7. **"Lido DVT track reconfiguration matrix: Simple DVT wind down 72 → IDVTC + cSSV + CMv2 transition"** (carry, accumulated since the 6/12 note)
   - **Timing rationale**: Snapshot D+7 results + suitable pre-publication timing before the 6/25 Community Call.
   - **Category**: Report -- 4,000~5,000 characters.

**Tier 3 -- 1 item for monitoring / follow-up window**:

8. **"Lido Web3SOC certification + client diversity track: institutional trust signal + NO-side client-diversity policy baseline"** ([6/19 recommendation 2 support)
      - **Timing rationale**: Pre-analysis for the 6/25 Community Call agenda + need to confirm Web3SOC definition/issuer/scope in advance.
   - **Category**: Comment -- 2,500~3,500 characters.

---

## 6. Key Schedule Next Week (W26, 2026-06-22 ~ 06-26)

| Date | Time (UTC) | Event | Agenda / Core |
|------|----------|------|------------|
| **06/22 (Mon)** | -- | **Estimated close of Lido Snapshot LIP-33 + LIP-35** (D+7) | Determines passage of `0x02` credential adoption + Staking Router v3 routing rework |
| 06/22 (Mon) | 14:00 UTC (est.) | **ACDT #84** ([issue 2126](https://github.com/ethereum/pm/issues/2126)) | Glamsterdam devnet-6 progress + Hegota gas-model alignment follow-up |
| 06/24 (Wed) | 13:00 UTC | **Post Quantum TX Signature #11** ([issue 2124](https://github.com/ethereum/pm/issues/2124)) | PQ TX signature track progress |
| 06/24 (Wed) | 15:00 UTC | **Encrypt The Mempool #6** | LUCID design + framed TX + AA anon paymaster + CL team participation + EIP-8105 / EIP-8184 bounty follow-up |
| **06/25 (Thu)** | TBD | **Lido Community Call** ([@LidoFinance 6/18](https://x.com/LidoFinance/status/2067472274366849184)) | (1) "what's next for Lido staking modules" — post-result follow-up for LIP-33/LIP-35 + Curated v2 migration roadmap, (2) "Web3SOC certification" — institutional trust signal, (3) "guest sessions on client diversity" — NO-side client-diversity policy baseline |
| 06/25 (Thu) | (est.) | **ACDC #181 (biweekly cycle)** | Fusaka deployment schedule + PeerDAS activation + QUIC mandate follow-up |
| **06/26 (Fri)** | 13:00 UTC | **SSZ Engine API Breakout #1** ([ethereum/pm #2132](https://github.com/ethereum/pm/issues/2132) + [ethereum-magicians 28832](https://ethereum-magicians.org/t/ssz-engine-api-1-june-26-2026/28832)) | **First official coordination call for REST-SSZ Engine API layer specs/tests/implementation** (RazorClient/Tamaghna in charge), entering the track of fully changing newPayload/forkchoiceUpdated serialization |
| 07/01 (Wed) | 15:30 UTC | **P2P Networking #3** ([issue 2129](https://github.com/ethereum/pm/issues/2129)) | Chainscope (Csaba) presentation, with possible discussion of discv5 / libp2p parameter tuning |
| 07/02 (Thu) | 14:00 UTC (est.) | **ACDE #240** | EIP-8282 CFI follow-up decision + EIP-2488 PFI + EIP-8304 Glamsterdam scoping |

### Devnet milestones

- Glamsterdam-devnet-5 completed peering + fork-choice bug fixes (reported in ACDT #83 on 6/15).
- Glamsterdam-devnet-6 is planning toward large-scale EL EIP integration, and progress is expected to be presented at ACDT #84 (6/22).
- bal-devnet-7 is for EL benchmarking and is a v7.3.2 release with Prague included (reported in ACDT #83 on 6/15).

### Monitoring windows

- 6/19~21 ACDE #239 call-note body publication (normal window through day 3 after the call) -- capture items not reflected in the 6/19 dump.
- **6/19~22 Lido Snapshot 6-item result capture** (LIP-33/LIP-35 close on 6/22 + 4 items posted on 6/12 closing D+7~D+10).
- **Awaiting PQ Interop #44 (6/17) + FOCIL Breakout #36 (6/16) call-note body publication** (D+2~D+3 each).
- vitalikblog's 13+ consecutive days of silence as of 6/19 is a monitoring target for activity-resumption signals from 6/22 onward, and is a qualitative signal for Glamsterdam / Hegota roadmap visibility.

---

## Key Insights (W25 Summary)

### (1) The Hegota track took formal shape for the first time this week

- At the 6/5 weekly report point, 7 Hegota EL headliner candidates were listed on the ACDE #238 agenda (EIP-8131/8279/7979/8173/8222/7851/8151), and only EIP-4758 was Proposed alone.
- At the end of this week (W25, 6/19), Hegota had formed a 20+ item track: Proposed 1 → 10, Considered 1, Scheduled 1 (EIP-7805 FOCIL move), Withdrawn 1, Declined 2, and PFI 5 (listed in the meta EIP body).
- Between 6/4 ACDE #238 and 6/18 ACDE #239 (14 days), the Hegota EIP candidate set took formal track shape. This is the first trajectory verification of the 6/5 weekly report assumption ("4 author camps dispersed — equilibrium state").
- **Differentiated research topic**: "First visibility of Hegota hard fork EIP scope" (Tier 1 #4) has 0 Korean-language comprehensive analyses and is timely for pre-alignment before 7/2 ACDE #240.

### (2) Lido SRv3 + LIP-33 brought the first verification of this research team's entry matrix

- At the 6/5 weekly report point, LIP-35 had been proposed on 6/3, the timeline was explicit (late-June Snapshot → July mainnet → October Period 1.5 → December Period 2 → 2027 Q1 full CMv1 termination), and a new 3-window entry matrix had appeared.
- At the end of this week, LIP-33 + LIP-35 Snapshots were active on the 4th day after 6/15 posting, while the first Galaxy Curated v1→v2 migration case, Simple DVT Wind Down, and the 6/25 Community Call announcement were confirmed. The first trajectory verification of the 6/5 ETA arrived.
- Explicit `0x02` withdrawal credential adoption (LIP-33) means entry into EIP-7251 compounding validator operationalization. Because this is a fundamental change in Curated operator infra/operations structure, this research team's pre-verification (devnet/testnet operating experience) is required.
- Differentiated research topics are simultaneous authoring of "LIP-33 + LIP-35 package analysis" (Tier 1 #1) and "Galaxy v1→v2 migration learning" (Tier 1 #3).

### (3) A 12-minute post-call EIP burst was the first signal of faster spec convergence

- At the 6/5 weekly report point, the recommendation was to settle the authority-priority SOP of meta EIP commit > ACDE/ACDC call notes > dump changes.
- At the end of this week, ACDE #239 decisions were immediately reflected as EIP repo commits inside a 12-minute window. This means a new "post-call commit window" monitoring layer has appeared one level above the "meta EIP commit > call notes > dump" SOP.
- If this pattern recurs at ACDE #240 (7/2) and later ACDEs, spec convergence can be viewed as accelerating from call-level cadence to 12-minute post-call cadence. This becomes a candidate for automated alerting SOP and a new priority monitoring rule for the EIPs commit window (24 hours after call end).

### (4) Infra operations-stack realignment is concentrated in late June~early July

- Four things happened at the same time this week: (a) Erigon v3.4.4 emergency patch (recommended for all node operators), (b) Rocket Pool Smart Node v1.20.4 + Flashbots close option (first external LST private-orderflow case), (c) SSZ Engine API Breakout #1 (6/26) first official coordination, and (d) execution-apis v1.0.0-beta.7 + EF Clear Signing official launch.
- 6/26 SSZ Engine API #1 means the EL-CL communication layer JSON → SSZ serialization transition is entering execution. It creates impacts across all EL/CL client communication-layer implementations and a new migration matrix for JSON-based monitoring tools (block explorers, MEV relays).
- Infra-stack realignment items for NO entry candidates are (i) immediate Erigon v3.4.4 upgrade, (ii) immediate Besu 26.5.0 upgrade (29+ day CVE), (iii) evaluation of the Rocket Pool Flashbots close option (private orderflow introduction), and (iv) pre-alignment on the SSZ Engine API migration matrix. All recommendations occurred simultaneously this week.

---

## Priority Action Items (NO / Institutional Perspective)

### Immediate action required (first weekend ~ Monday next week)

1. **Erigon operating nodes → immediate upgrade to v3.4.4** (resolves post-reorg gas mismatch)
2. **Rocket Pool minipool operating nodes → immediate upgrade to Smart Node v1.20.4** + evaluate Flashbots close option
3. **Besu nodes below 26.5.0 → immediately upgrade to 26.5.0 or higher for CVE-2026-34480/34478 patching** (29+ days HIGH ongoing)
4. **Check Lido Snapshot LIP-33 / LIP-35 body + results** (4th day after 6/15 posting → estimated 6/22 close): capture module priority + stake share cap + withdrawal queue model + `0x02` credential operating details

### Weekend recommendations (priority authoring window)

- Enter simultaneous authoring for 4 Tier-1 research topics:
  - (1) "LIP-33 + LIP-35 package analysis"
  - (2) "EIP-8282 Builder Execution Requests + ePBS builder deposit scheme"
  - (3) "Learning from the first Galaxy Curated v1→v2 migration case"
  - (4) "First visibility of Hegota hard fork EIP scope"
- Check ACDE #239 call-note body (6/19~21 publication window) + verify 6/19~22 dump (whether Hegota EIP-8131 newly surfaces in a forkcast stage: PFI → Proposed promotion)
- Check PQ Interop #44 + FOCIL Breakout #36 + ACDC #180 notes (raise priority for direct ethereum/pm checks)
- Pre-secure the `0x02` withdrawal credential operational verification baseline (EIP-7251 compounding consolidation devnet/testnet experience)

### Advance preparation for next week (6/22 ~ 06/26)

- On 6/22 ACDT #84, monitor Glamsterdam devnet-6 progress + Hegota gas-model alignment follow-up.
- For the 6/25 Lido Community Call, pre-capture staking-modules roadmap + Web3SOC certification + client-diversity agenda messages, and confirm Web3SOC definition/issuer/scope in advance.
- Monitor the 6/26 SSZ Engine API Breakout #1: first official coordination of the EL-CL communication-layer SSZ transition spec → monitor NO-side client-pair compatibility matrix baseline realignment.
- Capture the final deadline window of the Develp Post-Mortem 11603 response trajectory after 21+ days since posting, and complete the final segment of the "Develp Post-Mortem learning checklist".

### Monitoring / Pending

- Monitor vitalikblog's 13+ consecutive days of silence for activity-resumption signals from 6/22 onward (qualitative signal for Glamsterdam / Hegota roadmap visibility).
- Confirm EIP upgrade-status dump stabilization by checking whether the 148-entry baseline holds from 6/22 onward (if sawtooth recurs, reconfirm the meta EIP commit priority authority SOP).
- For Lean Staking EIP PR [#11500](https://github.com/ethereum/EIPs/pull/11500), check the body after EIP number assignment (EIP Editing Office Hour #102 agenda).
- Monitor IDVTC (lido-research 11649) for possible entry-application guideline proposals in the 13~16-day window after posting.
- 7/2 ACDE #240 may cover EIP-8282 CFI follow-up + EIP-2488 PFI + EIP-8304 Glamsterdam scoping decisions.

---

## Sources

### Daily Briefings
- [2026-06-15 Daily Briefing](../daily/2026-06-15-briefing.md) -- W25 Monday ACDT #83 + RPC #28 double-call D-Day
- [2026-06-16 Daily Briefing](../daily/2026-06-16-briefing.md) -- W25 Tuesday FOCIL #36 D-Day + EF Clear Signing launch
- [2026-06-18 Daily Briefing](../daily/2026-06-18-briefing.md) -- W25 Thursday ACDE #239 D-Day + Lido Snapshot 4-item burst
- [2026-06-19 Daily Briefing](../daily/2026-06-19-briefing.md) -- W25 Friday ACDE #239 next-day check + new EIP-8282 Considered

### Domain Analysis Notes
- [Roadmap Analysis 6/15](../daily/2026-06-15-roadmap-analysis.md) / [6/16](../daily/2026-06-16-roadmap-analysis.md) / [6/18](../daily/2026-06-18-roadmap-analysis.md) / [6/19](../daily/2026-06-19-roadmap-analysis.md)
- [Validator Analysis 6/15](../daily/2026-06-15-validator-analysis.md) / [6/16](../daily/2026-06-16-validator-analysis.md) / [6/18](../daily/2026-06-18-validator-analysis.md) / [6/19](../daily/2026-06-19-validator-analysis.md)
- [Infra Analysis 6/15](../daily/2026-06-15-infra-analysis.md) / [6/16](../daily/2026-06-16-infra-analysis.md) / [6/18](../daily/2026-06-18-infra-analysis.md) / [6/19](../daily/2026-06-19-infra-analysis.md)
- [Protocol Calls 6/19 (W25 summary)](../daily/2026-06-19-protocol-calls.md)

### Daily Recommendations
- [6/15](../../recommendations/2026-06-15.md) / [6/16](../../recommendations/2026-06-16.md) / [6/18](../../recommendations/2026-06-18.md) / [6/19](../../recommendations/2026-06-19.md)

### Input Data (forkcast diff)
- Monday: `output/sources/forkcast/2026-06-15.forkcast.json` (19 entries, partial fetch)
- Friday: `output/sources/forkcast/2026-06-19.forkcast.json` (148 entries full scale)
- Previous weekly: [2026-06-05 weekly report](./2026-06-05-weekly-report.md) -- LIP-35 SRv3 officially proposed + ACDE #238 Hegota 7-candidate listing

### Official Sources (Primary)
- ACDE #239: https://github.com/ethereum/pm/issues/2115
- ACDT #83: https://github.com/ethereum/pm/issues/2116
- RPC Standards #28: https://github.com/ethereum/pm/issues/2120
- FOCIL Breakout #36: https://github.com/ethereum/pm/issues/2121
- PQ Interop #44: https://github.com/ethereum/pm/issues/2128
- SSZ Engine API #1: https://github.com/ethereum/pm/issues/2132 + https://ethereum-magicians.org/t/ssz-engine-api-1-june-26-2026/28832
- P2P Networking #3: https://github.com/ethereum/pm/issues/2129
- EIP commits (6/18, 14:40~14:52 UTC 12-minute burst): [`bee14641`](https://github.com/ethereum/EIPs/commit/bee14641d13e369e1c0418757eedf2eb0f04e0ac) (EIP-8037) / [`803ee8d`](https://github.com/ethereum/EIPs/commit/803ee8d) (EIP-8038) / [`55fda83`](https://github.com/ethereum/EIPs/commit/55fda83) (EIP-2780)
- EIP commits (6/17, EIP-8081 PFI + EIP-8131 rewrite): [`37c28f7`](https://github.com/ethereum/EIPs/commit/37c28f7661b81585d9015b8bedb38dcd0e3cea3c) + [`cf5b8d9`](https://github.com/ethereum/EIPs/commit/cf5b8d9c0fd80dfc9d737135902b149ea64f6061)
- EIP-8304 discussion: https://ethereum-magicians.org/t/eip-8304-trustless-log-and-transaction-index/28824
- Erigon v3.4.4: https://x.com/ErigonEth/status/2067690980912906603
- Rocket Pool Smart Node v1.20.4: https://x.com/Rocket_Pool/status/2067352014003282059
- Lido Community Call announcement: https://x.com/LidoFinance/status/2067472274366849184
- Lido Snapshot [LIP-35](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x8fdec5d2cb70f8a266c4f5a269051fcfa985fab0f66cbe747702719d7433f606) / [LIP-33](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7b07bc31f0b38b69a117473031bc126becc70b9fa37246b53d9fe5a841c814f5)

### Related Entities

EIP-1559, EIP-2488, EIP-2537, EIP-2780, EIP-2935, EIP-4758, EIP-4844, EIP-6110, EIP-7002, EIP-7251, EIP-7549, EIP-7594, EIP-7610, EIP-7623, EIP-7642, EIP-7685, EIP-7691, EIP-7702, EIP-7708, EIP-7732, EIP-7745, EIP-7805, EIP-7843, EIP-7873, EIP-7904, EIP-7928, EIP-7934, EIP-7935, EIP-7951, EIP-7976, EIP-7981, EIP-8024, EIP-8025, EIP-8037, EIP-8038, EIP-8081, EIP-8105, EIP-8130, EIP-8131, EIP-8141, EIP-8146, EIP-8148, EIP-8182, EIP-8184, EIP-8188, EIP-8189, EIP-8205, EIP-8243, EIP-8246, EIP-8250, EIP-8253, EIP-8254, EIP-8282, EIP-8287, EIP-8295, EIP-8296, EIP-8304

Pectra, Fusaka, Glamsterdam, Hegota, Dencun

BAL, ePBS, FOCIL, MEV, DVT, PeerDAS, LUCID, SSZ, KZG, CSM, LIP-35

Geth, Nethermind, Besu, Erigon, Lighthouse, Prysm, Teku, Nimbus, Lodestar, Rocket Pool

ACDC, ACDE, ACDT, Lido

---

*Author: @r2jamong | 2026-06-19 W25 summary (ACDE #239 'Glam · Hegotá' joint agenda + new EIP-8282 Considered + 12-minute post-call commit burst + Hegota track expansion 1 → 10+ + Lido Snapshot 6-item burst + LIP-33 `0x02` credential + first Galaxy Curated v1→v2 case + Erigon v3.4.4 emergency + Rocket Pool Flashbots + SSZ Engine API #1 confirmed for 6/26 + Besu CVE 29+ days)*