search

ssvlabs / ssv-spec

GNU General Public License v3.0
25 stars 21 forks source link

We do slashing checks on sync committees #437

Open GalRogozinski opened 1 week ago

GalRogozinski commented 1 week ago

As part of committee consensus we perform attestation slashing checks on combined attestation/sync-committee data.

Meaning that slashable attestation data will hinder sync committee duty.

Since slashable data is rare and this should optimistically be resolved on the next QBFT round, it isn't this bad.

_Originally posted by @GalRogozinski in https://github.com/ssvlabs/ssv-spec/pull/421#discussion_r1656562403_

GalRogozinski commented 3 days ago

This needs to be discussed

GalRogozinski commented 3 days ago

So we have a max of 512 sync committee participants. As the network grows this number will become more and more negligible.

So perhaps it makes sense to separate runners for attestations and sync committees so we have a clean protocol that won't run into rare issues.

On the other hand, we can have an optimization instead that all non-slashable duties will use the same consensus