Closed xuyenvuong closed 4 years ago
Should be addressed by #6879
This applies to beacon node and validator client as well. We also just observed this again in latest master. This may have been to reason why validators are proposing attestations and beacon blocks in the future
Has since been resolved https://docs.google.com/document/d/11RmitNRui10LcLCyoXY6B1INCZZKq30gEU6BEg3EWfk/edit#
Thanks.
Sorry if this is the incorrect place for this comment. But shouldn't the roughtime system be taking the median and not the average?
The same suggestion was made here https://github.com/cloudflare/roughtime/issues/22
Hey @shawnz ,
We do not currently use roughtime anymore, it has been removed in this PR #7299 . As far as I am aware roughtime still takes the average of all responses rather than the median, but given the roughtime spec is still in progress and undergoing standardization this may change in the future.
🐞 Bug Report
Description
Slasher was up and running on Medalla and encountered the below error. I have pinged cc: @nisdas @prestonvanloon ### Has this worked before in a previous version? Yes, the previous version in which this bug was not present was: alpha.16 ## 🔬 Minimal Reproduction🔥 Error
🌍 Your Environment
Operating System:
What version of Prysm are you running? (Which release)
Anything else relevant (validator index / public key)?