prysm-pulse/slasher
Ivan Martinez c614412885
Remove silent errors from slasher (#5722)
* Remove silent errors from slasher
* Merge refs/heads/master into slasher-silent-errors
* Merge refs/heads/master into slasher-silent-errors
* Merge refs/heads/master into slasher-silent-errors
2020-05-04 08:17:18 +00:00
..
beaconclient Refactor db teardown to testing.TB.Cleanup (#5725) 2020-05-04 01:14:34 +00:00
cache Other Package Godocs for Prysm (#5681) 2020-04-29 21:32:39 +00:00
db Refactor db teardown to testing.TB.Cleanup (#5725) 2020-05-04 01:14:34 +00:00
detection Remove silent errors from slasher (#5722) 2020-05-04 08:17:18 +00:00
flags Other Package Godocs for Prysm (#5681) 2020-04-29 21:32:39 +00:00
node Unify usage of context in slasher client (#5684) 2020-04-29 19:27:01 -04:00
rpc Refactor db teardown to testing.TB.Cleanup (#5725) 2020-05-04 01:14:34 +00:00
BUILD.bazel Add slasher config file flag (#5639) 2020-04-27 17:14:26 +03:00
main.go Unify usage of context in slasher client (#5684) 2020-04-29 19:27:01 -04:00
README.md Update README for Slasher (#5106) 2020-03-15 18:46:21 +00:00
usage_test.go Deprecate span map cache flag (#5551) 2020-04-22 15:53:09 +00:00
usage.go Add slasher config file flag (#5639) 2020-04-27 17:14:26 +03:00

Hash Slinging Slasher Server Implementation

This is the main project folder for a slasher server implementation for Ethereum Serenity in Golang 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.