FOCIL2026-11-17_046

FOCIL Breakout #046

2026-11-17 5 decisions 455 transcript lines

Transcript

At a glance

PR#5769 (GetHead tiebreaker IL compliance check) green-lit; targeting merge at next breakout after detailed review
Next FOCIL Breakout in one week, focused exclusively on PQ FOCIL
PQ FOCIL dedicated breakout — one week from November 17, 2026verify date

Detailed notes

Pq Focil

  • •soispoke: high-level PQ FOCIL design needs discussion before sizing XMSS overhead; write-up publishing today/tomorrow; FOCIL may be low PQ priority (attacker must break 16 sigs in 12s)verify date00:59:24
  • •Dedicated PQ FOCIL breakout scheduled for next week (one week, not two)01:01:46

Consensus Spec Prs

  • •PR#5792: clarifies honest validator broadcasts IL after executing payload (not at slot start); also fixes Lighthouse/Lodestar marking early ILs untimely — tentatively good to merge pending broader sign-off00:17:48
  • •PR#5785: IL retention window extended from 2 → 3 slots; ILs broadcast in slot N must survive until slot N+2 enforcement00:20:44
  • •PR#5769: modify GetHead tiebreaker to not return slot N when payload is not IL-compliant; Teku already deployed this on devnet — green-lit, targeting merge next breakout00:23:06
  • •PR#5741: (1) P2P bid propagation only after IL deadline; (2) proposer picks bid only with timely ILs; potential attack if late IL reaches proposer after most attesters — second explicit proposer deadline under discussion00:28:47

Execution Engine Api

  • •PR#956: relax IL transaction field requirement to tolerate arbitrary bytes (EL teams to verify compliance)00:07:42
  • •PR#957: 'must not' → 'should not' for blocked transactions; EIP-7805 doesn't support block transactions00:08:39
  • •PR#964: open question — new engine API vs. FCU reuse for updating payload with IL transactions; Besu (Fabio) has no strong preference; decision deferred to Discord00:09:21

Il Equivocation Proofs

  • •Proposal: include IL equivocation proofs (two signed IL headers) in envelope — 352 bytes pre-PQ, ~5 KB post-PQ per equivocation; mixed reception, soispoke strongly against00:39:00
  • •Related: new gossip topic for equivocation proofs to save ~616 KB bandwidth vs. propagating full ILs; complexity vs. rarity trade-off unresolved00:49:08
  • •Proposal: replace IL bit list with signed IL headers/roots in bid (~3 KB pre-PQ, ~38 KB with XMSS) for builder accountability on unseen ILs00:57:43

Action items

  • •EL devs review PR#964 (FCU vs. new engine API for IL payload update) and share opinions in DiscordEL client teams
  • •Open GitHub issue for PQ FOCIL breakout; share articles/concerns on PQ FOCIL ahead of next week's callJihoon / all attendees

Agenda

From the call issue #2289Show

EL

  1. feat(engine): Simplify inclusion list type
  1. Type-3 transactions SHOULD NOT be included, rather than MUST NOT
  1. feat: reuse the built payload when only inclusion list transactions change

CL

  1. Clarify honest validator's IL proposal
  1. Retain inclusion lists one slot past the request window
  1. Do not prefer an unsatisfied payload as head during its own slot
  1. Validate and select bids on the inclusion list view at the deadline
  1. IL equivocation proofs in the envelope
  1. A new gossip topic for IL equivocation proofs

  2. IL roots in the bid

  1. Reorg a block with not inclusive bitlist

Key decisions

  • PR#956: relax IL transaction field requirement to tolerate arbitrary bytes (EL teams to verify compliance)

    EL teams to verify compliance.
  • PR#957: 'must not' → 'should not' for blocked transactions; EIP-7805 doesn't support block transactions

  • PR#5785: IL retention window extended from 2 → 3 slots; ILs broadcast in slot N must survive until slot N+2 enforcement

    ILs broadcast in slot N must survive until slot N+2 enforcement.
  • PR#5769 (GetHead tiebreaker IL compliance check) green-lit; targeting merge at next breakout after detailed review

    Teku already deployed this on devnet; targeting merge next breakout.
  • Next FOCIL Breakout in one week, focused exclusively on PQ FOCIL

    Dedicated breakout scheduled for November 24, 2026.

EIPs discussed

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.