Topic

News & Announcements

A collection of 38 articles

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

The Portal Network: Optimizing Ethereum data storage

The Portal network is a content-specific distributed storage network designed explicitly for storing Ethereum data. Unlike generic distributed storage networks like Codex, IPFS, or Swarm, the Portal network can be optimized for the specific types of data it handles, improving data access and verification processes. This specificity allows nodes in

Unbundling the Nimbus consensus client - Part one

Nimbus has released a production-ready version of its validator client, addressing a key demand from node operators and advanced users. The client is highly performant and requires low resources, allowing it to run on a range of devices — from embedded systems to enterprise servers. By default, the Nimbus consensus client&

Nimbus client 2022 year-end recap

As 2022 winds down, the Nimbus research team reflects on another year of building the infrastructure needed to maximally decentralize the Ethereum network. Here's our recap of updates to the Nimbus consensus client over the past 12 months. Nimbus' 2022 unpacked The broader Ethereum ecosystem enjoyed a

Nimbus Consensus Layer - past, present, and future

the image above shows 40 of our dependencies purpose built by us for Nimbus and the wider Status ecosystem It's happening! #eth2 genesis is upon us - stay tuned as we prepare a release with everything necessary to run @ethnimbus! Thanks to researchers, supporters, other client teams and

Nimbus - Execution Layer

It is a little known secret that, in addition to our consensus layer (eth2) client we are building out an execution layer (eth1) client - with the objective that it should be ready for the merge. Why is this important? One topical reason is client diversity. 1/ A diverse execution-layer

Nimbus update - Pre-merge interop!

In the words of Danny Ryan, Altair is here and the Merge is coming! Finalized no. 29https://t.co/ssVYW3M8d7 Altair is here; the Merge is coming. tl;dr below — dannyryan 🚂 (@dannyryan) September 28, 2021 We first simulated the merge back in April/May of this year. > This is

Fluffy: ultra-light client for Ethereum

How can we design networks that allow for clients to show up with small amounts of data, contribute to the network, and for those contributions to be meaningful? – Piper Merriam We are delighted to announce that Nimbus will be joining the Ethereum Foundation’s Portal Network team as one of

Nimbus update: v1.2 CPU 🔥

If v1.1 was the big I/O update, v1.2 is all about the CPU - together, these updates help secure Nimbus against future network growth, and provide us with a higher security margin and substantial profitability improvements. To highlight just one data point, CPU usage has been cut

Nimbus update: v1.1.0 release

Hi everyone, We're excited to announce that we pushed our v1.1.0 release over the weekend. This is a big one for us :) There are many highlights in this release. In particular, v1.1.0 contains substantial performance improvements to our database (we have a new schema)