prysm-pulse/slasher
Ivan Martinez 6488ab4a26
Add fast function for comparing attestation data (#5834)
* Add function for comparing attestation datas

* Fix imports

* Apply beneficial spots

* Gaz
2020-05-12 16:55:17 -04:00
..
beaconclient Fix historical detection for the slasher (#5831) 2020-05-12 18:32:42 +00:00
cache libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
db libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
detection Add fast function for comparing attestation data (#5834) 2020-05-12 16:55:17 -04:00
flags libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
node libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
rpc Is slashable block rpc endpoint implementation (#5765) 2020-05-08 08:51:56 +03:00
BUILD.bazel libfuzz based tests (#5095) 2020-05-05 07:22:26 +00: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--disable-historical-detection flag to slasher (#5759) 2020-05-06 22:17:36 +00: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.