Efficiencies Unlocked by a Post-Merge Execution Client
The lightweight and performant execution layer client being developed by Nimbus will play a key role in improving the Ethereum network's decentralisation and resilience. Work on this client continues alongside the development of the consensus layer (CL) client, verified Web3 proxy, and client for the Portal Network.
The Nimbus EL client is being developed and optimised specifically for implementation on the post-merge Ethereum blockchain.
When Ethereum migrated mainnet consensus from Proof-of-Work to Proof-of-Stake with the merge, existing execution-layer clients were updated to align with this change, although many still retain compatibility with the legacy consensus protocol.
The post-merge approach used in the design of the Nimbus EL client allows it to be simpler and lighter than its legacy counterparts, as it does not need to maintain backward compatibility with pre-Merge network architecture.
This design philosophy aligns with Nimbus's mission to create lightweight and efficient software for validators that can be used in various configurations and within resource-optimised environments.
Key improvements in the Nimbus Execution Client
The Nimbus execution client differs from others in several key aspects, most notably in its lightweight design and optimisations unlocked through the client being designed for deployment on the merged Ethereum network.
Unlike typical execution clients that store multiple full states, the Nimbus EL client stores only one base state that is updated when finality is reached. Non-finalised states are stored in memory as diffs, which aim to improve the performance and simplicity of the client’s state management. This could potentially use more RAM than other clients, but it aims to deliver better efficiency than the full state trie management system used by typical clients.
Reliance on the consensus client is part of a design philosophy which sees the Nimbus execution client working more closely with the consensus layer than its counterparts, opting for a more integrated approach than the more disparate operation of execution and consensus clients in typical setups.
Tighter consensus layer integration reduces unnecessary synchronisation work done by the execution client, bringing further optimisations and efficiency improvements.
Not only is the Nimbus EL client designed to be lightweight, but it also features flexible infrastructure that could see it tightly integrated with consensus clients and other projects like the Portal Network. The design of the Nimbus execution client also accounts for the possibility of operating the execution client, beacon node, and validator client in a unified node configuration, running in one process across two threads. This could deliver a lightweight node implementation that would be much more efficient and demand far less computing power than typical node setups.
Applications that can benefit from a lightweight execution client
It can be seen from the design of the Nimbus execution client that it aligns with the philosophy that drives the development of the team’s other projects - namely improving the decentralisation, client diversity, and resilience of the Ethereum network by creating a flexible, lightweight validator client capable of running on a variety of hardware configurations.
The benefits of a lightweight execution client designed with a post-merge approach are particularly pronounced for use cases that prioritise current or recent state over deep historical data, and those operating in resource-constrained environments.
For solo validators, a lightweight execution client paired with a similarly resource-efficient consensus client offers a way to stake and secure the network while minimising overheads. By delivering a unified node configuration that can run on a range of hardware, Nimbus further aims to lower the barriers for anyone to participate in the Ethereum network.
Applications where quick state updates are important but rapid access to archival data is not necessary could benefit from the improved performance of the Nimbus execution client. DeFi protocols could enjoy quicker state queries and updates by running a more performant node, and the same is true for web3 marketplaces and data oracles.
Developers building light clients and mobile dapps could also benefit from a lightweight execution client, as this may allow their users to run light nodes on their own devices, removing the reliance on a centralised server for transaction generation and giving users full control over their assets and information.
Light client implementations, or even full node configurations, could be run locally by users of web3 social media platforms and messaging apps, allowing these to be truly censorship-resistant and decentralised.
From solo stakers and DeFi protocols to mobile dApp developers, the Nimbus client provides flexibility and performance improvements across various use cases. These in turn improve the decentralisation, client diversity, and security of the Ethereum network.
Development on the Nimbus execution client is ongoing, and to learn more or get involved, visit the GitHub repository.