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

Jun 2026 — Week 1

· @r2jamong .md

Weekly Ethereum Research Report (2026-06-01 ~ 2026-06-05)

TL;DR

  • Bottom line: During the 6/1~6/5 week, the official Lido SRv3 (LIP-35) proposal, ACDE #238's release of 7 Hegota candidates, and registration of EIP-8282 Builder Execution Requests happened in parallel, realigning the operator-entry, roadmap, and ePBS analysis axes.
  • Numbers: SRv3 presented 2048 ETH MaxEB, end-June Snapshot, July audits·mainnet·on-chain vote, October Period 1.5, December Period 2, and 2027 Q1 CMv1 sunset, while ACDE #238 was held as a 90-minute call on 6/4 14:00 UTC.
  • Action: Operators and researchers should prioritize tracking SRv3's July·October~December·2027 Q1 entry windows, CFI decisions for the 7 Hegota candidates, and EL/CL interface decisions for EIP-8282 and ETM #5 (6/10 15:00 UTC).

Top 3 Takeaways

  1. HIGH Lido SRv3 (LIP-35) formal proposal -- the week our research team's curated operator entry ETA became visible for the first time.

    자세히 읽기

    On 6/3 10:20 UTC, research.lido.fi 11621 (Maksim_Kuraian, Proposals) proposed SRv3 — (a) MaxEB 2048 ETH integration (EIP-7251, a single validator can hold up to 2048 ETH based on 0x02 WC), (b) accounting model shift — "validator counts → balances" (leveraging EIP-6110 + removing transient balance), (c) a 3-stage migration (Period 1 — CMv1+CMv2 in parallel → Period 1.5 — consolidation + top-up → Period 2 — CMv1 0%) with natural attrition and no forced exits, (d) first explicit timeline — end-June Snapshot → July audits (4 firms: Certora·Statemind·Composable Security·MixBytes) + mainnet + on-chain vote → October Period 1.5 → December Period 2 → 2027 Q1 full CMv1 sunset, (e) Consolidation Easy Track + Merkle proofs, (f) "CMv2 gets top priority for new seed deposits" — new NO admission is automatically absorbed into the CMv2 track. The 6/4 08:04 UTC official Lido Twitter trailer ("reallocated stake + large validator deposit + lean validator management") + the 6/4 11:21 UTC Nemo new director proposal (research.lido.fi 11624) + the 6/4 08:48 UTC Q1'2026 Financial Report (research.lido.fi 11623, net DAO revenue $9.42M + operating surplus $3.1M + treasury $121M) — June Snapshot agenda 5 items confirmed (Dual Governance, SDVTM Winddown, wstETH Bridge cancellation across 9 chains, Nemo director, SRv3 LIP-35) + if the CMv2 governance proposal remains unregistered, 18 days remain until the June 23 Snapshot, until 6/23 Snapshot (18). Our research team's entry ETA became visible — a new decision matrix appears with 3 entry windows (just before July mainnet / during the October-December migration / after full transfer following 2027 Q1).

  2. HIGH ACDE #238 (6/4) listed 7 Hegota candidates + EIP-7701 Withdrawn + EIP-8130 finalize burst + EIP-8148 Proposed for Inclusion in EIP-8081 meta EIP -- AA track closure + Hegota EL headliner lineup reshuffle.

    자세히 읽기

    The 6/4 14:00 UTC ACDE #238 issue 2076 agenda body officially listed 7 Hegota EL candidates — EIP-8131·EIP-8279 (@nerolation), EIP-7979·EIP-8173 (@gcolvin), EIP-8222 (@mmjahanara), EIP-7851·EIP-8151 (@lightclient) + bal-devnet-7 + Glamsterdam-devnet-5/6 — distributed across 4 camps: @lightclient(Geth) + @nerolation + @gcolvin + @mmjahanara, while the assumed lineup from yesterday — EIP-4758 / EIP-8141 / EIP-8130 / EIP-8148 — had 0 appearances, a partial rejection. On 6/2 17:24 UTC, commit 0f6f7e2 formally processed EIP-7701 Native AA Stagnant → Withdrawn + the same day's 19:50~20:25 UTC 35-minute window saw a 3-commit EIP-8130 burst (gas accounting → signature-invariant nonce-free replay identifier → existing-account + code-size guards) + 6/4 14:29~23:19 UTC saw 4 EIP-8130 finalize-pass commits (owners → actors rename + per-actor expiry + actor call policies + cleanup +182/-223) — the Native AA track effectively closed and the follow-on EIP-8130 (Account Abstraction by Account Configuration) candidate strengthened. On 6/4 12:37 UTC, commit 137011d listed EIP-8148 "Custom sweep threshold for validators" as Hegota Proposed for Inclusion in the EIP-8081 meta EIP — meta EIP body (Hegota Scheduled — EIP-7805 FOCIL 1 item + Proposed for Inclusion — EIP-8148 + EIP-4758 + EIP-7709 + EIP-7716, etc.) vs 6/5 dump — only [4758] exposed — revealing a synchronization gap between dump and meta EIP, with meta EIP commit-level monitoring serving as an inclusion-signal source 1~3 days faster than the dump.

  3. HIGH Chainnodes stVault Basic Operator application + EIP-8282 Builder Execution Requests + 5 days until ETM #5 on 6/10 + end of DVV DVT incentives -- first primary NO admission track case + new ePBS builder lifecycle separation + Lido DVT cycle reshaping.

    자세히 읽기

    The 6/2 14:44 UTC research.lido.fi 11616 (koraykoska_cn, first active application in the stVaults Identification category) — (a) 3 EL clients (Geth + Nethermind + Besu) + 3 CL clients (Teku + Lighthouse + Grandine, including minority), (b) self-hosted + cloud hybrid + Europe/North America distribution, (c) Web3Signer, (d) MEV policy "All relays enabled, including non-censoring", (e) operating scale of 10,000+ project RPCs + 1.5B daily requests, (f) business case of "Avalanche → Ethereum bridging + retail/B2B2C staking within 1 month", (g) acceptance of the "default Basic tier grid" — the starting point for entry into the stVault NO tier system — secured the first primary-source baseline for a 6-item standard-template matrix for our research team's entry application. On 6/4 07:40 UTC, ethereum-magicians 28699 (wemeetagain) + PR #11760 introduced EIP-8282 Builder Execution Requests — (a) completely separates the EIP-7732 ePBS builder lifecycle from validator flows, (b) creates two predeploy contracts on the EIP-7685 request bus: 0x03 (builder deposit/top-up) + 0x04 (builder exit), (c) a single pubkey can perform both validator + builder roles — proposer-builder integrated operating scenario — potential change to the mev-boost external-builder model, (d) reignites the EL implementation layer after a 6-month gap since ePBS Breakout 2025-12-19 (#029). On 6/4 17:52 UTC, Encrypt The Mempool #5 had 5 days left until 6/10 (ethmagicians 28703) — SFI Execution Spec Very Draft PR + Glamsterdam + FOCIL-based build + "To build on Framed TX or not?" — imminent EIP-8141 adoption decision + CL side not participating. The 6/3 11:40 UTC @LidoFinance 2062137257 DVV Migration — dvstETH DVT incentives ended in April 2026 + EarnETH (Mellow Protocol) migration recommended — introduced a new 1-year window pattern for DVT adoption incentives. New ERC bundle on 6/2 — ERC-8286 Modular Accounts for Frame Transactions (validator·executor·hook·config 4 modules) + ERC-8287 Privacy-Native Fungible Tokens (Zcash Orchard) + pERC20 standards track 25089 + ERC-8004 VNI multi-validator network (5/31 21:26 UTC) — dApp-facing AA ERC coupling + Privacy-domain standards cluster + multi-validator standardization all progressed at once.

