Nimbus Team

Nimbus Team

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 - checkpoint sync, era files, Vouch

(image of the Lennon Wall courtesy of IFMSA) As these notes were being written, Putin's senseless war in Ukraine left nobody untouched and Status is no exception: Our Ukrainian contributors have been forced into bomb shelters with their families as brutalities increase: here are several ways that you

The importance of light nodes in Vitalik's endgame

image courtesy of Vitalik's endgame post Preface Ethereum can support both full nodes and light clients, it contains a peer to peer layer which allows nodes to send messages to each other. While Ethereum's current architecture is not particularly well-suited to light clients, the beacon chain

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 + Nethermind - Kintsugi tutorial

Diagram courtesy of Mikhail Kalinin's Engine API design space document. Note that this diagram dates from the Amphora era, and so is not strictly accurate. Nevertheless the general communication flow between consensus and execution for Kintsugi is the same. Kintsugi, also known as kintsukuroi, is the Japanese art

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

Ethereum is green

Preamble: energy and power The unit of energy we’ll use in this post is the kilowatt-hour (kWh). This quantity is called “one unit” on electricity bills, and it costs a domestic user about 12 cents in the US. When discussing power, we’ll use kilowatt-hours per day (kWh/d)