Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slasher prevents proposal #7159

Closed
stefa2k opened this issue Sep 2, 2020 · 2 comments
Closed

Slasher prevents proposal #7159

stefa2k opened this issue Sep 2, 2020 · 2 comments
Assignees
Milestone

Comments

@stefa2k
Copy link

stefa2k commented Sep 2, 2020

🐞 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:

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`
  
@stefa2k
Copy link
Author

stefa2k commented Sep 4, 2020

same thing here: https://beaconcha.in/validator/2222#blocks with slot 187519

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.

@rauljordan
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants