The Nimbus Ethereum client v0.3.0 alpha, along with the Nimbus verified Proxy, are medium-urgency releases which introduce a single combined binary for both the consensus and execution layers, along with a unified client interface to both consensus and execution layers; more detail on this at https://blog.nimbus.team/the-nimbus-unified-client/
-
Provide the Nimbus client as a single binary: #3966
-
Provide multiarch images for the Nimbus single binary: #3988
-
Provide a C API for verified proxy: #3745
-
Support multiple Web3 endpoints for verified proxy: #3891
-
Support multiple frontends for verified proxy: #4000
-
Support by the verified proxy to download blocks in parallel: #3892
-
Support getBlobsV3 in execution and unified client: #3893
- Avoid startup issues with corrupt databases: #4023
The Nimbus EL v0.2.2 alpha is a high-urgency release for the impending Fusaka fork and low-urgency for the Hoodi and Sepolia testnets.
-
Improve performance of certain addition, multiplication, and pairing precompiles by 80+%: #3747
-
Dynamically adjust block persistence batch sizes to safely maximize throughput: #3750
-
Optimize Portal database pruning performance by 150x: #3753
-
Optimize Osaka modExpFee calculation: #3784
-
Add support for runtime ChainId in Portal ENR field: #3749
-
Fix segfault when processing bad block: #3733
-
Fix crash while syncing: #3751
-
Fix segfault when database directory is locked or in use: #3736
-
Fix secp256r1 verification in certain cases: #3759
-
Fix forkId compatibility according to EIP-2124 and EIP-6122: #3803
-
Fix Portal bridge crash when JSON-RPC methods not available: #3785
-
Fix out-of-order execution client launch logging: #3728
The Nimbus EL v0.2.1 alpha is a high-urgency release for the Hoodi, Sepolia, and Holesky testnets, due to their impending Fusaka forks. There are no Verified Proxy changes since v0.2.0.