The FOCIL Breakout #43 Notes Read Like a Launch Checklist. Here Is What Still Needs Fixing.

The meeting started at 13:00 UTC on September 29. Eight client teams logged in. The agenda said "Development updates, Spec updates, Testing updates, and more." What actually happened was quieter and more telling: most teams were close to ready for dev-net-zero, but close is not launched, and the gaps that remain are the kind that break networks.

I listened to the recording. What I heard was not celebration. It was calibration.

Key Metrics at a Glance

What Actually Happened

FOCIL Breakout #43 was a readiness check for the upcoming fossil-dev-net-zero launch. The participants included teams from Teku, Lighthouse, Nethermind, Lowestar (Go Ethereum), Bessel, and others. The format was familiar: each team reports status, blockers, and ETA.

The results:

• Bessel (Fabio): Ready for DevNet Zero. Confirmed.
• Lowestar (NC): Rebased on beta.2, spec tests passing. Ready.
• Teku (Mehdi): Fixed issues from prior DevNet, preparing new Docker image. Close.
• Lighthouse (Cristian): Close, still working on gos-sip verification and NewPayloadV6.
• Nethermind (Marc): Ready with small fixes remaining. Close.
• Hive Testing (Iván): Three failing tests remaining. Close but blocked.

The conversation that mattered most was not about who was ready. It was about what happens next.

The Competitive Landscape: Client Readiness Scorecard

This is not a race. It is a relay where every runner must hand off the baton. If one client fails validation, the DevNet does not launch cleanly. The history of Ethereum testnets is full of launches that were delayed because one team found a consensus bug at the last minute.

The Technical Translation: What FOCIL Actually Does

FOCIL stands for Fork-Choice Enabled Inclusion Lists. It is a mechanism designed to improve transaction inclusion guarantees in Ethereum's consensus layer. The idea is simple: validators publish inclusion lists that the fork-choice rule must respect, preventing block builders from censoring transactions.

What that means in practice:

• Before FOCIL: Block builders control transaction inclusion. A builder can refuse to include a transaction for any reason.
• After FOCIL: Validators can force the inclusion of certain transactions through consensus rules, not just economic incentives.

The dev-net-zero launch is the first coordinated test of this mechanism across multiple clients. If it works, FOCIL moves from specification to implementation. If it fails, the timeline for mainnet activation gets pushed back.

The Accountability Layer

Here is the question the meeting did not answer directly: who decides when dev-net-zero is "good enough" to launch?

The call ended with consensus to proceed, but consensus is not a standard. Three failing tests in Hive are not cosmetic. They represent edge cases in fork-choice behavior that could become consensus splits on a live network. Iván committed to fixing them within hours, but that commitment was made on the call, not in a documented specification.

The other unresolved item: Cristian's Lighthouse branch was "close" but not confirmed ready. Close is not a binary. In distributed systems, close means you do not know what you do not know.

Governance Lessons

The FOCIL breakout teaches three lessons about Ethereum protocol development:

1. Client diversity is a security feature, but it is also a coordination cost. Eight teams means eight codebases, eight test suites, and eight schedules. The cost of diversity is paid in calendar time.

2. DevNet launches are not neutral events. They are political commitments. Once a DevNet is announced, teams feel pressure to hit the date. That pressure can mask readiness gaps.

3. Testing is the last thing that gets done and the first thing that matters. Three failing Hive tests are not a footnote. They are a warning.

Strategic Implications and Future Outlook

The next steps from the call are concrete:

• Iván fixes the three Hive tests and confirms passing.
• Mehdi publishes the new Teku Docker image.
• Cristian shares the Lighthouse DevNet Zero-ready branch.
• The group reconvenes to discuss the interaction between FOCIL and class frames at the next breakout.

Two CFI features — EIP-8015 and EIP-8365 — were deferred to post-DevNet-Zero evaluation. That is the right call. Adding new features before the base mechanism is proven stable is how testnets become debugging exercises.

For validators and node operators, the message is: watch the DevNet launch, not the breakout notes. A successful DevNet Zero means FOCIL is ready for broader testing. A failed launch means more months of specification refinement.

TL;DR

• What: FOCIL Breakout #43 confirmed most client teams are near-ready for dev-net-zero, with 2 fully ready and 4 close
• Why: FOCIL is a consensus-layer mechanism to prevent transaction censorship by block builders
• Impact: Three remaining Hive test failures and Lighthouse verification gaps could delay the DevNet launch
• Watch: Whether the Hive tests clear and Lighthouse confirms readiness before the DevNet goes live; whether CFI features (EIP-8015, EIP-8365) make it into DevNet 1 or 2

Sources

• Ethereum Magicians — FOCIL Breakout #43, September 29, 2026
• FOCIL GitHub Issue Tracker

Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter. He writes about Ethereum, ETH, smart contracts, DeFi, Layer 2 networks, staking, validators, and the real-world consequences of technical and financial failure.