1. Roadmap / Upgrade Highlights

Hegota EL headliner lineup 7 candidates + ACDE #238 agenda published

EIP Author Track This Week's Change
EIP-8131 @nerolation Hegota Newly listed on ACDE #238 agenda on 6/4
EIP-8279 @nerolation Hegota Newly listed on ACDE #238 agenda on 6/4 (BAL Byte Floor)
EIP-7979 @gcolvin Hegota Newly listed on ACDE #238 agenda on 6/4
EIP-8173 @gcolvin Hegota Newly listed on ACDE #238 agenda on 6/4 (EVM Control Flow)
EIP-8222 @mmjahanara Hegota Newly listed on ACDE #238 agenda on 6/4
EIP-7851 @lightclient Hegota Newly listed on ACDE #238 agenda on 6/4 (Geth-view priority)
EIP-8151 @lightclient Hegota Newly listed on ACDE #238 agenda on 6/4 (Geth-view priority)
EIP-4758 STEEL Hegota proposed dump [4758] stable for 5 consecutive days + absent from ACDE #238 agenda
EIP-8148 gkoumout Hegota proposed Listed in EIP-8081 meta EIP body on 6/4 (Proposed for Inclusion)
EIP-7805 FOCIL -- Hegota scheduled Listed as Scheduled in EIP-8081 meta EIP body on 6/4
EIP-8130 -- Draft (unlisted) 6/2 3-commit burst over 35 minutes + 6/4 finalize pass 4 commits — concentrated spec-polish phase, absent from ACDE agenda
  • Distributed across 4 author camps (@lightclient/Geth + @nerolation + @gcolvin + @mmjahanara) — an equilibrium state where no single camp monopolizes Hegota EL (interpretation).
  • Assumed lineup from yesterday partially rejected: EIP-4758 / EIP-8141 / EIP-8130 / EIP-8148, which were estimated just before this week, had 0 appearances on the ACDE agenda. The EIP-8141 / EIP-8130 camps are running separate Headliner Breakout tracks (one-off-1954, one-off-1985) — timing for entry into the ACDE main agenda will be decided separately.
  • Decisions body unpublished as of week-end — lag 1~2 days — 6/8~6/9 notes are the key change-capture point.

EIP-8282 Builder Execution Requests — new complete separation of the ePBS builder lifecycle

Area Detail
Registration 6/4 07:40 UTC ethereum-magicians 28699 (wemeetagain) + PR #11760
Separation mechanism EIP-7732 ePBS builder deposit/exit — registration/exit through validator flow → independently routed via a separate EL request contract
Predeploy contracts 0x03 (builder deposit/top-up — deposit(pubkey, withdrawal_credentials, amount, signature)) + 0x04 (builder exit — exit(pubkey))
Reasons for separation (1) routing by type (replacing withdrawal-credential prefix inspection), (2) DoS defense (MAX_REQUESTS_PER_BLOCK + EIP-1559), (3) cold-key security (builder BLS active, exit authorized by execution_address)
Integration scenario A single pubkey can perform both validator + builder roles — proposer-builder integrated operating scenario emerges
Track implication post-Glamsterdam fork target (extension after EIP-7732 body lands) + signal that EL implementation layer is reignited after a 6-month gap in ePBS Breakout calls

