-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Add page about energy use post-merge [Issue #3020] #4654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev
Previous commit
Copy edits to remove first-person language
- Loading branch information
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -22,11 +22,11 @@ At the time of writing, there are 140,592 validators from 16,405 unique addresse | |||||
|
|
||||||
|  | ||||||
|
|
||||||
| How much power does it take to run a beacon node (BN), 5.4 validator clients (VC), and an eth1 full-node? Using my personal setup as a base, it’s around 15 watt. Joe Clapis (a Rocket Pool dev) recently ran 10 VCs, a Nimbus BN, and a Geth full node off of a 10Ah USB battery bank for 10 hours, meaning that this setup averaged 5W. It is unlikely that the average staker is running such an optimised setup, so let’s call it 100W all in. | ||||||
| How much power does it take to run a beacon node (BN), 5.4 validator clients (VC), and an eth1 full-node? Using an average personal setup as a base, it’s around 15 watt. Joe Clapis (a Rocket Pool dev) recently ran 10 VCs, a Nimbus BN, and a Geth full node off of a 10Ah USB battery bank for 10 hours, meaning that this setup averaged 5W. It is unlikely that the average staker is running such an optimised setup, so let’s call it 100W all in. | ||||||
|
|
||||||
| Multiplying this with the 87k validators from before means that home-stakers consume ~1.64 megawatt. Estimating the power consumed by custodial stakers is a bit harder, they run tens of thousands of validator clients with redundancy and backups. | ||||||
|
|
||||||
| To make life easy, let’s also just assume that they use 100W per 5.5 validators. Based off of the staking infrustructure teams I have spoken to, this is a **gross** over-estimate. The real answer is something like 50x less (And if you are a custodial staking team consuming more than 5W/ validator hit me up, I’m sure I can help you out). | ||||||
| To make life easy, let’s also just assume that they use 100W per 5.5 validators. Based off of the staking infrustructure teams I have spoken to, this is a **gross** over-estimate. The real answer is something like 50x less. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
|
||||||
| In total, a Proof-of-Stake Ethereum therefore consumes something on the order of 2.62 megawatt. This is not on the scale of countries, provinces, or even cities, but that of a small town (around 2100 American homes). | ||||||
|
|
||||||
|
|
@@ -44,7 +44,7 @@ If energy consumption per-transaction is more your speed, that’s ~35Wh/tx (avg | |||||
|
|
||||||
| ## Looking Forward {looking-forward} | ||||||
|
|
||||||
| While Ethereum continues to use PoW for now, that won’t be the case for much longer. In the past few weeks, [we have seen](https://twitter.com/protolambda/status/1388093066993668098) the emergence of the first testnets for _The Merge_, the name given to the moment Ethereum switches to from PoW to PoS. Several teams of engineers are working overtime to ensure that _The Merge_ arrives as soon as possible, and without compromising on safety. | ||||||
| While Ethereum continues to use PoW for now, that won’t be the case for much longer. In the past few months, [we have seen](https://twitter.com/protolambda/status/1388093066993668098) the emergence of the first testnets for _The Merge_, the name given to the moment Ethereum switches to from PoW to PoS. Several teams of engineers are working overtime to ensure that _The Merge_ arrives as soon as possible, and without compromising on safety. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
|
||||||
| Scaling solutions (such as rollups and sharding) will help further decrease the energy consumed per-transaction by leveraging economies of scale. | ||||||
|
|
||||||
|
|
||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.