Skip to content
You are reading Web3Signer development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.

Slashing protection

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 --slashing-protection-db-enabled to false.

Note

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.

Questions or feedback? You can discuss issues and obtain free support on Web3Signer Discord channel.
For paid professional support by Consensys, contact us at quorum@consensys.net