EIP-7701 Withdrawn + EIP-8130 burst pattern — AA track closure + follow-on strengthening

  • 6/2 17:24 UTC 0f6f7e2 formally processed EIP-7701 Stagnant → Withdrawn.
  • 6/2 19:50~20:25 UTC 35-minute window saw 3 EIP-8130 burst commits — (a) gas accounting + interface cleanups (916c073), (b) signature-invariant nonce-free replay identifier (cd0b021), (c) create entry existing-account + code-size guards (07f7dc7).
  • 6/4 14:29~23:19 UTC EIP-8130 finalize pass 4 commits — owners → actors rename + IAccountConfiguration.verify → verifyActor + per-actor expiry + actor call policies + cleanup (+182/-223, 41-line net reduction) — concentrated spec polish in the window right after ACDE #238.
  • 6/2 17:42 UTC EIP-8133 Draft → Review promotion (bca0b64) — meta governance standardizing Ethereum hard-fork naming rules (CL constellations + EL cities).
  • In Native AA Breakout #1 (4/14~4/22, comparing EIP-7701/8141/8223/8224), the EIP-7701 line closed — EIP-7701 is no longer an option in the Hegota EL headliner lineup.

Frame TX / dApp ERC coupling + Privacy standards cluster + ERC-8004 VNI

  • ERC-8286 Modular Accounts for Frame Transactions (6/3 23:35 UTC ethereum-magicians 28695 → ERC number 8286 assigned on 6/4) — validator·executor·hook·config 4 modules — first dApp-facing ERC coupling for EIP-8141 Frame TX — signal that the post-7701 AA follow-on track is entering the ERC layer.
  • ERC-8287 Privacy-Native Fungible Tokens (ethmagicians 28702, 6/4 10:04 UTC, Cyimon, Zcash Orchard-based) + pERC20 standards track 25089 (ethresearch 25089, _pERC20Labs, 6/4 07:32 UTC) — Privacy-domain standards appeared simultaneously.
  • ERC-8004 VNI multi-validator network (ethmagicians 28669, Traciecmyers, 5/31 21:26 UTC) + Draft spec pokt-network/erc-8004-vni — extension of AI-agent validation standards into a multi-validator dimension — possible alignment with DVT (Obol/SSV) / Lido CSM tracks (hypothesis).
  • EIP-3668 Gateway-to-gateway Mesh Sync Protocol (ethmagicians 28680, Tiago Merlini / Damon Zwicker / Vincent Wu, 6/2 12:01 UTC) — attestation-based mesh sync between CCIP-Read gateways — long-term change signal for RPC infrastructure architecture.

Encrypt The Mempool #5 + PQ urgency narrative strengthens after 6/2

  • ETM #5 had 5 days left until 6/10 (6/10 15:00 UTC) (ethmagicians 28703, agenda posted 6/4 17:52 UTC) — SFI (Single-slot Finality Integration) Execution Spec Very Draft PR + build based on Glamsterdam + FOCIL + "To build on Framed TX or not?" — imminent EIP-8141 adoption decision + Execution Spec Tests / Consensus Specs / Hive Tests / EL/CL Client Implementation all TBD + "We need a CL dev to help here" — CL-side non-participation — CL-EL interface (Engine API) design not yet fixed.
  • PQ urgency narrative strengthened after 6/2 — (a) 6/2 12:55 UTC @drakefjustin Shor's algorithm tweet "Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography on March 31... the paper was a bombshell" + (b) 6/2 13:57 UTC @drakefjustin neutral atoms qday tweet + (c) 6/2 20:32 UTC ethresearch 25067 "Ethereum Cryptography and AI slop" "The crypto space is in panic mode" + (d) PQ Interop #42 held on 6/3 14:00 UTC (leanspec refactoring + PQ Public Key Registry discussion) — the PQ track has moved through narrative → mandate → spec polish → keys/registry mechanism design and entered the stage where external quantum-computing progress is added as a timeline-pressure factor.

2. EIP Status Changes (Monday 6/1 vs Friday 6/5)

Data-integrity signal: This week had 6 consecutive days from 5/31~6/5 of summary dump freeze (Hegota proposed=[4758] stable + Dencun included=[4844] + Pectra included=[2537, 2935, 6110] or [2537, 2935] changing, Glamsterdam declined [2926, 6466] ↔ [2926, 5920] toggle). Inclusion-stage updates were not reflected at the dump time right after ACDE #238 (6/4 14:00 UTC), 6/5 00:30 UTC — the dump is a lagging indicator. The meta EIP (EIP-8081) emerged this week as a more authoritative inclusion truth source — automated alerting priority — (1) meta EIP commit > (2) ACDE/ACDC call notes > (3) dump changes.

6/1 (Mon) → 6/5 (Fri) summary diff

Track / Stage 6/1 (Mon) 6/5 (Fri) Change
Dencun included [4844] [4844] Same
Pectra included [2537, 2935] [2537, 2935, 6110] +EIP-6110 restored (missing on 6/1 → returned on 6/5)
Pectra declined [3540, 3670, 4200, 4750, 5450] Same Same (EOF bundle)
Glamsterdam considered [2780] [2780] Same
Glamsterdam declined [2926, 6466] [2926, 5920] +EIP-5920 / -EIP-6466 toggle
Fusaka declined [3540, 3670, 4200, 4750, 5450] [3540, 3670, 4200, 4750, 5450, 5920] +EIP-5920 newly exposed
Hegota proposed [4758] [4758] Stable for 5 consecutive days (6/1/2/3/4/5)

Reliable actual changes this week (cross-verified across calls / commits / external primary sources)

Meta EIP listings (not reflected in dump)

  • EIP-8081 Hegota Meta EIP body update (6/4 12:37 UTC 137011d) — Hegota Scheduled — EIP-7805 FOCIL 1 item + Proposed for Inclusion — EIP-8148 + EIP-4758 + EIP-7709 + EIP-7716, among others — not reflected in 6/5 dump — meta EIP commit is a more authoritative inclusion-truth source than the dump.

