[Tracking] - Standard Slashing Protection Interchange Functionality

[rauljordan]

💎 Issue

Background

The objective of this issue is to define a clear path for Prysm to implement the eth2 client slashing protection interchange format defined by EIP-3076. The EIP now comes with conformity tests which we can ensure our client satisfies. We have written up a design document for this feature here.

v1.0.1 Schema and Foundations

• Define the standard slashing format struct in Prysm Implement Standard Slashing Protection JSON With Importing Logic #7675
• Implement the import functions for the standard slashing format Implement Standard Slashing Protection JSON With Importing Logic #7675
• Add missing protection features (genesis validator root) Verify GenesisValidatorRoot Matches the One in DB on Slashing Protection Import #7864 and Save GenesisValidatorsRoot from WaitForChainStart #7855
• Ensure we support optional signing roots in the interchange JSON import Allow Optional Signing Roots in Proposal History #7960
• Support lowest and highest signed proposals in our DB Add ValidatorDB Methods for Highest and Lowest Signed Proposals #7957

V1.1.0 Runtime Integration

Import and exporting

• Implement the export proposal history functions for the standard slashing format Implement Export Block Proposals #7964
• Implement the export attesting history functions for the standard slashing format Export Attesting History for Slashing Interchange Standard #8027
• Ensure slashing protection JSON cannot be imported into a running validator client (our boltdb lock might already enforce this)
• Ensure we ask users for their slashing interchange json file upon importing keys into Prysm Add EIP-3076 Interchange JSON CLI command to validator #7880
• Include a command to export the standalone interchange JSON for all validators in the DB Export Slashing Protection History Via CLI #8040
• Validate whether proposer public keys we are importing is slashable with respect to other entries in the JSON file and prevent importing those entries Validate Proposers Are Not Slashable With Regard to Data Within Slasher Interchange JSON #8031
• Validate whether attester public keys we are importing is slashable with respect to other entries in the JSON file and prevent importing those entries Filter Slashable Attester Public Keys in Slashing Interchange Import #8051
• Prevent running keys that were found to be slashable from the 2 previous bullet points

Integrating invariants at runtime

It’s possible for an interchange file to contain blocks and attestations that
are mutually slashable, i.e. the interchange file contains evidence that the
validator has already committed a slashable offence. It’s also possible for
an interchange to contain messages that are slashable with respect to ones already
in the database. Require implementations to import all validators that are not slashable,
and reject all that are slashable

• Support lowest and highest signed proposals in our DB Add ValidatorDB Methods for Highest and Lowest Signed Proposals #7957
• Add test to ensure slashing protection allows genesis attestations to go through Add test for local protection genesis attestation #7977
• Ensure lowest signed source / target epoch getters return a boolean indicating if they exist in our database Update LowestSignedTargetEpoch to include exists #8004
• Ensure lowest signed proposal getters return a boolean indicating if they exist in our database Change LowestSignedProposal to Also Return a Boolean for Slashing Protection #8020
• Support the invariant below:

Refuse to sign any block with slot <= min(b.slot for b in data.signed_blocks if b.pubkey == proposer_pubkey), except if it is a repeat signing as determined by the signing_root. #8067

• Support the invariant below Add the additional eip-3076 attestation checks #7966

Refuse to sign any attestation with source epoch less than the minimum source epoch present in that signer’s attestations (as seen in data.signed_attestations)

• Migrate attesting history with unattested epochs to FAR_FUTURE_EPOCH Implement Migration for Unattested Epochs in Attesting History Database #8121

Testing and docs

• Include the conformity test vectors and ensure Prysm passes the tests Add Slashing Interchange, EIP-3076, Spec Tests to Prysm #7858