Learn how to participate in Ethereum 2.0 pledge in this article?

Editor's Note: This article comes fromCrypto Valley Live (ID: cryptovalley)Editor's Note: This article comes from

Crypto Valley Live (ID: cryptovalley)

, Author: Gaurav Agrawal, translation: Li Hanbo, reproduced by Odaily with authorization.

I would like to share with you what I think is the process required to participate in Ethereum 2.0 staking, when you pledge 32 ETH.

I will start with the general basic process and then introduce the specific methods, and finally share some advanced concepts in security, which may not apply to every staker.

secondary title

1. Familiar with the process and tools of depositing and staking on one of the ETH2 testnets, such as the Medalla testnet (medalla.launchpad.ethereum.org) or the upcoming testnet. This reduces the risk of running into problems when it really comes down to stakes. If you can't eat hot tofu in a hurry, don't rush for success.

2. Make sure you get all the information you need from reputable sources, such as the official Ethereum blog (blog.ethereum.org), Ethereum launchpad (launchpad.ethereum.org), or from someone you highly trust, and use the official and vetted tools like launchpad and the eth-deposit cli tool to generate your public/private key pair.

3. If you don't understand something, don't be afraid to ask. Ethereum has a great supportive community. You will definitely get help on the r/eth pledger or eth pledger Discord server. But don't forget: don't share any secrets and always be on the lookout for scammers or fakes.

secondary title

Step 2: Key Generation

Now that we've talked about general preparation. So let's look at the best practices for generating key pairs.

4. I recommend that you generate your staking keypair on a machine running a live (linux) distro / non-persistent system (such as Ubuntu or Tails), and during the generation process, make sure you are using a non-persistent OS or hardware is On, your machine is completely offline and disconnected.

5. Use official tools for key generation, such as outlined on Ethereum Lanchpad. If you use the binaries, check that the checksum matches the one in the release notes. Use sha256sum NameOfBinary on linux to see if they match. If your technology is complex, you can clone the repo and compile/build from source.

6. Either write down the passphrase/mnemonic, or store it encrypted, eg on a fingerprint drive. Make sure no third party can know about it. Make sure the camera is offline/blocked and the microphone is off.

7. If you have a key for a hardware wallet, you can also use the same key. This way you only have to keep this one safe. Store this copy in a safe place.

9. Never enter keys in fields that have autocorrect. Do not print the key, as your printer may have permanent storage. Try regenerating your deposit file and keystore file from the key you wrote down. For example, if you use the official eth-deposit-cli tool, use the command existing-mnemonic. See if the generated file is consistent with the original. The timestamps may be different, so check the public key matches in the keystore file. This ensures that if the signing key is lost after depositing, it can be regenerated later and the corresponding withdrawal key will be generated.

10. Save the deposit file and signature key/keystore file on a clean fingerprint drive. If you used the official eth2-deposit cli tool, the keystore is encrypted with the password you chose during generation. Make sure to remember it. Put the deposit file and the keystore on different USB sticks. This way the keystores only need to be connected to the actual staking machine to transfer the signing key later.

11. Securely destroy any extra copies of keys you may have created that are no longer needed.

secondary title

Step 3 - Deposit Process"12. Let's start with some prep work so you don't get overwhelmed by small details. Remember, deposits happen on public blockchains. So all transactions are traceable. If you don't want everyone to know how many and which validators you're running, make sure not to deposit from an address that can (easily) be linked to your identity."the address of.

This may include not depositing from addresses associated with ens names or addresses associated with addresses you have used in the past. You might want to consider using a mixer or sending your funds from an exchange to a clean address. For example, you can use tornado.cash with the relayer option to send funds to

clean

the address of.

13. If you plan to deposit more than 1 verification node and inject your funds into different addresses in a group of 32 Ethereum, then you are willing to bear these transaction fees by default. Considering the different transaction fees at different times, you can stake at different times. However, because of these steps, staking can also become more complicated. Now that we have our keys securely generated and our funds ready, let's talk about the deposit process itself.

14. If you have a hardware wallet, send your deposit from there.

15. Use official tools such as the Ethereum deposit launchpad to make deposits.

17. Make sure your deposit address is correct. Please triple check the address you will be depositing against the address you found from an official and reputable source, see #2. The address of the deposit contract should start with 8 0s, then 219, and finally it should be 5fa. But don't take my word for it, check against addresses from other sources.

18. If you plan to deposit many validators, make sure to use a proper auditing tool such as ethdo. If you want to deposit in batches, say 10 today and 5 later, be careful not to accidentally deposit twice for the same validator.

19. Besides using deposit tools like beaconcha.in or beaconscan.com and tools like eth1 block explorer to monitor deposit status like launchpad.

secondary title

Last talk: ETH2 setup and deposit

Now that you have successfully staked, let's talk about staking itself.

20. Consider running a non-majority ETH1 node and a non-majority ETH2 relay node to promote healthy client diversity. In particular, running a non-majority ETH2 node also reduces the risk of simultaneous failures with the rest of the network, whereas in ETH2 risk inflictors are generally punished more strongly."21. Before genesis starts, get your entire setup, among other things, your ETH1 node, your relay node, and your validator client all set up in advance, just in case something goes wrong or You need to reset."22. When performing staking at home, consider whether you need to take precautions to hide your IP. Network analysis allows an attacker to identify which validators belong to which machine relay node/ip. With ip geolocation it is often easy to find even where you are staking. Use a vpn service or other means to hide your ip.

23. More advanced (for

master

): Consider sending signed SMS, linking validators to ip/machines via network analysis, via a lightweight ETH2 network client on a separate system. You'll probably want to use multiple lightweight web clients to send signed mail (in rotation), and/or put them on different vpns, taking turns using ips. This reduces the risk of the target being attacked.

24. When staking from home, take into account (especially common or costly) failure situations such as power or internet outages. If you're running many validators, consider setting up a failover internet connection, and consider installing a battery UPS. The latter not only helps you stay online during a power outage, and generally protects your hardware from power spikes, but also reduces the risk of your validator db being corrupted during a power outage.

25. Test the migration from one client implementation to another on the testnet, as an exercise.

26. Consider the backup procedure/procedure for validator db. A live sync backup system might save you headaches in case of a validator db outage.

27. Think of all the applause you can think of that could affect your staking, and make protocols for at least the most common failures and failure costly failures. This might include having redundant/spare hardware on hand, having a failover internet connection.

28. Think about how to ensure the security of the operating system. Set up a firewall with traffic and port rules set up appropriately. Minimize the number of ports exposed publicly. Regularly check for system/software updates. In particular, make sure you are updated on ETH2 related issues such as client updates, forks, etc.

29. When staking at home, keep your network hardware’s firmware updated. Only open the required ports.