network: holesky
validators: 3.3k attached through web3signer
some of them appear to be invalid (i.e the same attester index doesnt appear in both logged attestations), but there are indeed valid detected double votes, such as validator 967119 for example.
noticed that to they have been detected after they were already slashed on the chain? beaconcha.in says the slashing for 967119 was included in slot 889285, but the below logs are at slot 889349? thats exactly 64 slots later.
anyways this caused all attached validators to be offline until restarted
Thanks for the report. I'm afraid that we even forgot that we have slasher and didn't run it for more than 2 years. We will look at it at some point, but for now it's best to not activate built-in slasher.
network: holesky validators: 3.3k attached through web3signer
some of them appear to be invalid (i.e the same attester index doesnt appear in both logged attestations), but there are indeed valid detected double votes, such as validator 967119 for example.
noticed that to they have been detected after they were already slashed on the chain? beaconcha.in says the slashing for 967119 was included in slot 889285, but the below logs are at slot 889349? thats exactly 64 slots later.
anyways this caused all attached validators to be offline until restarted