prysm-pulse/slasher
Preston Van Loon 4beb352e6f
Move Slot and Epoch functions from helpers to core pkg (#9519)
* Move Slot and Epoch functions from helpers to core

* limited viz

* goimports

* fix fuzz build

* fix fuzz build

* fix

* fix

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2021-09-03 20:10:31 +00:00
..
beaconclient Move v1alpha1 into Prysm API namespace (#9245) 2021-07-21 21:34:07 +00:00
cache Feature lru cache wrapper 2 (#9511) 2021-09-02 18:36:54 +08:00
db Move Slot and Epoch functions from helpers to core pkg (#9519) 2021-09-03 20:10:31 +00:00
detection Move Slot and Epoch functions from helpers to core pkg (#9519) 2021-09-03 20:10:31 +00:00
node Bazel: minimal test build transitions (#9122) 2021-06-30 19:22:09 +00:00
rpc Move Slot and Epoch functions from helpers to core pkg (#9519) 2021-09-03 20:10:31 +00:00
BUILD.bazel Add Goland Standard "cmd" Pattern for Slasher Binaries (#8542) 2021-03-03 18:37:57 +00:00
README.md Reduce Usage of Eth2 Terminology in Prysm (#9104) 2021-06-26 19:00:33 +00:00

Slasher Implementation

This is the main project folder for a slasher implementation for Ethereum 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