Deregister Remote Slashing Protection Until Further Notice

[rauljordan]

Slashing protection is one of the riskiest features to include in an Ethereum beacon chain implementation. Prysm today supports three methods

1. Local slashing protection database. This is enabled for every validator client, cannot be disabled, and is, in general, a quite safe way of protecting against double signing of data
2. Doppelganger detection. This is an optional feature that looks at some beacon chain information to determine if a validator key is performing its duties on chain. This can halt the process right away and is helpful for preventing getting slashed in case a user is running the same validator key but on a different machine. It is not perfect and redundant key setups should be avoided at all costs.
3. Remote slashing protection using a slasher. Slasher is a process that acts as the "police" of the network. It is a highly resource intensive process, and is not bug-free. The team is still working on improving slasher. However, trusting software that is still being drastically improved with something as risky as "slashing protection" is dangerous.

It has been brought to our attention that slasher currently returns incorrect data for its HighestAttestations endpoint, which is used by some stakers for slashing protection. We believe this is a serious risk and are now disabling the ability for validator clients to use remote slashing protection until we feel 100% confident in its safety for further notice.