This article mainly includes the following aspects:
- Hardware requirements
- Select & install client
- Set up ETH1 node
- Use ETH2 launchpad
1. Hardware requirements
Based on Eth2’s decentralized design goals, it expects verifiers to use a variety of different infrastructures for setup (local deployment, cloud deployment, etc.).
Below are some hardware introductions, resource links, and some useful guides to help you prepare.
Hardware specifications:
– Operating system: 64-bit Linux, Mac OS X, Windows
– Processor: Intel Core i7-4770 or AMD FX-8310 (or higher)
– Memory: 8GB RAM
– Storage: 100GB free space SSD
– Network: Broadband Internet connection (10 Mbps)
– Power supply: Uninterruptible power supply (UPS)
Equivalent to Digital Ocean (cloud service provider), etc.:
* Standard Droplet
– Memory: 8GB RAM
– Storage: 160GB free space SSD
-Uptime: 99.99%
-Availability: 8 data centers
-$/HR: $0.060
-$/MO: $40
Equivalent hardware:
- ZOTAC ZBOX CI662 Nano Silent Passive-Cooled Mini PC 10th Gen Intel Core i7
- SanDisk Ultra 3D NAND 2TB Internal SSD
- Corsair Vengeance Performance SODIMM Memory 16GB (2x8GB)
Minimum requirements:
Operating system: 64-bit Linux, Mac OS X, Windows
Processor: Intel Core i5-760 or AMD FX-8110 (or higher)
Memory: 4GB RAM
Storage: 20GB free space SSD
Network: Broadband Internet connection (10 Mbps)
Power supply: Uninterruptible power supply (UPS)
Equivalent to Digital Ocean Equivalent:
*Standard Droplet
– Memory: 4GB RAM
– Storage: 80GB free space SSD
-Uptime: 99.99%
-Availability: 8 data centers
-$/HR: $0.030
-$/MO: $20
Equivalent hardware:
- ZOTAC ZBOX CI642 Nano Silent Passive-Cooled Mini PC 10th Gen Intel Core i5
- SanDisk Ultra 3D NAND 2TB Internal SSD
- Corsair Vengeance Performance SODIMM Memory 8GB
2. Select & install client
Eth2 will start with multiple clients, and the verifier can choose to use different implementations to run the verifier. Up to now, there are 4 ready clients for you to choose:
Client
- Prysm (Prysmatic Labs)
Prysm is a Go implementation of the Eth2.0 protocol, which focuses on usability, security and reliability. Prysm is written in Go and released under the GPL-3.0 license.
Description: https://docs.prylabs.network/docs/getting-started/
Github: https://github.com/prysmaticlabs/prysm/
- Lighthouse (Sigma Prime)
Lighthouse is a Rust implementation of the Eth2.0 client, which focuses on speed and security. Sigma Prime is the team behind it, an information security and software engineering company. Lighthouse is released under the Apache2.0 license.
Description: https://lighthouse-book.sigmaprime.io/
Github: https://github.com/sigp/lighthouse
- Teku (ConsenSys)
PegaSys Teku is a Java-based Ethereum client designed and constructed to meet institutional needs and security requirements. Teku is licensed under Apache 2 and written in Java (a mature and ubiquitous language).
Description: https://docs.teku.pegasys.tech/en/latest/HowTo/Get-Started/Build-From-Source/
Github: https://github.com/PegaSysEng/teku
- Nimbus (Status)
Nimbus is an Eth2.0 research project and client implementation. Its goal is to run well on embedded systems and personal mobile devices (early smart phones with resource-constrained hardware). Nimbus (Apache 2) is written in Nim, which is a language similar to Python syntax.
Description: https://nimbus.team/docs/
Github: https://github.com/status-im/nim-beacon-chain
3. Install Eth1 node
Running a validator on Eth2 requires you to run an Eth1 node, with the purpose of monitoring the validator storage of 32 ETH. There are multiple options for selecting Eth1 nodes. Below you can find the most commonly used tools for starting Eth1 nodes.
Self-hosted:
- OpenEthereum
- Geth
- Besu
- Nethermind
escrow:
4. Run Eth2 validator
Step 1: get ETH ready
If you are new to Ethereum, the first important step is to get fuel for participation. Eth2 requires 32 ETH per validator. This is real money! It should be noted that if you become a validator, it means that you have made a long-term commitment to ETH2.0, which may take several years. (Note from Blue Fox: Because the deposited ETH cannot be transferred or withdrawn temporarily, and locked for a long time) ETH can be obtained through some centralization or DEX (such as Uniswap).
Step 2: Enter the Eth2 launchpad interface
In the past few months, the Ethereum Foundation (EF), Codefi Activate, and Deep Work Studio have been committed to developing a startup interface that can make it easier for users to participate in pledges and become validators of ETH2.0.
The work product of this startup interface is the Eth2 launchpad, which is designed to safely guide users to generate Eth2 key pairs and deposit 32ETH into a formal storage contract.
The launchpad is designed for ordinary family verifier users. They are amateurs, have plans to run their own validators, and are willing to run commands on their computer terminal screens.
Step 2-a: due diligence
In the process of becoming a verifier, it is important to spend some time reading some content. The overview section can help you understand the risks involved in staking ETH.
Step 3: Generate your key pair and mnemonic
For each verifier node, you need to generate a verifier key pair and a mnemonic phrase to generate your withdrawal key.
In the first step, you need to select the number of validators to run and on which operating system you want to run them.
To generate your deposit key, the launchpad will provide you with two options.
You can find detailed instructions about the operating system here:
https://github.com/ethereum/eth2.0-deposit-cli/blob/master/README.md
The first is to use the binary executable file downloaded from the Eth2 Github code base, and then run the ./deposit command in the terminal window.
Please note, remember to verify the URL and make sure you are using the correct URL!
Another option is to build the deposit-CLI tool from the Python source code. You need to follow the instructions to ensure that all necessary development libraries and deposit-CLI tools are installed.
Once you install the deposit-CLI tool and run it in the terminal window, the system will prompt:
*Specify the number of validators you want to run
*The language you want to use to generate the mnemonic
*Specify the network (main network) where you want to run the validator
Please make sure you have set up the chain mainnet for the Mainnet testnet, otherwise the deposit will be invalid.
Now you will be asked to set your password. Once confirmed, a mnemonic phrase will be generated to ensure that you write it down safely and save it offline!
If you have successfully completed this step, you will see the following screen.
If you have questions about deposit-cli, you can visit the GitHub code repository:
https://github.com/ethereum/eth2.0-deposit-cli
Step 4: Upload your storage files
Almost done! The next step is to upload the deposti.json file you generated in the previous step.
It is located in the /eth2.0-deposit-cli/validator_keys directory and is titled deposit-data-[timestamp].json.
Step 5: connect your wallet
The next step is to connect your web3 wallet and click continue. Make sure to select “Mainnet” in your wallet settings.
Step 6: Confirm transaction summary & start storage.
After connecting and confirming your wallet address, you will enter the summary page, which displays the total amount of ETH required to send to the storage contract based on the number of validators you have selected to run.
Agree to the alert check and click “Confirm” to navigate to the last step: actual storage of ETH.
Click “Start Transaction” to deposit your ETH into the official Eth2 storage contract.
You will need to confirm 32 ETH per validator through the wallet.
Once your transaction is confirmed… it’s done! You have succeeded and you can call yourself a real pledger in the milestones of Web3!
(From https://bankless.substack.com/p/-guide-how-to-become-a-validator)
Risk warning: All articles of Blue Fox Note cannot be used as investment advice or recommendation. Investment is risky. Investment should consider personal risk tolerance. It is recommended to conduct in-depth inspection of the project and make your own investment decisions carefully.
