EIPsInsight

Loading Experience

Preparing your insights...

Loading0%
FOCIL2026-02-10_028

FOCIL Breakout #028

2026-02-10 2 decisions 161 transcript lines

Transcript

Ask about this call

Answered from this call's summary and transcript only.

AI-generated — verify against the recording.

Call summary

Targets
  • February 19th - ACDC call to decide CL headliner and review CL spec — 00:09:41
  • End of week - CL spec PR submission with proposed changes — 00:21:01
Decisions
  • IL bitlist serves informational purpose only; not enforced in fork choice — 00:13:27
  • Payload IL compliance validated against local view, not builder's bitlist — 00:14:20
Highlights
  • Research Updates:
    • ·One-slot delay analysis: only 0.1% improvement in inclusion; 20% transactions already included — 00:22:00
    • ·Censorship detection: transactions valid, above 10-25th percentile priority fee, pending 2+ blocks — 00:24:48
    • ·Full IL inclusion recommended over censorship-only ILs based on current data — 00:25:21
  • Specification Changes:
    • ·IL bitlist added to bids as signal; informational only, not used in fork choice — 00:11:01
    • ·PTC validates bitlist inclusivity; payload can be compliant even with non-inclusive bitlist — 00:12:21
    • ·Attesters validate IL compliance; expect beacon block to reorg IL-noncompliant envelopes — 00:14:44
  • Fork Status And Schedule:
    • ·FOCIL proposed as Hegotá headliner; CL headliner decision on Feb 19 ACDC — 00:09:00
    • ·CL spec updates targeting Feb 19: IL bitlist inclusivity and compliance checks — 00:09:41
Action Items
  • Jihoon — Finalize CL spec PR with IL bitlist and compliance check changes — 00:10:47
  • Pelle — Complete Block Native data analysis for higher resolution delay research — 00:22:00

Meeting chat1

Key decisions

  • IL bitlist serves informational purpose only; not enforced in fork choice

    IL bitlist is informational and does not affect fork choice
  • Payload IL compliance validated against local view, not builder's bitlist

    Payload IL compliance is validated against the local view, not the builder's bitlist