![]() A crucial part of maintaining infrastructure is being able to see what’s going on. Running an Ethereum 2.0 validator is running infrastructure for a distributed system. In this section, I’m going to walk through how to read your validator node’s metrics. In the final installment of this series, I will discuss how to safely and (hopefully) successfully migrate a Teku node from one server to another. I provide an overview on how to access Teku metrics, set up Beaconcha.in notifications, and how to query the node. ![]() In this blog post I will be covering monitoring and financial analysis of your Eth2 validator. Now’s a good time to take a breath to take stock of what we’ve done so far. Despite the tremendous interest in staking, it’s actually been a pretty uneventful month and a half: There have been no major disruptions, only a few slashings and validator participation in the 98th percentile most of the time. Already, 2,515,170 ETH has been staked (about $2.9 billion at current market rates) with 61,561 unique validators, and another 16,687 waiting in queue. It’s been a month and a half since Ethereum 2.0 Beacon chain genesis kicked off. Our Eth2 Knowledge Base is helpful if you need more of a background on key terms, phases, and ConsenSys’ Eth2 products. ![]() If you are new to this series, be sure to check out Part 1: Getting Started, Part 2: Setting Up Your Client and Part 4: Safely Migrating Your Eth2 Node.Īlso, you all should be checking Ben Edgington’s Eth2.News newsletter f or essential updates, bug fixes, and news on the forthcoming roadmap. This is the third article in a four-part series on how to run your own Eth2 validator. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |