mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2024-12-26 05:17:22 +00:00
d121b19145
* Hide beacon operation field if it's 0 * Rename NewSerivce to New * Revert "Hide beacon operation field if it's 0" This reverts commit 896fa11a0bb605212293d6fff02a8974c54710ab. * Fix NewServiceRegistry * Update slasher/detection/service.go Co-authored-by: Radosław Kapka <rkapka@wp.pl> Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com> |
||
---|---|---|
.. | ||
beaconclient | ||
cache | ||
db | ||
detection | ||
flags | ||
node | ||
rpc | ||
BUILD.bazel | ||
log.go | ||
main.go | ||
README.md | ||
usage_test.go | ||
usage.go |
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