119
I see a lot of little friends are very interested in #ETH's POS pledge, and let's talk about this topic tonight. The first step is to understand what kind of pledge you want to choose. The first two types of pledges are not so different, they both need 32 ETHs as a stage of pledge. And joint pledge is similar to Lido or exchange, so it's not within the scope of discussion. At present, I use a separate pledge, run their own node, their own server, the advantage is that all can be controlled, the benefits are their own, and very transparent. It's like a mine runner you're building. It's all your own. However, there are also shortcomings, is once the status of the server is not monitored well, the process may hang up, will cause punishment (deduction) yellow light pole
And once the penalty is deducted, it will reduce the APY, which is about 4.1% for the week, but if it is punished, it will go down to 2%, just like this node. But if it's just this low, there's no reason to dig, so after #ETH merge, we can already get the reward, and see that I'm also punished, and if I get the reward, APY goes up to 9%.
If there is no penalty, a block can reach more than 12%. If the Gas is high, such as grabbing NFT or paying bills for high-profile projects, the revenue can soar to higher, so if you want to do your own node, you better understand the maintenance of the server. At least we need to know how to restart the process. And then there's Can't Be Lazy, and the little guy asks me if I can have my own computer at home, which is basically okay, so long as you're not afraid of being punished.
Because the network requirements for nodes to synchronize are relatively high, especially in domestic networks, I personally chose AWS, although the cost is slightly higher, in terms of total benefits, one verifier (32 ETHs) for a year and a half would essentially cover the cost of AWS (around $3,500), and a server configured like this would be fine running eight nodes.
The second kind of pledge is the service, and the first kind is similar essentially, but also needs 32 #ETH as the start-up, just like the server's custodian party to deal with the hardware problem, but the benefit first has to pay the custody fee, honestly, this kind of supplier is still quite few, and the charge is not cheap, the only benefit is saving time, does not need hardware knowledge. There has been a detailed Chinese introduction, but I am not running according to this set, I started running node when there is not yet so detailed a strategy, and it seems there is no very detailed steps, for new beginners, one step by one try it can be seen, you can first run in the test network, run through the main network. This is my scheme, which has the advantage that it's very detailed at every step. It has the drawback that English and Technical Hand look like God knows what they're doing, but it's really very detailed, just do it. And there's an advanced scheme, which is that after you've run and become a validator, you can improve the odds of getting out of blocks by MEV, which is six times, I'm observing. The program is not official with #ETH, but it has been audited so interested parties can see for themselves. That's all. What's not clear? Tweet me. I've been poking around for a year and a half now
