Sign in Subscribe

Nimbus Team

Nimbus Team

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)

The importance of client diversity leading to the merge

Note that Nimbus tends towards privacy by default making it harder for crawlers to detect it - nevertheless, the magnitude of the skewed client distribution in the above image still stands Last week we saw a small incident occur on the Beacon Chain (see here for a more complete write-up)

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)