All right. Hi, everyone. My name is Katya Ryzantseva, and my project is peer So, I'm not going to dive into what S-peer does, it's been mentioned already, so it's scaling solution for data availability. And all of you know that Ethereum protocols built with according to the consensus and execution specs. But the metrics for different clients are different.
I mean, we don't have the unified metrics for the clients. It's challenging for core devs to compare the different clients and for the DevOps team it's challenging to monitor all the clients, there are a lot of them, and it's also difficult for research to get the unified data to synchronize the data. So the solution is one dashboard for all clients. And the unified metrics specs. So how it worked before?
We had different dashboards for every client, different graphs, so to compare different clients it was quite painful. What do we have now for peer DAS? We have a single dashboard with different clients. The metrics implemented for Grandin, for Lighthouse, for Teco, and Grandin, Lighthouse, TecoO and, uh, Grundy in lighthouse, tackle and prison a little bit. So, uh, for this dashboard you can apply filters.
Um, you can choose if it's a full note or super note. Um, you can choose one client, two clients, all clients, and you can also choose an instance and compare or monitor or wherever you need. Let's look at some examples. This blue client implemented some feature. This one is peer-dust and the field.
Automatic transcript — names and jargon may be misspelled.
