FOCIL Breakout #037
Transcript
Ask about this call
Answered from this call's summary and transcript only.
AI-generated — verify against the recording.
Call summary
Targets
- •Engine API PR #609 merge — week of June 30 or following week — 00:09:55
- •FOCIL Breakout #38 — July 21, 2026 — 00:48:39
Decisions
- •Payload attributes SSE event: tentatively adopt option 3 — add IL bits as a top-level field; revisit if Engine API changes direction — 00:14:42
- •IL bit list restored to block container but NOT enforced in fork choice for now; fork choice treatment to be determined after further design work — 00:36:23
Highlights
- Spec Updates:
- ·Engine API PR #609 (payload status V2): replaces latest-IL-satisfied hash with a Boolean IL-satisfied flag; EL must retain ILs for accepted payloads to support branch switching; near-final, targeting merge this week or next — 00:07:40
- ·Consensus spec will add comment clarifying that is_payload_il_satisfied returns true for non-validated payloads; small change, Jihoon to add — 00:10:58
- ·Payload attributes SSE event: three options discussed for exposing IL bit list to builders; tentatively going with option 3 (add inclusion-list bits as top-level field in the event) as least-invasive CL-only change — 00:11:26
- ·IL bit list being restored to block container (previously removed); fork choice enforcement deferred pending design exploration of two options: (1) reorg the block, or (2) suppress trustless payment without reorging the block — 00:15:03
- Client Updates:
- ·Teku integrated latest Glamsterdam changes into FOCIL branch but couldn't interop with Lodestar due to builder execution requests; old docker image left in place — 00:05:21
- ·Lighthouse and ethrex both need to rebase on Glamsterdam devnet 6; Lodestar PR #9541 pending merge to unblock rebase — 00:06:06
- Organizational:
- ·Next FOCIL breakout pushed one week to July 21 (Jihoon OOO around July 14) — 00:48:39
- Protocol Design:
- ·Bit list rationale: prevents honest builders from being penalized when they missed an IL due to network conditions under trustless payment; also aligns proposer incentive to select non-censoring payloads — 00:16:07
- ·No consensus yet on fork choice enforcement of bit list; near-term plan is proposer SHOULD pick a bit list that is a superset of their local IL view, but this is not checked in fork choice — 00:32:12
Action Items
- •Jihoon — Merge engine API PR #609 (payload status V2); then source execution spec test resources from Stihl — 00:09:55
- •Jihoon — Explore candidate spec implementations for bit list in fork choice; present options at next breakout — 00:37:06
Meeting chat11
- Barnabas
“A zoom call a day keeps the doctor away”
- Barnabas
welcome core gang
- Nico Flaig
no update for FOCIL
- Nico Flaig
ah we probably didn't rebase on glam devnet 6 yet
- Mehdi Aouadi
Reacted to "ah we probably didn't rebase on glam devnet 6 yet" with 👍
- Edgar | ethrex
we need to rebase on glam 6 too on ethrex
- Mehdi Aouadi
Replying to "ah we probably didn'..." I guess once this PR is merged in FOCIL it should work agin https://github.com/ChainSafe/lodestar/pull/9541
- Nico Flaig
Replying to "ah we probably didn'..." yes we merged that to unstable, so rebase should be simple
- Mehdi Aouadi
Reacted to "yes we merged that to unstable, so rebase should be simple" with 👍
- Barnabas
Sorry guys gonna drop now. Pls ping me if I can do anything for you guys.
- Nico Flaig
pretty sure we still have the bitlist in our code @NC
Key decisions
Payload attributes SSE event: tentatively adopt option 3 — add IL bits as a top-level field; revisit if Engine API changes direction
IL bit list restored to block container but NOT enforced in fork choice for now; fork choice treatment to be determined after further design work