FOCIL2026-06-16_036

FOCIL Breakout #036

2026-06-16 2 decisions 518 transcript lines

Follow along

Call summary

•IL bitlists removed from spec; engine API kept as-is; EL deduplication of IELTs deferred to future change - 00:20:23
•IL enforcement turned off during non-finality (circuit breaker); 1-epoch threshold preferred over 2; final value to be confirmed after broader review - 00:47:03

Client Updates:
- ·Lodestar rebased on Glamsterdam devnet-5; bit serialization bug (Gloas version) confirmed fixed - 00:05:23
- ·Censoring builder branch works; Bharath to retest against latest Lodestar branch tomorrow - 00:05:44
- ·Lighthouse rebased on Glamsterdam devnet-5; FOCIL implementation still being tested - 00:07:23
Focil Spec Changes:
- ·IL bitlists decided for removal: can be faked by builders; no enforcement mechanism; engine API unchanged for now - 00:09:43
- ·Payload status V2 proposed: adds 'latest IL-satisfied hash' field to clarify IL compliance across branches - 00:20:37
- ·Accepted payloads (non-canonical branch) treated as IL-compliant by CL; EL must cache IELTs for head (and possibly parent) payload only - 00:22:03
- ·Non-finality circuit breaker: rough consensus to turn off IL enforcement after 1 epoch without finality (down from current 2-epoch threshold); to be confirmed via Discord - 00:47:03

•Jihoon - Open Discord thread on 1-epoch vs 2-epoch non-finality threshold for IL enforcement; gather broader input from client teams - 00:52:40
•Jihoon - Prepare write-up and spec PR covering: payload status V2, accepted-payload IL handling, and non-finality circuit breaker; coordinate test case changes with Felix - 00:57:28

IL bitlists removed from spec; engine API kept as-is; EL deduplication of IELTs deferred to future change
IL bitlists removed from spec to simplify the implementation
IL enforcement turned off during non-finality (circuit breaker); 1-epoch threshold preferred over 2; final value to be confirmed after broader review
IL enforcement turned off during non-finality to improve performance