HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ethereum
consensus-specs
Python2019–2022
ethereum / consensus-specs

consensus-specs

Ethereum Consensus Specifications

10Distinct people
13Mentions
1Explicit recommenders
4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Ethereum Consensus Specifications

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

You get assigned by a random number generator to create the next block. If you fail to create it your only penalty is the opportunity cost (i.e., you miss on the reward that…

pa7x1 used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:02:05 AM 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 year13 dated mentions

Observed mentions: 2019-01-03 08:35:23 UTC to 2022-12-25 10:14:10 UTC.

012342019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022

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
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC211
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404

What Hacker News says

4 sources
Disclaimer: I work on Ethereum core development. One of the coolest things happening that will be available to everyone over the coming year is something called a light client, which is essentially a very light, validating node that tracks the head of the chain with certainty, and can be used as an alternative to services such as Unfura. In the future, Metamask will probably be a light client that actually tracks the head of the chain and can validate proofs of user account state. Source: https://github.com/ethereum/consensus-specs/blob/dev/specs/a...
In Web3 Is Not Decentralization
The total ETH created does depend on the amount staked. Here's a table[1] and formula[2]. The total reward doesn't go up linearly with the number of validators, but it does go up. Lowering the incentive for attacks like you mention is a reason for that. And while having fewer validators gives you a somewhat higher reward per validator, it's still that case that all validators get the same reward in any given block. Everyone is equally competitive. Someone who reinvests will get higher absolute rewards than they got before, but they pay the price of locking up more capital. In the same way, a miner could reinvest profits into more mining equipment, but that doesn't make them more competitive, just bigger. Their profit margin will be the same (barring economies of scale that don't exist in staking). [1] https://docs.ethhub.io/ethereum-roadm
Read the rest
In Ethereum staking – More sustainable crypto
As of 01 Dec 2020, there is already another Ethereum mainnet chain (Eth2 Phase 0) running in parallel with and dependent upon the Eth1 mainnet chain: https://beaconcha.in/ https://beaconscan.com/ https://github.com/ethereum/eth2.0-specs/tree/dev/specs/phas... Vitalik is proposing a role reversal to take place earlier than it was previously planned (not completely accurate in a technical sense re: previous plans, but effectively the same): Eth1 mainnet will hand-off consensus responsibility to Eth2 mainnet (PoW -> PoS), while Eth1 nodes continue to "run the code" that executes smart contracts / processes transactions. If the plan is put into motion, and as long as some miners / mining pools don't yank the plug on their mining nodes in the canonical Eth1 mainnet, then the canonical mainnet — per consensus among the Ethereum Foundation and a
Read the rest
ligned developers, Eth2 validator operators, orgs/companies/exchanges/etc — will transition suddenly from Eth1 (PoW) to Eth2 (PoS). And that will be the end of all mining on the canonical Ethereum mainnet. Miners/pools who find it impractical or undesirable to reallocate resources from mining to staking may band together to continue running an alternate mainnet chain based on PoW (ETW?); market forces would then decide whether that chain is viable, as well deciding the fate of the evolved (PoS) Ethereum mainnet chain.
In Vitalik escalates ETH 2.0 merge as miners plan a 51% attack
It involves something called the staking deposit contract: https://ethereum.org/en/eth2/staking/ https://launchpad.ethereum.org/overview/ Picking any active validator on the Beacon Chain, we can see that there is an Eth1 deposit and a corresponding Eth2 deposit: https://beaconcha.in/validator/91676#deposits https://beaconscan.com/validator/91676#deposits If you're interested in the technical details, see: https://github.com/ethereum/eth2.0-specs/tree/dev/specs/phas...
In Vitalik escalates ETH 2.0 merge as miners plan a 51% attack

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.