Use NetworkState in node rewards. - #1182
Conversation
|
There seems to be a regression related to |
Metrics collection should either not use the GetHeadStateForNode if it cares about network-wide aggregates, or should not care about network-wide aggregates. Personally, I think having network stats in grafana is a bit pointless, as better third-party trackers exist (Dune, steely's site). All it does is increase load on the node every time the state locker cache thingy refreshes. |
I'm in favor of removing global stats that are impacting the SN performance. Just make sure to adapt the Grafana dashboard so users understand these changes. |
Merging this branch changes the coverage (2 decrease, 1 increase)
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. |
A handful of improvements to the node rewards path: #1140
Your share of unskimmed Beacon Chain (CL) rewards is currently -8.005268 ETH.Highly scientific benchmark on two different hoodi nodes: