mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2024-12-25 12:57:18 +00:00
aad1b93f70
* Move data saving to listener service * Map result data to attestations to prevent duplicate DB reads * Gaz * Fix tests * Revert "Fix tests" This reverts commit 499b205a88ad632e02238d65adc6698725195e53. * Revert "Move data saving to listener service" This reverts commit fd52938dbaccb0c374f9d2405f8a61f4d17f8709. * Gaz * Undo changes * Imports * Reorder parameters * Fix error log * Add test for mapReusltsToAtts * Fix errorf * Change to safer crypto Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com> |
||
---|---|---|
.. | ||
beaconclient | ||
cache | ||
db | ||
detection | ||
flags | ||
node | ||
rpc | ||
BUILD.bazel | ||
main.go | ||
README.md | ||
usage_test.go | ||
usage.go |
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.