mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-23 11:57:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
3b2c514c06
prysm-pulse/slasher
History
Shay Zluf 4da7701249
Add slasher config file flag (#5639) 
* Add slasher config file

* shorter line

* fix package dependencies

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2020-04-27 17:14:26 +03:00
..
beaconclient Align code base to v0.11 (#5127) 2020-04-14 20:27:03 +00:00
cache slasher retrieve and cache validator public key (#5220) 2020-04-02 06:08:23 +03:00
db Slasher min span remove lookback (#5591) 2020-04-23 19:27:06 +00:00
detection Slasher min span remove lookback (#5591) 2020-04-23 19:27:06 +00:00
flags Deprecate span map cache flag (#5551) 2020-04-22 15:53:09 +00:00
node Deprecate span map cache flag (#5551) 2020-04-22 15:53:09 +00:00
rpc proper error checking and type assertions (#5424) 2020-04-14 16:41:09 +00:00
BUILD.bazel Add slasher config file flag (#5639) 2020-04-27 17:14:26 +03:00
main.go Add slasher config file flag (#5639) 2020-04-27 17:14:26 +03: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

README.md

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.