This section provides instructions to run slasher to identify and report slashable offenses on eth2 . If slasher detects a slashable offense, proof is sent to the beacon-chain node for inclusion in a block. Validators earn a small whistleblower reward for including this proof into a block.
Slasher Can Be a Resource Hog
Slasher can be a huge resource hog during times of no chain finality, which can manifest as massive RAM usage. Please make sure you understand the risks of this, especially if you want high uptime for your beacon nodes. Slasher places significant stress on beacon nodes when the chain has no finality, and might be the reason why your validators are underperforming if your beacon node is under this much stress.
NOTICE: Running slasher is optional, but helps secure the chain and may result in additional earnings.
- Double voting
- occurs when a validator signs two different beacon blocks in the same epoch
- Surround votes
- occurs when a validator signs two conflicting attestations
Block Proposer slashings
- occurs when a proposer broadcasts more than one block for the same slot
Get Prysm and start beacon-chain
NOTICE: If beacon-chain is already running, skip to step 2
- To begin, follow the instructions for GNU\Linux, macOS, ARM64, or Windows to fetch and install Prysm. The beacon-chain process should be running and fully synced before proceeding.
- Depending on your platform, issue the appropriate command alongside any startup parameters from the examples below to start slasher.
Running slasher with prysm.bat on Windows
Running slasher with prysm.sh on GNU\Linux, macOS, and ARM64
Running slasher with Docker on GNU\Linux, and macOS
Running slasher with Docker on Windows
Running slasher with Bazel on GNU\Linux, macOS, and ARM64
- Slasher will spin up and immediately begin communicating with the beacon-chain process.
Congratulations, you are now ready to identify and report slashable attestations and block proposals
Still have questions? Stop by our Discord for further assistance!