EIP lifecycle changes

  • EIP-7701 Stagnant → Withdrawn (6/2 17:24 UTC 0f6f7e2) — formal closure of the Native AA track.
  • EIP-8133 Draft → Review (6/2 17:42 UTC bca0b64) — meta governance standardizing hard-fork naming rules.
  • EIP-8148 0x03 WC removal commit (6/2 13:13 UTC 2f97ce6) "Remove 0x03 WC from EIP-8148 and add a link to spec" — 0x03 WC split into separate spec — withdrawal-credentials standardization trajectory branched — NO side keeps the current 0x02 compounding WC baseline + monitoring card for separate 0x03 spec proposal.
  • EIP-8037 typo fix (6/2 13:34 UTC 546b61a) — polish aligned with ACDT #82.

New EIP / ERC registrations

  • EIP-8282 Builder Execution Requests (6/4 07:40 UTC, wemeetagain) + PR #11760 — ePBS builder lifecycle separation.
  • ERC-8286 Modular Accounts for Frame Transactions (6/3 23:35 UTC → ERC number 8286 assigned on 6/4).
  • ERC-8287 Privacy-Native Fungible Tokens (6/4 10:04 UTC, Cyimon, Zcash Orchard).
  • pERC20 standards track 25089 (6/4 07:32 UTC, _pERC20Labs).
  • ERC-8004 VNI multi-validator network extension (5/31 21:26 UTC carry-over, Traciecmyers) + Draft spec pokt-network/erc-8004-vni.
  • Evidential Survivability OCP / CROPS (ethresearch 25012, Damon Zwicker, 5/31 04:52 UTC carry-over) — first external academic elaboration of the 3/14 EF CROPS mandate.

Burst pattern (EIP-8130 7 commits + 1 tooling item)

  • EIP-8130 6/2 3-commit burst (35-minute window) + 6/4 finalize pass 4 commits (14:29~23:19 UTC, +182/-223 41-line net reduction) — Account Abstraction by Account Configuration spec polish → concentrated pre-Review preparation phase. Week-end body status — still Draft (not promoted to Review) + absent from ACDE #238 agenda — candidate-entry timing may be delayed.

3. Validator / Infrastructure Key Issues

Lido SRv3 (LIP-35) formal proposal — first visibility of our research team's entry ETA

Area Detail NO Entry Implication
MaxEB integration Uses EIP-7251 — single validator can hold up to 2048 ETH (0x02 WC basis) NO per-key operating cost efficiency improves up to 64x + lean validator management paradigm
Accounting model shift "Accounting moves from validator counts to balances" (leveraging EIP-6110 + removing transient balance) NO reward-distribution accounting — key count → effective-balance basis
3-stage migration Period 1 (CMv1+CMv2 parallel) → Period 1.5 (consolidation + top-up) → Period 2 (CMv1 0%) Gradual 6-9 month natural attrition with no forced exits
Timeline first specified End-June Snapshot → July audits (4 firms: Certora·Statemind·Composable Security·MixBytes) + mainnet + on-chain vote → October Period 1.5 → December Period 2 → 2027 Q1 full CMv1 sunset Our research team's entry ETA visible — decision matrix with 3 windows (just before July / mid-October-December / after 2027 Q1)
Consolidation Pipeline Easy Track motion + Merkle proof-based trust-minimized verification New governance for source NO → target NO key transfer
Exit Rate limit Based on total effective balance instead of validator count (32/2048 ETH units) NO churn-rate operating baseline transition
Top-up mechanism Top up 0x02 WC validators up to 2048 ETH New NO capital-efficiency operating card
CSM v3 compatibility Independent module based on LIP-33 — built on top of LIP-35 base layer Core / CMv2 / CSM compatible infrastructure
Automatic routing "CMv2 gets top priority for new seed deposits" + withdrawal-driven exit Stronger possibility that new NO admission proceeds through the CMv2 track
Twitter trailer 6/4 08:04 UTC (@LidoFinance 2062445305) 3 value propositions: "reallocated stake + large validator deposit + lean validator management"

Lido governance burst peaks this week (5 Snapshot agenda items + CMv2 unregistered as of 6/5)

# Agenda Proposal Date Week-End Status
1 SRv3 LIP-35 (11621) 6/3 10:20 UTC Key new item this week (Snapshot confirmed for end-June)
2 Lido Labs Nemo Director (11624) 6/4 11:21 UTC New (added to June Snapshot agenda) — backfills Konstantin's board departure
3 Lido Q1'2026 Financial Report (11623) 6/4 08:48 UTC New — net DAO revenue $9.42M + operating surplus $3.1M + treasury $121M (-$36.5M, -$31.6M stETH price effect) + operating expenses conservatively executed at 22% of EGG
4 Chainnodes stVault Basic Operator (11616) 6/2 14:44 UTC First active application in the stVaults Identification category, 3rd day of review after 6/2 proposal
5 BCV Lido DAO LTM Dashboard (11614) 6/2 07:34 UTC Explicit governance centralization risk: a single delegate has ~50% voting power
6 DVV Migration ([DVT] incentives end) 6/3 11:40 UTC tweet dvstETH April end + EarnETH migration recommended — new DVT 1-year window pattern
7 Dual Governance activation (Snapshot confirmed) 6/23~6/30
8 SDVTM Regular Clusters Winddown (Snapshot confirmed) 6/23~6/30
9 wstETH Bridge canonical cancellation across 9 chains 5/26 carry-over 6/23~6/30 Snapshot + NEC delegation
10 CMv2 governance proposal Unregistered As of 6/5, 18 days until 6/23 Snapshot — if not registered this week, 2 SNOPs v4 items lag into July schedule
11 CMv2 Prover Bot Funding (11597) 5/28 245k NOR → 3,829 compounding × 2048 ETH (64:1) + 15,316 tx + 6 ETH gas

June Snapshot final agenda — 5 items confirmed (6/5):

