mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-25 04:47:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
ce725ceec3
prysm-pulse/slasher
History
terence tsao ce725ceec3
Move state pkg to stateV0 pkg (#8620) 
* Move state pkg to stateV0 pkg

* Build.bazel

* Remove unused RootsArrayHashTreeRoot

* Revert "Remove unused RootsArrayHashTreeRoot"

This reverts commit bf0bda30d1a8eb7a071f6e3ce9ee85041b45aca6.

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2021-03-17 19:49:49 +00:00
..
beaconclient Use validatorIndex instead of validatorID (#8498) 2021-02-22 19:40:58 -06: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 Update rules_go and fix proto conflicts (#8596) 2021-03-11 18:03:19 -06:00
node Add Goland Standard "cmd" Pattern for Slasher Binaries (#8542) 2021-03-03 18:37:57 +00:00
rpc Move state pkg to stateV0 pkg (#8620) 2021-03-17 19:49:49 +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

README.md

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