week 0: Exploration and Consensus Finality Leaks
- I’m taking part in EPF 7 on the permissionless track, hacking on
leanstart. - Mapped the
leanstartrepo architecture and pushed PRs for client tooling and DevEx fixes. - Spun up a 6-node devnet (
ream:3 --subnets 2); the bootstrap was clean, but consensus stalled and finalisation froze ~90 minutes in while the slot clock raced on. - Exploring the implementation of client-side metrics for the P2P consensus layer (targeting Lighthouse).
As I shift my attention to systems-level engineering, it feels like the right time to resume building in public. For the next five months, I’ll be permissionlessly participating in the seventh iteration of the Ethereum Protocol Fellowship (EPF).
I spent the past year optimising the Ethereum Execution Specs Test framework. While participating in the EPF study group, I was introduced to many Ethereum concepts and organisations that implement them. One concept that caught my attention was Ethereum’s goal to make the chain quantum-resistant. I attended a presentation by a member of the Ream team, which led me to explore the organisation, what they are building, and how my current skill set can help them achieve their goal. I discovered a project ripe for optimisation: LeanStart.
LeanStart is a devnet orchestrator for lean Ethereum clients. Since I discovered it, I have mapped out the architecture, opened a couple of client tooling and devex PR fixes, and stress-tested the program by spinning up a 6-validator devnet (2 subnets × 3 pods = 6 Ream nodes) with a simple command: leanstart run ream:3 --subnets 2.
The bootstrap was flawless, but the devnet failed to sustain consensus. On my modest box (8 vCPU / 16 GB), the slot clock raced ahead to ~4,500 while the canonical chain head froze at slot 1,604 and finalisation stalled at 1,001, roughly 90 minutes in. The nodes never crashed outright; they simply lost their peers and could never claw their way back.
Another project that has caught my attention is implementing p2p consensus-layer client metrics, aiming to complete them for the Lighthouse client.
Bis später — and more to come.