Agenda Registration Snapshot Schedule
Dual Governance activation Confirmed 6/23~6/30
SDVTM Regular Clusters Winddown Confirmed 6/23~6/30
wstETH Bridge cancellation across 9 chains + NEC Confirmed 6/23~6/30
Nemo director appointment New 6/4 6/23~6/30
SRv3 LIP-35 New 6/3 End-June (specified in LIP-35 body)
CMv2 governance proposal Unregistered, 18 days until 6/23 Snapshot TBD
Aragon on-chain (Dual Governance) Waiting 6/25~6/30

Chainnodes stVault Basic Operator application — NO entry standard-template baseline

Item Chainnodes Detail Requirement for Our Research Team Entry
EL clients Geth + Nethermind + Besu (3 types) At least 2 types (Geth + 1 minority)
CL clients Teku + Lighthouse + Grandine (3 types) At least 2 types (Lighthouse + 1 minority — Nimbus/Grandine/Lodestar)
Infrastructure Self-hosted + cloud hybrid Eliminate single-cloud risk — at least 2 providers
Region/Jurisdiction Europe/North America distributed Korea + 1 additional region distributed
Key management Web3Signer Adopt standards such as Web3Signer / Vouch / Dirk
MEV policy "All relays enabled, including non-censoring" Pre-decide OFAC sanctions-screening policy
Existing operating scale 10,000+ project RPCs + 1.5B daily requests + VaaS + Liquid + Solo Prepare a multi-product RPC/VaaS/Staking line for the Korean market
Business case Avalanche → Ethereum bridging + retail/B2B2C within 1 month Pre-design a Korean-market (KRW → ETH) commercial driver
Application track stVault Basic tier (default tier grid accepted) Review NOR/CSM curated track vs stVault Basic in parallel
Customer examples EtherFi / GFX Labs / Oku Trade / Thales / Contango Pre-secure Korean institutional B2B2C partners
Fee structure TBD [Further verification needed]
Respondents/supporters Zero as of week-end Monitor NOWG / Tokenholder due-diligence trajectory

Client security risks -- 3 HIGH items unresolved for 16 accumulated days

# Client Issue Recommended Action
1 Besu 26.5.0 CVE-2026-34480 / CVE-2026-34478 Patch immediately (16-day exposure)
2 Erigon v3.4.0 → v3.4.1 segfault (TrieContext.Branch) v3.4.1 upgrade required
3 Geth v1.17.3 structLog Tracing API parser mismatch (Breaking Change) Awaiting patch + inspect MEV/monitoring pipelines
  • Zero new EL/CL releases for 16 consecutive days (since 5/21, week-end 5/29 → 6/5) — 6~8x slower than normal cadence (1~2 per week).
  • Privacy-domain standards cluster newly appeared — ERC-8287 (Zcash Orchard) + pERC20 — zero direct infrastructure impact, but new simultaneous standards-track lines appeared.
  • New EIP-3668 Mesh Sync Protocol proposal (Tiago Merlini / Damon Zwicker / Vincent Wu) — attestation-based mesh sync between CCIP-Read gateways — long-term change signal for RPC infrastructure architecture (zero short-term impact).

Lido Q1'2026 financial baseline + governance centralization risk

  • Lido Q1 2026 financials: net DAO revenue $9.42M (April additional +$2.79M) + foundation operating expenses $6.44M (22% of approved EGG budget) + operating surplus $3.1M (positive) + treasury $157.5M → $121.0M (-$36.5M, of which -$31.6M — stETH price effect) + stETH holdings 43,833.9 (Q1 end) → 40,428.3 (April end, 2,500 stETH paid for Kelp incident compensation) — "conservative spending approach" + partial fill of BCV Dashboard's cost-data omission limitation.
  • BCV LTM Dashboard 11614 governance centralization risk: "a single delegate/address represented nearly half of the voting power" — single delegate ~50% voting power — possible impact on decision-making consistency for key governance decisions such as SRv3 / CMv2 / NO admission — must verify the governance-decentralization effect of introducing LDO Staking Module 11600 (veLDO, carried over for 10 days since 5/29).
  • LDO Accumulation Batch 1 remaining 274.31 stETH window has 11 days until 6/14 close (@LidoFinance 2061813992, 6/2 14:15 UTC) — 6/14 deadline + price cap 0.000163 LDO/ETH + expected total use ~745 stETH (7.45% of approved 10,000 stETH cap) — consistency of conservative execution.

4. Key Protocol Call Decisions

Sources: output/notes/protocol-calls/2026-06-02-call-summary.md (8 calls from 5/21~6/1) + output/sources/protocol-calls/2026-06-05.protocol-calls.json + 6/4 ACDE #238 agenda body (issue 2076).

This week's call matrix

Date Call Number Agenda / Decisions Notes Status
6/1 (Mon) 14:00 UTC ACDT — All Core Devs Testing #81 bal-devnet-7 EVM fuzzing 100% participation stable + Glamsterdam-devnet-4 chain split issue being resolved + two EIP-8037 PRs (calldata floor accounting merged + EIP-7702 authorization gas accounting open) + EIP-7928 BAL state-access verification EIP-2929 split PR (pre-state stack/balance / post-state cold-access + BAL insertion) + 3 devnet-5 strategy options (clean rerun / integrate bal-devnet-7 / run in parallel then merge) Official summary unpublished (organized from GitHub issue comments)
6/1 (Mon) 15:00 UTC RPC Standards #27 tag-driven release pipeline (execution-apis #807/#808) + handling whether eth_* state methods require block param vs default value (latest block) Official notes unpublished
6/2 (Tue) 13:00 UTC FOCIL Breakout #35 Development/Spec/Testing updates agenda — progress on FOCIL (EIP-7805) Glamsterdam headliner candidacy GitHub Issue decisions not captured
6/3 (Wed) 14:00 UTC PQ Interop #42 leanspec refactoring + PQ Public Key Registry discussion (ethresearch 25040 EF core researchers 4 + Drake) Notes unpublished
6/3 (Wed) 15:30 UTC P2P Networking #2 Sparse blobpool state + metrics + cell-level deltas updates — directly tied to PeerDAS (EIP-7594) P2P-layer design — possible changes to EL/CL client blob gossip implementation requirements Notes unpublished
6/4 (Thu) 14:00 UTC ACDE — All Core Devs Execution #238 (90 min) Agenda — "Glam / Hegotá" + 7 Hegota candidates officially listed (EIP-8131·EIP-8279·EIP-7979·EIP-8173·EIP-8222·EIP-7851·EIP-8151) + bal-devnet-7 + Glamsterdam-devnet-5/6 + distribution across 4 author camps Decisions body unpublished as of week-end (lag 1~2 days, 6/8~6/9 change-capture window)

