Ethereum Staking Made Easy: Complete Tutorial (Ubuntu / Erigon / Lighthouse / Grafana / Goerli)
Вставка
- Опубліковано 8 тра 2024
- A step-by-step guide on how to stake Ethereum completely on your own. You will learn:
- The hardware for staking Ethereum
- How to install an operating system on your hardware
- How to fund your validator with 32 ETH
- How to install and run execution and consensus clients
- How to make sure everything runs continuously, even after a restart
- How to monitor your validator and create helpful dashboards with all the essential stats
And, by doing all of the above, how to earn your Ethereum staking rewards
For easy reference, all the code, commands, URLs and steps are listed here: qn.social/stakingguide
00:00 Introduction
00:56 Hardware (Intel NUC)
01:35 Operating System (Ubuntu)
03:04 Preparing the OS
03:35 Ethereum Launchpad
04:48 Execution client (Erigon)
07:36 Generating JSON Web Token (JWT)
10:25 Create validator keys (Wagyu)
12:22 Consensus client (Lighthouse)
15:42 Funding the validator with 32 ETH
18:34 Monitoring (Prometheus)
20:32 Monitoring (Node Explorer)
21:28 Dashboards (Grafana)
24:24 It's live!
26:20 Tasks to do after the validator is live
To get a free RPC node to connect to Goerli or Ethereum mainnet, click the link below and sign up for a free account (details in the video) 👉 qn.social/3GdYVPi
---
QuickNode loves sharing its knowledge and tech with the community. Check out the following resources ♥:
Blog: qn.social/qblog
Web3 guides: qn.social/guides
RPC docs: qn.social/docs
Discord community: qn.social/discord
Follow us on our social channels to stay updated about everything [[web3]]:
Twitter: qn.social/twitter
Facebook: qn.social/facebook
Instagram: qn.social/instagram
Linkedin: qn.social/linkedin - Наука та технологія
Thank you! This helps.Command line is intimidating !
Thank you!!
I can't source the .profile file that you're talking about. Could you help explain how you find the .profile file? Thanks
so a how much different for main net B if i use a ledger nano s for the address does a ledger receive address always stay active
Hello, I hope you're still responding to comments. I'm curious about the power consumption of your NUC when it's running as a node. Have you measured how much power it uses in watts? From what I understand, it might use around 7-8W when idle, but this can increase to as much as 55W under full load. So, the actual consumption could vary between 7W and 55W. Could you share the typical power usage of your NUC in this scenario?
Hi, thanks for the video. If I want to stake more than 32 eth, do I need to set up a separate node?
Yes, same process for every increment of 32 eth. You theoretically could add 32 eth to your existing validator but that would not increase your rewards, it would just sit there, so it doesn't make sense.
You can run more than one validator on the same hardware, so for every 32 eth you want to use, just add another validator. The hardware will be just fine.
Very efficient, some comments on dappnode ?
Dappnode does look good. I tried installing it but it didn't work for me. Being an all-in-one tool, it was harder to pinpoint the problem and fix it, so I just went the DIY way, where I have more control over all the ingredients.
The problem with NUCs is that it's small and you have to do a lot of maintenance the CPU fan is like a little dust vacuum. It is easier with a computer a little bigger like an A4 paper format.
NUC is good because it's small and quite powerful. But if size is not a priority, you can go with something bigger (and probably a bit cheaper).
@@QuickNode I had a Bitcoin Lightning node in it, every 3 months I had to open it to clean, all electronics attract dust. My setup was Ubuntu in SSD and /home in HDD. I'm not saying it's not good, just the maintenance part was more difficult.
Mine is fine after a year+, but it's SSD only, no HDD. The larger the machine the easier it is to cool and maintain. I like the small size of NUC though.
FYI - externalcl flag is no longer available and throws an error.
Good catch, thanks. It's always good to check the latest documentation. The situation is constantly changing, so there could be some minor differences in the final implementation.
@@QuickNode my pleasure!