Slashing refers to penalties that are applied to Ethereum 2.0 validators that sign conflicting blocks or attestations.
Web3Signer provides slashing protection to prevent validators from signing blocks and attestations based on what it knows has already been signed. A slashing protection database records each block and attestation signed by a validator.
Slashing protection is enabled by default, and you are responsible for creating and maintaining
the required PostgreSQL database, or you can disable slashing protection by setting
Web3Signer only supports PostgreSQL for creating the slashing protection database.
Multiple Web3Signer instances can connect to the same slashing protection database. Database locking ensures that if Web3signer instances load the same keys, only one Web3signer instance actually signs.