Summary of key observations from this week's calls

  1. ACDT #81 (6/1) — Glamsterdam devnet-5 scoping + two EIP-8037 PRs + EIP-7928 BAL state-access split -- official summary unpublished carry-over. 3 devnet-5 strategy options under review — (1) clean rerun vs (2) integrate bal-devnet-7 vs (3) run in parallel then merge. EIP-7902 delegated addresses add BAL specs only after gas/balance/stack-depth checks (@nerolation 5/21 ACDE #237 carry-over).
  2. ACDE #238 (6/4) — date when Hegota EL headliner lineup was formally listed -- decisions body unpublished as of week-end (6/5 00:30 UTC) — 6/6~6/9 dump is the key change point + body analysis of each of the 7 newly listed EIPs is the 6/8 daily follow-up priority. At week-end, the final confirmed Glamsterdam scoping lineup also remains uncaptured — decision window for inclusion of EIP-7708 / EIP-7732 ePBS / EIP-7805 FOCIL / EIP-7928 BAL.
  3. P2P Networking #2 (6/3 same day) Sparse blobpool + cell-level deltas -- PeerDAS P2P layer — possible change to NO-side blob traffic/bandwidth cost baseline + EL mempool structure + CL gossip subnet allocation method changes. Notes unpublished.
  4. PQ Interop #42 (6/3) — Post-Quantum Public Key Registry discussion enters regular meeting body -- leanspec refactoring + ethresearch 25040 (4 EF core researchers + Drake) design thread + 6/2 Drake Shor's algorithm tweet + ethresearch 25067 "panic mode" — date when the PQ track 48-hour triangle activated simultaneously.
  5. FOCIL Breakout #35 (6/2), follow-up check on 6/3 -- development/spec/testing agenda for the Glamsterdam headliner candidate. GitHub Issue side did not capture decisions, carried over.
  6. 6 official notes remain unpublished cumulatively — ACDT #81 / RPC #27 / FOCIL #35 / PQ Interop #42 / P2P #2 / ACDE #238 — this week's pattern worsened from the previous week (5/25~5/29) with 5 unpublished notes. Accumulated dependence on direct reading of ethereum/pm GitHub Issues for call notes.

Daily recommendations (Topic Recommender)

