FOCIL Breakout #045
Transcript
- Jun Song
gm
- Prysm
involved in devnet 2/3, currently landing FOCIL stuffs in our trunk branch
- Jihoon
https://github.com/ethereum/consensus-specs/pull/5740 https://github.com/ethereum/consensus-specs/pull/5741
- Mehdi Aouadi
I’d also like to understand if this IL deadline (8s -> 9s) change is scheduled for the next devnet or if it should be deployed to heze-devnet-3 https://github.com/ethereum/consensus-specs/pull/5727
- Jun Song
Replying to "I’d also like to und..." AFAIU currently devnet-3 uses 7500 bps - it’s configurable from yaml file at the startup
- Mehdi Aouadi
Reacted to "AFAIU currently devnet-3 uses 7500 bps - it’s configurable from yaml file at the startup" with 👍
- Justin Florentine
but i am not a CL dev
- Justin Traglia
Replying to "but i am not a CL de..." But your input still matters 😄
- Justin Florentine
Reacted to "But your input still matters 😄" with ❤️
- Justin Traglia
Oh I see now, sorry.
- Jihoon
- Nico Flaig
is_bid_compatible_with_head
- Jihoon
Marc's PRs - https://github.com/ethereum/EIPs/pull/12394 - https://github.com/ethereum/consensus-specs/pull/5698 - https://github.com/ethereum/execution-apis/pull/911 Jihoon's PRs - https://github.com/ethereum/consensus-specs/pull/5772 - https://github.com/ethereum/execution-apis/pull/960
- Mehdi Aouadi
Definetely prefer the validation abstraction
- Nico Flaig
we can get rid of inclusion_list_bits then in payload_attributes sse event
- Mehdi Aouadi
So FOCIL <> FRAME would be in hegota-devnet-0 which is not scheduled yet right?
- Nico Flaig
will likely be traveling
Call summary
Targets
- •FOCIL devnet-0 (with FOCIL-frame interaction) — after DEF CON; timeline TBD - 00:39:00
Decisions
- •Tentative preference for PR #5741 (only-timely IL bid selection) over #5740; final decision deferred pending bitlist-in-fork-choice discussion - 00:19:22
- •Next FOCIL breakout rescheduled to November 10, 2026 - 00:41:16
Highlights
- Spec Updates:
- ·PR #5741 preferred over #5740: proposer considers only timely ILs when selecting bids, aligning with attester view and closing late-IL griefing attack - 00:08:06
- ·Second attack vector: builder broadcasts high early bid before IL deadline to crowd out compliant bids; fix is P2P gossip rule ignoring bids before IL deadline - 00:09:16
- ·PR #5769: Lodestar picks IL-unsatisfied payload as head; spec bug allows non-compliant payload to become head in current and next slot; fix under discussion - 00:25:22
- ·New FOCIL-frame engine API approach (Jihoon PRs #5772, execution-apis #960): CL passes raw ILs to EL instead of deduped IL transactions; EL handles deduplication and omission claims; max bandwidth overhead ~4.4% at 20M gas limit - 00:31:06
- Client Updates:
- ·Nethermind: quick slots and FOCIL devnet-3 changes implemented - 00:04:59
- ·Besu: quick slot feature not yet implemented; compliant only if slot time stays at 12s - 00:05:18
- ·Lodestar: FOCIL devnet-3 changes in trunk branch, merging into unstable - 00:06:11
- ·Prysm: FOCIL work landing in trunk, involved in devnet-2 and devnet-3 - 00:07:13
- Organizational:
- ·Next FOCIL breakout pushed two weeks to November 10 due to DEF CON travel - 00:41:16
- Testing Progress:
- ·FOCIL-frame interaction design must be settled before targeting FOCIL devnet-0; timeline not yet set, likely after DEF CON - 00:39:00
Action Items
- •CL client teams - Review PR #5769 (IL-unsatisfied payload as head bug) and suggest fixes - 00:25:13
- •EL and CL client teams - Review and provide feedback on FOCIL-frame engine API PRs (consensus-specs #5772, execution-apis #960) ahead of L1 days discussion - 00:31:24
Key decisions
Tentative preference for PR #5741 (only-timely IL bid selection) over #5740; final decision deferred pending bitlist-in-fork-choice discussion
Proposer considers only timely ILs when selecting bids to align with attester view and close late-IL griefing attack.Next FOCIL breakout rescheduled to November 10, 2026
Rescheduled due to DEF CON travel.
AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.