Season 2 Finale w/Nethermind’s Łukasz & Marek

Wukash and Marek from the Nethermind team discuss the Ethereum development roadmap, focusing on the Pectra and Fusaka upgrades. Wukash highlights that while Pectra was technically easier than the merge, it faced challenges with Asypolia and Holensky, but recovery was effective. Marek expresses confidence in a smooth rollout of Pectra on Mainnet by the end of April, assuming successful testing.

The conversation shifts to Fusaka, where Wukash emphasizes the importance of insights from Pectra to enhance Fusaka's scoping discussions. Key features for Fusaka include Peer Dust and EOF, with a goal to finalize the scope quickly. Marek notes the expansion of core developers and the increase in proposals, leading to parallel work on various initiatives, which can complicate scoping and readiness assessments.

The idea of "leapfrogging" forks is proposed to improve efficiency, allowing simultaneous scoping of Fusaka while initiating discussions for Amsterdam. Recent ACD calls showed strong support for including EIP 7688 in Fusaka, but the complexity may delay the fork until next year. Concerns about rushed scoping discussions hindering proper implementation and testing are raised, alongside the need for a long-term adaptable plan.

The discussion also touches on EOF, with uncertainty about its future due to the focus on Pyrdas, but current sentiment leans towards retaining it. Marek expresses surprise at Tomasz's new role as co-executive director at the Ethereum Foundation, noting his organizational experience.

Marek outlines what sets the Nethermind client apart, including high validator performance, lower hardware requirements, fast syncing, and stability through rigorous testing. The conversation highlights the critical nature of client diversity to mitigate risks associated with bugs. The developers have a strong track record of addressing bugs quickly, often within hours, to minimize disruption.

A recent dialogue with Piper Miriam from the Ethereum Foundation introduced the concept of history expiry, which could optimize node storage by limiting historical data. This could significantly reduce node size, enhancing scaling and throughput. Clients like NetherMind can be configured to remove history, although preserving it remains a challenge.

NetherMind is leading in execution clients with its integration into the Portal Network, which requires further testing before full rollout. There is enthusiasm about expiring more historical data, both pre- and post-merge. Marek intends to continue in his current role while seeking growth within the Ethereum project.

Looking ahead, there is a strong emphasis on performance improvements for head processing and potential competition in the archive node space. There is interest in Layer 2 solutions leveraging NetherMind's technology for scaling, with a recognition of the need for client diversity in the L2 ecosystem. Currently, NetherMind is not fully utilized on the Ethereum mainnet, indicating untapped capacity.

The conversation also touches on increasing throughput for Layer 2 solutions and the upcoming launch of a search feature using the NetherMind client for execution, with anticipation of demonstrating the project's scalability.