mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-24 12:27:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
be078d6a16
prysm-pulse/slasher
History
Victor Farazdagi be078d6a16
Update TestMain(): do not call os.Exit() explicitly (#8046) 
* update workspace

* update testmain
2020-12-04 16:10:07 +00:00
..
beaconclient Update TestMain(): do not call os.Exit() explicitly (#8046) 2020-12-04 16:10:07 +00:00
cache Slasher highest source target (#7604) 2020-10-26 14:15:42 +02:00
db Update TestMain(): do not call os.Exit() explicitly (#8046) 2020-12-04 16:10:07 +00:00
detection Update TestMain(): do not call os.Exit() explicitly (#8046) 2020-12-04 16:10:07 +00:00
flags Slasher highest source target (#7604) 2020-10-26 14:15:42 +02:00
node Update TestMain(): do not call os.Exit() explicitly (#8046) 2020-12-04 16:10:07 +00:00
rpc Update TestMain(): do not call os.Exit() explicitly (#8046) 2020-12-04 16:10:07 +00:00
BUILD.bazel Fix creation time of beacon-node, validator and slasher (#7886) 2020-11-21 21:37:03 +00:00
main.go Add Backup Webhooks to All Prysm Services With DBs (#8025) 2020-12-03 22:28:57 +00:00
README.md Fix Up READMEs for Mainnet (#7910) 2020-11-23 18:47:55 +00:00
usage_test.go Applies assertion funcs to slasher/* tests (#6998) 2020-08-18 12:41:25 +00:00
usage.go Add Backup Webhooks to All Prysm Services With DBs (#8025) 2020-12-03 22:28:57 +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