HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
OffchainLabs
prysm
Go2020–2022
OffchainLabs / prysm

prysm

Go implementation of Ethereum proof of stake

6Distinct people
13Mentions
0Explicit recommenders
3.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Go implementation of Ethereum proof of stake

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, 3:03:16 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 month13 dated mentions

Observed mentions: 2020-12-01 15:26:38 UTC to 2022-09-15 04:06:31 UTC.

012342020-12-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsDec 20202021-01-01 00:00:00 UTC to 2021-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-02-01 00:00:00 UTC to 2021-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-03-01 00:00:00 UTC to 2021-04-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2021-04-01 00:00:00 UTC to 2021-05-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-05-01 00:00:00 UTC to 2021-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-06-01 00:00:00 UTC to 2021-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-07-01 00:00:00 UTC to 2021-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-08-01 00:00:00 UTC to 2021-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-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 commentsOct 20212021-11-01 00:00:00 UTC to 2021-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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 comments2022-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): 1 mentions; 0 submissions, 1 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 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
Dec 20202020-12-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
Jan 20212021-01-01 00:00:00 UTC2021-02-01 00:00:00 UTC000
Feb 20212021-02-01 00:00:00 UTC2021-03-01 00:00:00 UTC000
Mar 20212021-03-01 00:00:00 UTC2021-04-01 00:00:00 UTC413
Apr 20212021-04-01 00:00:00 UTC2021-05-01 00:00:00 UTC101
May 20212021-05-01 00:00:00 UTC2021-06-01 00:00:00 UTC101
Jun 20212021-06-01 00:00:00 UTC2021-07-01 00:00:00 UTC000
Jul 20212021-07-01 00:00:00 UTC2021-08-01 00:00:00 UTC000
Aug 20212021-08-01 00:00:00 UTC2021-09-01 00:00:00 UTC000
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 UTC101
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 UTC101
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC211
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC110

What Hacker News says