Date Rec 1 Rec 2 Total Score
6/1 (Mon) ERC-8004 VNI multi-validator network (issue) NO Transparent Post-Mortem Culture — contractual obligation evolution hypothesis (report) 8.65 / 8.65
6/2 (Tue) (no recommendation written) -- --
6/3 (Wed) Chainnodes stVault Basic Operator application precision decoding + NO standard-template 6-item matrix + stVault ETA compression hypothesis (issue) EIP-7701 Withdrawn + EIP-8130 35-minute burst concurrency — Native AA closure + follow-on candidate hypothesis (article) 9.45 / 8.575
6/4 (Thu) First dApp-facing ERC coupling for EIP-8141 Frame TX (ERC-8286) (issue) PQ transition triangle (PQ Interop #42 + PQ PK Registry + Shor) (report) 0.813 / 0.823
6/5 (Fri) Lido SRv3 (LIP-35) precision decoding — MaxEB 2048 ETH + accounting model shift + end-June~2027 Q1 migration timeline (issue) EIP-8282 Builder Execution Requests — ePBS builder lifecycle separation + single pubkey validator+builder integration + mev-boost inflection point (article) 0.91 / 0.83

6/2 (Tue) — no recommendation written. 8 recommendations available across 4 dates: 6/1/3/4/5. This week's recommendation score peaks — 6/3 Rec 1 (Chainnodes 9.45/10) + 6/5 Rec 1 (SRv3 0.91/1.00).

Priority Writing Targets (Top 3)

  1. [6/5 Rec 1] Lido Staking Router v3 (LIP-35) precision decoding -- MaxEB 2048 ETH integration, end-June~2027 Q1 migration timeline, and the structure where new NO admission is automatically absorbed into the CMv2 track -- category: issue, length 6,500~7,500 Korean chars, difficulty high.

    • Why: (i) proposal on 6/3 10:20 UTC after 6/2 — primary source where our research team's entry ETA became visible for the first time, (ii) zero Korean-language comprehensive analysis before the end-June Snapshot → July mainnet deployment window (info gap HIGH), (iii) direct precise mapping possible for 7 core changes (MaxEB / balances accounting / 3-stage migration / Consolidation / Exit Rate / Top-up / CSM v3 compatibility), (iv) new decision matrix with 3 entry windows (just before July mainnet / mid-October-December / after 2027 Q1) — pre-decision on stating lean validator management capacity in our research team's entry application.
    • Differentiation: 5/14 Lido May Snapshot 5 items / 5/21 Q1 quarterly report / 5/26 EIP-8243 / 5/28 CMv2 Prover Bot Funding (case after 1 day from 6/2 Snapshot proposal) / 6/3 Chainnodes application / 6/5 SRv3 LIP-35 peak — Lido NO entry track series v5 peak — MaxEB migration quantification + LIP-35 integrated view + visible entry ETA — first such 3-axis synergy in the Korean-speaking region.

  2. [6/3 Rec 1] Chainnodes stVault Basic Operator application precision decoding -- first active case in Lido V3 stVaults Identification category, 6-item NO entry application standard-template matrix + NOR/CSM/stVault 3-way comparison + stVault ETA compression hypothesis -- category: issue, length 5,000~6,000 Korean chars, difficulty medium-high.

    • Why: (i) proposal on 6/2 14:44 UTC, after 1 day from 6/2 proposal — first case with 100% alignment to our research team's core target track — first Korean-language summary window, (ii) 6 application items (client diversity / infrastructure / key management / MEV policy / operating scale / business case) — direct baseline for our research team's entry-application standard template, (iii) first Korean-language NOR / CSM / stVault 3-way comparison + analysis of stVault Basic / Higher tier entry starting-point data — verifies stVault track ETA compression hypothesis, (iv) NOWG / Tokenholder due-diligence trajectory monitoring window 1~30 days after 6/2 proposal — baseline catalog of pre-answers when writing an entry application.
    • Differentiation: Rec 1 (SRv3 core accounting/migration infrastructure) + Rec 2 (Chainnodes entry application matrix) — can form an infrastructure + entry application two-axis series — peak synergy for curated-operator entry-track intelligence.

  3. [6/5 Rec 2] EIP-8282 Builder Execution Requests -- the first EIP where the ePBS builder lifecycle is completely separated from validator flows, single-pubkey validator+builder integration scenario, and the inflection point of the mev-boost external builder model -- category: article, length 5,500~6,500 Korean chars, difficulty high.

    • Why: (i) proposed 6/4 07:40 UTC, after 1 day from 6/2 proposal — zero Korean-language comprehensive analysis, (ii) signal that the EL implementation layer is reignited after a 6-month gap since ePBS Breakout call 2025-12-19 (#029) — precise analysis window before the next ePBS Breakout call is scheduled, (iii) timeliness peaks because ETM #5 (6/10 15:00 UTC, 5 days left until 6/10) aligns with SFI Execution Spec + Framed TX adoption decision immediately after Glamsterdam scoping confirmation, and ePBS EL layer is reignited, (iv) single-pubkey validator + builder integration scenario — mev-boost external-builder model inflection point — pre-analysis for redesigning our research team's MEV policy ("all relays + non-censoring").
    • Differentiation: redesign of NO-side MEV value-capture strategy — direct builder register vs relay delegation choice card — zero first-pass analysis in both Korean and English + cross-domain infrastructure/validator/roadmap analysis.

Series continuity recommended: Rec 1 (SRv3 LIP-35) → Rec 2 (Chainnodes stVault application analysis) — Lido NO entry track v5 peak + v6 entry application matrix two-axis series. Rec 3 (EIP-8282) — suitable as an independent ePBS article to publish around the point when 2 days remain until ETM #5 (6/10).

6. Key Schedule for Next Week (2026-06-08 ~ 2026-06-12)

Protocol calls (second-week-of-June burst window)

Date Call Number Key Observation Points
6/8 (Mon) 14:00 UTC ACDT — All Core Devs Testing #82 Agenda TBD (ethereum-magicians 28681) — first follow-up call after ACDE #238 (6/4) Glamsterdam devnet-5 scoping decision + bal-devnet-7/8 transition + processing EIP-8037 EIP-7702 authorization gas accounting PR + follow-up on EIP-7928 BAL state-access split PR
6/10 (Wed) 15:00 UTC Encrypt The Mempool #5 5 days left until 6/10 — SFI Execution Spec Very Draft PR + "To build on Framed TX or not?" — imminent EIP-8141 adoption decision + EL implementation-direction decision while CL side is not participating + follow-up alignment after ACDE #238 Glamsterdam scoping confirmation
6/10~6/12 (expected) EIP Editing Office Hour #101 Follow-up to 6/2 EIPOH #100 (EIP-7701 Withdrawn formal resolution + ERC-7813 Last Call + EIP-867 Draft revival + Contract Payer Transaction)
6/15 (Mon) ETA RPC Standards #28 follow-up to execution-apis tag-driven release pipeline
6/23 (Tue) 10:00 UTC Fast Confirmation Rule #9 Client + Spec + Testing + API and Metrics + Research Updates — impact on eth_getBlockByNumber safe/finalized tag handling + monitoring dashboard finalized-block display logic

Devnet / spec milestones

  • Glamsterdam devnet-5 launch -- immediately after ACDE #238 (6/4) scoping decision or second week of June. Decision window for 3 options (clean rerun / integrate bal-devnet-7 / run in parallel then merge) — core agenda for ACDT #82 (6/8).
  • Hegota devnet-0 launch -- window around end-June~early July depending on EL/CL client spec decision ETA after ACDE #238 listed 7 Hegota candidates. dump frozen 6 days (5/31~6/5) → 6/8~6/9 is the capture point for inclusion-stage updates.
  • bal-devnet-7 → bal-devnet-8 transition -- ACDT #82 (6/8) agenda or mid-June.
  • PQ Devnet stability -- depends on follow-up call results after PQ Interop #42 (6/3) leanspec refactoring + PQ PK Registry discussion.

Governance / operations

  • ACDE #238 (6/4) official notes publication window -- unpublished as of this week-end (6/5) — key monitoring item for 6/8~6/9. Direct quotes for Hegota 7-candidate (EIP-8131·8279·7979·8173·8222·7851·8151) CFI decisions + final confirmed Glamsterdam scoping lineup (EIP-7708/7732/7805/7928) + whether EIP-8243 Batching Attestations / MPBC / EIP-8282 are added to the agenda.
  • Raise priority of EIP meta EIP commit-level monitoring -- EIP-8081 Hegota meta EIP commit is an inclusion-truth source 1~3 days faster than dump — automated alerting — adopt order: (1) meta EIP commit > (2) ACDE/ACDC call notes > (3) dump changes.
  • Lido governance July Snapshot window enters full swing — (i) CMv2 governance proposal unregistered as of 6/5, 18 days until 6/23 Snapshot — if not registered by 6/8~6/13, SNOPs v4 2 items will definitively lag into the July schedule, (ii) SRv3 LIP-35 NOWG / Tokenholder response trajectory enters monitoring period (25 days until end-June Snapshot), (iii) Chainnodes 11616 due-diligence respondent/supporter trajectory enters 6/7~7/2 window, (iv) LDO Accumulation Batch 1 remaining 274.31 stETH has 9 days left until 6/14 close, (v) Nemo director appointment added as Snapshot agenda item (starting June 23).
  • EIPOH #100 (6/2) follow-up flow -- end of the 14-day EIP-7701 Withdrawn window + follow-up for EIP-867 revival PR #9594 (retry after 8 years, attempt to standardize ETH recovery mechanism) + ERC-7813 Last Call.

Technical risk monitoring

  • 16 consecutive days without client releases -- as of week-end (6/5). HIGH-risk 3 items (Besu CVE-2026-34480/34478 + Erigon v3.4.0 segfault + Geth v1.17.3 structLog) carried over unresolved for 16 days. Monitor GitHub Releases for EL/CL releases supporting Glamsterdam devnet-5 right after ACDT #82 (6/8) (EIP-8037 / EIP-7928 BAL / EIP-8246 implementation tags).
  • dump frozen 6 days (5/31~6/5) vs meta EIP commit signal -- dump right after ACDE #238 (6/4 14:00 UTC), at 6/5 00:30 UTC, was not updated — need to raise priority of dump normalization layer — review integrating meta EIP commit polling into scripts/fetch_forkcast.py + monitor whether EIP-7805 Hegota Scheduled / EIP-8148 Proposed are reflected on 6/6~6/9.
  • EIP-8130 finalize pass 4 commits + no Review promotion -- remains Draft as of week-end + absent from ACDE #238 agenda — window to verify whether follow-up EIP-8130 commit bursts occur 1~7 days after 6/2 — AA follow-on candidate strengthening hypothesis.
  • Follow-up to end of DVV DVT incentives -- monitor dvstETH → EarnETH (Mellow Protocol) migration trajectory + whether similar DVT incentive tracks such as cSSV Syndicate Boost (ongoing 7 days after 5/29) apply the 1-year window.
  • PQ urgency narrative external quantum-computing progress trajectory -- impacts both ECC-based secp256k1 transaction signatures and BLS validator signatures — tracking CL client validator-key-management roadmap is required.

EIP-2537 EIP-2780 EIP-2926 EIP-2935 EIP-4758 EIP-4844 EIP-5920 EIP-6110 EIP-6466 EIP-7251 EIP-7594 EIP-7685 EIP-7701 EIP-7702 EIP-7732 EIP-7805 EIP-7851 EIP-7928 EIP-7975 EIP-7979 EIP-8081 EIP-8130 EIP-8131 EIP-8141 EIP-8148 EIP-8151 EIP-8173 EIP-8222 EIP-8243 EIP-8279 EIP-8282 EIP-8286 EIP-8287

Reference Sources

Daily Briefings (This Week)

  • 2026-06-01 Daily Briefing -- static Monday entry + 5 Lido 5/29 items continuing for 3 days since 5/29 + new ERC-8004 VNI + Evidential Survivability CROPS + EIP dump stabilization + SRv3/CMv2 unpublished Day 9 + ACDT #81 same day
  • 2026-06-02 Daily Briefing -- (partial ACDT #81 results reflected) PQ Interop / FOCIL / ACDE #238 countdown with 2 days left until 6/10
  • 2026-06-03 Daily Briefing -- new Chainnodes stVault Basic Operator application + EIP-7701 Withdrawn + EIP-8130 35-minute burst + PQ urgency strengthened after 6/2 + EIP-8148 0x03 WC removal + EIP-8133 Review + P2P Networking #2 same day + ACDE #238 1 day until 6/4 + dump frozen 4 days + Lido cool-down partially lifted
  • 2026-06-04 Daily Briefing -- ACDE #238 same day + ERC-8286 Modular Accounts for Frame Transactions + PQ transition triangle (PQ Interop #42 + PQ PK Registry + Shor)
  • 2026-06-05 Daily Briefing -- official Lido SRv3 LIP-35 proposal + ACDE #238 Hegota 7 candidates + EIP-8130 finalize burst 4 commits + EIP-8081 EIP-8148 listing + new EIP-8282 + ETM #5 5 days left until 6/10 + Lido Nemo Director + Q1 Financial + DVV Migration + dump frozen 6 days + infra 16-day gap

This Week's Recommendation Notes

This Week's Lido Tracker Notes

This Week's Protocol Call Notes

Key External Sources

Previous Weekly Report

  • 2026-05-29 Weekly Report -- MPBC + PeerDAS Constantine + Lido CMv2 Prover Bot Funding (245k → 3,829 64:1) + Sepolia testnet sunsetting + EIP-7701 Withdrawn notice + Lido governance 7-track multiplexing

Written by @r2jamong | 2026-06-05 (Friday · June first week close W23 day 5 · 1 day after ACDE #238 · 3 days until ACDT #82 · 5 days until ETM #5 on 6/10 · 18 days until Lido June Snapshot · 2 days after SRv3 LIP-35 proposal · 16-day client release gap · dump frozen 6 days)