Light and High Performing Ethereum Clients

Run Nimbus on lightweight devices or enterprise-grade servers with equal ease and peace of mind. Trusted by solo stakers and node operators alike.

Nimbus clients

Consensus client

Monitor the Beacon Chain and join the network as a validator to participate in proof of stake consensus.

Verified web3 proxy

Independently verify data received from RPC endpoints and add a layer of protection.

Portal client

An ultra-light client that enables users to interact with the Ethereum blockchain in a trust-minimised manner.

Execution client

A lightweight execution layer client to complement the consensus client - coming soon.

[01]

Easy to use

Nimbus offers a simple and easy to use consensus layer client that combines Beacon Node and validator client duties in one package, while also offering the flexibility to run the two independently.

[02]

Lightweight

Nimbus' low resource footprint makes it an attractive option for solo stakers. It's low CPU and memory consumption is also attractive for Institutional node operators, as it leaves more headroom on a server for when Ethereum network is under stress, reducing the risk of failover.

[03]

Resilient

Nimbus offers the ability to connect the validator client with multiple Beacon Nodes. It also supports connection with multiple execution layer clients, creating redundancy and resilience in your setup.

[04]

Secure

Nimbus has undergone extensive security testing from some of the leading security firms in blockchain technology, including ConsenSys Diligence, Trail Of Bits, and NCC Group.

Run the Nimbus consensus client
in one of three ways

Simple setup

Setup the Nimbus Beacon Node with validator client duties built in.

Beacon Node setup

Use Nimbus Beacon Node with an alternative validator client.

Validator setup

Use Nimbus validator client with an alternative Beacon Node.

Community feedback

Nimbus is trusted by Etherem validators diverse in both size and operating requirements. But don't just take our word for it.

Lido@LidoFinance

🧩 CSM Client Diversity Survey data also highlights a diverse mix of EL and BN client usage among CSM operators. Top combinations: • @ethnimbus x @NethermindEth (used by ⅓ of respondents' validators) • @lodestar_eth x Nethermind • @Teku_Consensys x Nethermind

liftlines@liftlines

Wow, @ethnimbus + @NethermindEth combo rocking it amongst CSM operators 👏👏🏽

EthStaker@ethStaker

Compounding On Giraffe from @ethnimbus

ethOS@EthereumPhone

Love to the @ethnimbus team for displaying the dGEN1 at their Devcon booth! ethOS v4 on the dGEN1 will have Nimbus light client embedded at the OS layer, your own personal RPC 🥹

ethOS@EthereumPhone

Connect directly to Ethereum with onboard @ethnimbus and Helios light nodes Trustless. Liveness. Never worry about 3rd party downtime again Only on ethOS

liftlines@liftlines

Just in time, with the report published by @miga_labs comparing CL client after Dencun @ethnimbus clearly shines on both minimal CPU and Memory consumption in this study! Read more on it here: https://migalabs.io/blog/post/ethereum-hardware-resource-analysis-update

Nimbus@ethnimbus

Yes, it's true - with @ethnimbus you run multiple Execution Clients simultaneously paired with the Nimbus CL! 🖇️ Do your bit to improve Execution Layer client diversity without any stress, with Nimbus Consensus client. https://nimbus.guide/eth1.html#running-multiple-execution-clients Sharing this again as there was an overwhelmingly positive reaction to the previous post!

SenseiNode@SenseiNode

✨ Using minority clients truly pays off ✨ Client distribution is critical for the continue development of #Ethereum and its decentralization. We are one of the few node operators using @ethnimbus unique feature connecting Nimbus CL with both Nethermind and Geth ELs. This means that if one fails, we switch back to the other and maintain uptime, while supporting minority clients. Learn more in the following link ↓

Samuel Chong@stakesaurus

- 30-day performance: Pre-Alan fork on SSV - 1-day performance: Post-Alan fork Visibly lower CPU usage on my Intel NUC i5 running 60 validator key shares. Client combinations: @NethermindEth EL + @ethnimbus CL + @ssv_network DVT