13 sources

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

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
I am one of the maintainers of the Go implementation of Ethereum proof-of-stake, called Prysm (github.com/prysmaticlabs/prysm) and also implemented a "slasher" in Go that can be used to slash malicious validators. Anyone can run a slasher and you don't need to have 32 ETH to do so. As long as your slasher software can prove that a validator committed a slashable offense, you can submit this proof to any full node to proceed with slashing the malicious actor. It is permissionless, global, and we only need a few honest slashers in the world for the system to work correctly
In Mainnet Merge Announcement
> Our current (Ethereum) clients are a hundred thousand lines or so for proof-of-stake. Well, not quite. Prysm[1] has a pretty harrowing codebase, but it’s not huge. You can grep all of the ick in a handful of minutes. :) [1] https://github.com/prysmaticlabs/prysm edit: I stand corrected! I guess it's been a while since I took a peep. Don't say I didn't warn ya! ------------------------------------------------------------------------------- Language files blank comment code ------------------------------------------------------------------------------- Go 1496 32842 20431 257311 C 3 3528 874 4783 Bourne Shell 31 348
Read the rest
278 2304 YAML 15 43 51 1343 C/C++ Header 5 456 239 666 C++ 1 31 64 182 DOS Batch 1 18 7 145 PowerShell 1 21 8 98 ------------------------------------------------------------------------------- SUM: 1553 37287 21952 266832 -------------------------------------------------------------------------------
In Proof-of-Stake and Stablecoins: A Blockchain Centralization Dilemma
I want to add more clarity on where Ethereum currently stands. I am one of the devs that worked on proof of stake and the future of the Ethereum protocol, bundled into an umbrella term called "Ethereum 2.0". Eth2 is a monumental research effort to create a blockchain that makes no compromises on security, scalability, and decentralization. Given Ethereum is live today, secures a ton of value, and runs a lot of applications, it is almost impossible to upgrade to 2.0 via a simple network upgrade. As such, the project is split into phases. The first phase is a proof of stake chain that runs _in parallel_ to Ethereum today. People can join as validators via a "one-way burn" smart contract. The next phase is then "merging" the state of Ethereum today with this new chain using proof of stake via a docking process. That is, Ethereum will continu
Read the rest
e to function normally, but mining will be disabled and consensus will utilize proof of stake instead. My implementation of Eth2 is a client called Prysm written in Go here (https://github.com/prysmaticlabs/prysm). Previous attempts at proof of stake were either too expensive, too centralized, or hard to scale to a large enough number of validators. After many years of research and hard work, and leveraging really awesome cryptography for signature aggregation called BLS (Boneh–Lynn–Shacham), the first phase launched December 1st, 2020 and the current proof of stake chain is now securing over $10bn worth of value at the consensus layer. A few important things to keep in mind: - Ethereum development for its future is quite decentralized, with 4 different teams having implemented high-quality, production clients for proof of stake. These teams are independent of the Ethereum Foundation. Most other blockchains have only one, canonical client implementation that has very large majority share - The "merge" is happening later this year or possibly very early 2022 - The technology used in Eth2 is quite a breakthrough in cryptography and I urge those curious to dig deeper. Using BLS signatures, the protocol can support millions of validators at the consensus layer EDIT: readability
In Ethereum Breaks Past $3k
I am one of the implementers of Ethereum Proof of Stake (https://github.com/prysmaticlabs/prysm) and I would like to clarify a lot of misconceptions around Ethereum and why we find this technology so exciting: - Proof of stake has serious flaws if done from scratch, as you are trying to secure a network using value created out of thin air. Ethereum is migrating to proof of stake from proof of work, and has already built up a security pool of over $200bn USD market cap and a significant amount of activity. ETH as the native asset required for proof of stake has enough security pool to allow the migration to make sense. - "You have been talking about proof of stake for years, wake me up when it happens". We launched proof of stake on December 1st, 2020 https://www.coindesk.com/valid-points-ether-staked-eth-2-0-q.... This runs as a parallel
Read the rest
chain that users deposit ETH into to participate in consensus via a bridge contract. The next step is to merge the current Ethereum chain to use this new chain's consensus, and we are working on this to happen late this year. - "There is a vibrant developer community, but for what? All speculation?" Yes, speculation was and is ever present in this new technology given how permissionless it is. This means anyone around the world can interact with the blockchain without a gatekeeper. However, there is an incredible amount of financial innovation happening on Ethereum that didn't even exist back in 2017. Really well-thought out stablecoins, flash loans (which are a blockchain native concept), automated market makers such as Uniswap which had more trading volume than Coinbase https://www.theblockcrypto.com/linked/79775/uniswap-coinbase.... We have privacy technologies such as Aztec Protocol or Tornado Cash. We have zero-knowledge proof games such as DarkForest. What makes me personally excited is that Ethereum is like this global, shared computer where every application deployed immediately opens a composable API for others to interact with by design, creating infinite possibilities. - Ethereum's development is far more decentralized today than it was years ago. Ethereum proof of stake was developed by 4 independent teams, unaffiliated with the Ethereum Foundation, and had a successful launch this past December 1st, 2020, and no, Vitalik cannot roll back the chain. - "Some other blockchain already had proof of stake and have been running for years". What makes Ethereum proof of stake special is it takes no compromises between decentralization, security, and scalability. At the base layer of the blockchain, Ethereum uses really neat cryptography known as BLS signatures (https://medium.com/cryptoadvance/bls-signatures-better-than-...), which allow for signature aggregation at scale. This means there can hundreds of thousands or millions of consensus participants with minimal network overhead, compared to other chains which have a permissioned set of < 100 consensus participants. Moreover, Ethereum is fully permissionless at the consensus. Anyone can run a validator at home easily on a consumer laptop. You don't need to buy ASICs, live in a country where electricity is cheap, or anything of that nature. I urge everyone here to look deeper into Ethereum for what it offers and look at the depth of innovation happening in this ecosystem. Happy to answer any questions, as there seems to be a lot of misinformation.
In Ethereum: A Store of Value with Cash Flow [pdf]
I'm one of the maintainers of one of the implementations of eth2 live today (https://github.com/prysmaticlabs/prysm) and can help offer more context on this. Ethereum proof of stake has been live since December 1st and it currently secures over 6 billion USD worth of value https://beaconcha.in/. Currently, this is a chain that lives in parallel to the proof of work chain we know as Ethereum today. The idea is that over this coming year, the entire state of Ethereum will be "merged" into this new chain that uses proof of stake consensus via a docking process. "Escalating the eth2 merge" means there is more expedited work from researchers and developers when it comes to performing this critical decision. Since eth2 consensus is already live and running correctly with a large set of validators, miners cannot censor this new chain and therefo
Read the rest
re cannot really stop the merge.
In Vitalik escalates ETH 2.0 merge as miners plan a 51% attack
This is not true. I am one of the maintainers of https://github.com/prysmaticlabs/prysm, one of the main client implementations of eth2 today. My team is unaffiliated with the Ethereum Foundation. There are also 3 other client implementations of the protocol that are very robust and done by independent teams in different parts of the world. We also can't force users to accept all our changes, and development on ETH's infrastructure has indeed been trending towards more decentralization. There are few blockchains out there today with more than 1, production-quality client implementation.
In Vitalik escalates ETH 2.0 merge as miners plan a 51% attack
I am one of the maintainers of one of the main implementations of eth2 https://github.com/prysmaticlabs/prysm, which runs a large portion of the current network. We are not affiliated with the Ethereum Foundation. Any ideas or changes need to be implemented into code and shipped to users. Development is decentralized, as there are 4 client implementations of eth2 today. Vitalik does not control our code, of course.
In Vitalik escalates ETH 2.0 merge as miners plan a 51% attack
Core dev of ETH here. There are at least 100 people from independent teams unrelated to the Ethereum Foundation working on the transition to proof of stake for ETH, which just launched this December 1st. https://www.coindesk.com/ethereum-2-0-beacon-chain-goes-live.... This did not require any "Vitalik intervention". My team is not even affiliated with the Ethereum Foundation and we maintain one of the main implementations of the protocol: https://github.com/prysmaticlabs/prysm
In SEC charges Ripple and two executives
Eth2 dev here, maintainer of https://github.com/prysmaticlabs/prysm, one of the implementations currently running the blockchain written in Go. This has been a monumental effort. There are 3 other implementations in mainnet, and consensus is running perfectly. Few other protocols in blockchain have more than one dominant implementation. The beauty of eth2 comes from its efficiency in signature aggregation: https://twitter.com/technocrypto/status/1330150362427387910. This tweet thread summarizes the importance of the technology used.
In Ethereum 2.0 launches

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.