prysm-pulse/slasher
Potuz 88083d1000
Add journald option for logger (#7463)
* Add journald option for logger

Fixes #7353

* fix docker images

* go mod tidy

Co-authored-by: Preston Van Loon <preston@prysmaticlabs.com>
2020-10-14 00:10:57 +00:00
..
beaconclient Better naming for constructor funcs (#7316) 2020-09-23 08:59:49 +00:00
cache Historical detection fix (#6455) 2020-07-07 05:57:40 +03:00
db Combines func params of the same type (#7500) 2020-10-12 15:43:19 +00:00
detection Combines func params of the same type (#7500) 2020-10-12 15:43:19 +00:00
flags Slasher improvements (#7061) 2020-08-20 10:31:16 +03:00
node Fix --clear-db on Windows (#7474) 2020-10-09 09:28:35 +00:00
rpc Fix reported anti patterns (#7501) 2020-10-12 16:12:00 +00:00
BUILD.bazel Add journald option for logger (#7463) 2020-10-14 00:10:57 +00:00
main.go Add journald option for logger (#7463) 2020-10-14 00:10:57 +00:00
README.md Update README for Slasher (#5106) 2020-03-15 18:46:21 +00:00
usage_test.go Applies assertion funcs to slasher/* tests (#6998) 2020-08-18 12:41:25 +00:00
usage.go Optional services flags (#7358) 2020-09-30 20:55:56 +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.