HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
status-im
nimbus-eth1
Nim2021–2022
status-im / nimbus-eth1

nimbus-eth1

Nimbus: an Ethereum Execution Client for Resource-Restricted Devices

Systems & InfrastructureHardware & EmbeddedMobile & DesktopNetworkingFinance & Commerce
Explore on GitHubRead Hacker News discussions
3Distinct people
3Mentions
0Explicit recommenders
637GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Nimbus: an Ethereum Execution Client for Resource-Restricted Devices

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month3 dated mentions

Observed mentions: 2021-08-24 09:37:30 UTC to 2022-09-15 04:06:31 UTC.

012021-08-01 00:00:00 UTC to 2021-09-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 20212021-09-01 00:00:00 UTC to 2021-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-10-01 00:00:00 UTC to 2021-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-01 00:00:00 UTC to 2021-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2022-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-01 00:00:00 UTC to 2022-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 20222022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20212021-08-01 00:00:00 UTC2021-09-01 00:00:00 UTC110
Sep 20212021-09-01 00:00:00 UTC2021-10-01 00:00:00 UTC000
Oct 20212021-10-01 00:00:00 UTC2021-11-01 00:00:00 UTC000
Nov 20212021-11-01 00:00:00 UTC2021-12-01 00:00:00 UTC000
Dec 20212021-12-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
Jan 20222022-01-01 00:00:00 UTC2022-02-01 00:00:00 UTC000
Feb 20222022-02-01 00:00:00 UTC2022-03-01 00:00:00 UTC000
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC000
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC000
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC000
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC000
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC000
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC110
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC110

What Hacker News says

3 sources
michaelsbradley·Sep 15, 2022Submission

Ask HN: Is Ethereum's Merge one of the biggest successes in Open Source?

It certainly seems it will be remembered as a major success story for open p2p protocols on the global Internet of our time. A great multitude of developers and enthusiasts belonging or contributing to diverse teams spread across the world: developing, debating, and collaborating for years to arrive at the big event. And it's all been done very much in the public view: https://weekinethereumnews.com/ https://hackmd.io/@benjaminion/eth2_news https://github.com/ethereum/pm https://www.youtube.com/c/EthereumFoundation/videos Consensus Clients: https://github.com/sigp/lighthouse#readme https://github.com/ChainSafe/lodestar#readme https://github.com/status-im/nimbus-eth2#readme https://github.com/prysmaticlabs/prysm#readme https://github.com/ConsenSys/teku#readme Execution Clients: https://github.com/akula-bft/akula#readme https://github.com/h
Read the rest
yperledger/besu#readme https://github.com/ledgerwatch/erigon#readme https://github.com/ethereum/go-ethereum#readme https://github.com/NethermindEth/nethermind#readme https://github.com/status-im/nimbus-eth1#readme And there are many Open Source specs and libraries underlying those clients that have also involved non-trivial development and collaboration, e.g. libp2p.
22 points · Open discussion
RjQoLCOSwiIKfpm·Aug 24, 2022Submission

Ask HN: Does the Ethereum foundation really not develop a post-Merge client?

TL;DR: To use the new Proof of Stake network, you'll need 2 pieces of software in parallel. It seems only one of those is developed by the Ethereum foundation - implementations of the other one are only developed by various seemingly commercial entities - despite the foundation holding $ 1 billion in assets (see comments). Now that the PoS-merge is close, I tried to find out how to actually use it. https://ethereum.org/en/developers/docs/nodes-and-clients/ says: > After The Merge, both execution and consensus clients must be run together in order for a user to gain access to the Ethereum network. Here are the lists of implementations of those two clients: https://ethereum.org/en/developers/docs/nodes-and-clients/#execution-clients https://ethereum.org/en/developers/docs/nodes-and-clients/#consensus-clients So they do develop an execution
Read the rest
client, commonly known as "geth". It's on their own GitHub: https://github.com/ethereum/go-ethereum But the 5 consensus clients not only have websites which aren't ethereum.org - they are in fact also hosted on different GitHub accounts: https://github.com/sigp/lighthouse https://github.com/ChainSafe/lodestar https://github.com/status-im/nimbus-eth1 (yes, this is also for eth2, see "About" at top right) https://github.com/prysmaticlabs/prysm https://github.com/Consensys/teku Further, all of these 5 institutions seem to be companies from the looks of their website, not non-profit foundations. (Please correct me and pardon me if that is not true, I don't have the time to navigate through all these websites to figure out their precise legal status.) So is it true that there is no official reference implementation to run the post-Merge, Proof of Stake Ethereum? Only 3rd party software which is somehow endorsed but which you have to choose on your own still? Sure, more choice can be nice, but it would seem advantageous to have at least one trustworthy reference client instead of the users having to decide which of 5 commercial entities they trust?
15 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.