You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like slasher prevents proposal of all validators, not every time. Validator 2073 skipped a proposal because slasher prevented the proposal. https://beaconscan.com/slot/183839
Has this worked before in a previous version?
Yes
🔬 Minimal Reproduction
🔥 Error
Validator A:
time="2020-08-30 01:47:56" level=error msg="Failed post block signing validations" error="made a double proposal, considered slashable by remote slashing protection" prefix=validator pubKey=0x94e2aa11465b slot=183839
Validator B:
time="2020-08-30 01:47:56" level=error msg="Failed post block signing validations" error="made a double proposal, considered slashable by remote slashing protection" prefix=validator pubKey=0x94e2aa11465b slot=183839
Validator C:
time="2020-08-30 01:47:56" level=error msg="Failed post block signing validations" error="made a double proposal, considered slashable by remote slashing protection" prefix=validator pubKey=0x94e2aa11465b slot=183839
🌍 Your Environment
Operating System:
Ubuntu 20.04
What version of Prysm are you running? (Which release)
https://github.com/stefa2k/prysm-docker-compose with https://github.com/stefa2k/ansible-prysm/blob/master/eth2node-ha.yaml docker tag `:HEAD-78a25f`
The text was updated successfully, but these errors were encountered:
And external slashing protection didn't work with https://beaconcha.in/validator/2222 there is only one Failed block safety check of proposal (on 3 nodes) expected were 2 Failed block safety check.
There were only two time="2020-09-02 13:12:22" level=info msg="Received block via RPC" prefix=rpc proposer_index=2222 slot=208861 expected were 3. So one validator didn't submit their block to the external slashing protection and therefore didn't get blocked.
We have not been able to isolate this to slasher, and I believe @shayzluf has worked on this and has not found a correlation. Is it comes up and we have clear data about it, we can take further action
🐞 Bug Report
Description
Seems like slasher prevents proposal of all validators, not every time. Validator 2073 skipped a proposal because slasher prevented the proposal. https://beaconscan.com/slot/183839
Has this worked before in a previous version?
Yes
🔬 Minimal Reproduction
🔥 Error
Validator A:
Validator B:
Validator C:
🌍 Your Environment
Operating System:
What version of Prysm are you running? (Which release)
The text was updated successfully, but these errors were encountered: