prysm-pulse/slasher
Radosław Kapka 389bad7d24
Extract node configuration to separate file (#8744)
* Extract node configuration to separate file

* rename WarnIfNotSupported

* rename configuration to config

Co-authored-by: Preston Van Loon <preston@prysmaticlabs.com>
Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2021-04-13 07:04:34 +00:00
..
beaconclient Embed Config Pattern For Slasher, Slashing Protection (#8637) 2021-03-21 17:53:17 +00:00
cache Use validatorIndex instead of validatorID (#8498) 2021-02-22 19:40:58 -06:00
db Add Goland Standard "cmd" Pattern for Slasher Binaries (#8542) 2021-03-03 18:37:57 +00:00
detection Embed Config Pattern For Slasher, Slashing Protection (#8637) 2021-03-21 17:53:17 +00:00
node Extract node configuration to separate file (#8744) 2021-04-13 07:04:34 +00:00
rpc Embed Config Pattern For Slasher, Slashing Protection (#8637) 2021-03-21 17:53:17 +00:00
BUILD.bazel Add Goland Standard "cmd" Pattern for Slasher Binaries (#8542) 2021-03-03 18:37:57 +00:00
README.md Fix Up READMEs for Mainnet (#7910) 2020-11-23 18:47:55 +00:00

Slasher Implementation

This is the main project folder for a slasher implementation for eth2 written in Go by Prysmatic Labs. A slasher listens for all broadcasted messages using a running beacon node in order to detect slashable attestations and block proposals. It uses the min-max-surround method by Protolambda.

The slasher requires a connection to a synced beacon node in order to listen for attestations and block proposals. To run the slasher, type:

bazel run //slasher -- \
    --datadir PATH/FOR/DB \
    --span-map-cache \
    --beacon-rpc-provider localhost:4000

The beacon node entered in beacon-rpc-provider will then receive slashings from the slasher client and send them to any requesting proposer to be put into a block. You can read more about configuration options for our slasher in our documentation portal