A Lightweight Execution Client That Pairs With Nimbus

You're running an Ethereum node and watching your RAM disappear. Or maybe you're just curious whether an execution-layer client can be lean without cutting corners on security. Either way, Nimbus might be worth a look. It's an execution-layer client built to pair with the Nimbus consensus-layer client, and its stated goal is to be as light-weight as possible in terms of resources used.

What It Does

Nimbus is an Ethereum execution-layer client written in Nim. It's developed by the Status team and designed to work alongside their consensus-layer client (which lives in a separate repository, nimbus-eth2). The project focuses on efficiency and security, and the README is upfront about the priority: keep resource usage low.

The repository isn't just the execution client, though. It's also home to two other pieces of software. There's the Nimbus Portal client, which is a lightweight client for the Portal Network, and the Nimbus Verified Proxy. So if you're interested in the Portal Network specifically, this repo covers that too.

All consensus-layer work happens in parallel over in the nimbus-eth2 repo, so don't expect to find that here. This is the execution side of the equation.

Why It's Cool

• Lightweight is the whole point. Plenty of clients claim to be efficient. Nimbus puts it in the first sentence of the README. If you're running on constrained hardware or just don't want a client eating your machine alive, that's a design goal worth paying attention to.

• It's a matched pair. Running an Ethereum node means running both a consensus client and an execution client, and they need to talk to each other. Nimbus is explicitly built to pair with Nimbus, which means you're not mixing and matching implementations and hoping the integration holds up.

• Nim as the language. The project is written in Nim, which isn't the usual choice for Ethereum tooling. If you're the kind of developer who likes seeing a different stack applied to a well-known problem, there's something interesting here. The build instructions even mention a Status Nim fork, so there's some custom tooling under the hood.

• The Portal client is a bonus. The Portal Network is a set of specifications for lightweight Ethereum data access, and having a client for it living in the same repo means you get more than one thing to explore. If you're curious about where light clients are heading, this is a practical entry point.

• Apache 2.0 and MIT licensing. Dual-licensed, which keeps things flexible if you're thinking about building on top of it or incorporating parts into your own work.

How to Try It

The README keeps the build process straightforward. You'll need GNU Make, Bash, the usual POSIX utilities, and Git 2.9.4 or newer. If you use the Nix package manager, you can grab all the prerequisites with nix develop — though the README flags that as experimental.

On a POSIX-compatible OS, here's the flow:

# The first make invocation updates all Git submodules
make -j4 nimbus_execution_client

# See available command line options
build/nimbus_execution_client --help

# Start syncing with mainnet
build/nimbus_execution_client

When you want to update later, it's git pull && make update, then rebuild with make -j4 nimbus_execution_client. There's also make test if you want to run the test suite.

Windows support exists but is marked experimental. The README walks through installing Mingw-w64, Git for Windows, and cmake, then creating a symlink from make to mingw32-make. It's more involved than the POSIX path, so keep that in mind.

If you need to use binaries from the Status Nim fork, there's an env.sh script that sets the right environment variables. You can start an interactive shell with ./env.sh bash or run a single command like ./env.sh nim --version.

The repo is at github.com/status-im/nimbus-eth1.

Final Thoughts

Nimbus is a solid option if you're already in the Nimbus ecosystem or you care about resource efficiency above all else. The pairing with nimbus-eth2 makes it a natural fit for anyone running that consensus client, and the inclusion of the Portal client and Verified Proxy means there's more to dig into than just an execution client. It's not the most mainstream choice, and the Windows support is still experimental, but if lightweight is what you're after, this is a project that takes that goal seriously. Worth a build if you've got the prerequisites handy.