mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2025-01-12 04:30:04 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
c45fe5cc1c
prysm-pulse/slasher
History
Marcin Górzyński 02966e64d8
Feature lru cache wrapper 2 (#9511) 
* Add Wrapper to LRU Cache to handle Invalid Parameters #9461

* Regenerate BUILD.bazel and simplify tests using lru.Cache

* Fix: fuzz_exports.go build error

* Fix: block_fuzz.go

* Revert lru.Cache interface

* Remove redundant err check in pending_attestations_queue_test.go

* Add tests for lru wrapper

* Use lru package in prysm/shared instead of lruwrpr

* Fix: goimports

* Fix: BUILD.bazel

Co-authored-by: Nishant Das <nishdas93@gmail.com>
2021-09-02 18:36:54 +08:00
..
beaconclient Move v1alpha1 into Prysm API namespace (#9245) 2021-07-21 21:34:07 +00:00
cache Feature lru cache wrapper 2 (#9511) 2021-09-02 18:36:54 +08:00
db Eliminate Proto V2 Namespace (#9297) 2021-07-28 21:23:44 +00:00
detection Eliminate Proto V2 Namespace (#9297) 2021-07-28 21:23:44 +00:00
node Bazel: minimal test build transitions (#9122) 2021-06-30 19:22:09 +00:00
rpc Eliminate Proto V2 Namespace (#9297) 2021-07-28 21:23:44 +00:00
BUILD.bazel Add Goland Standard "cmd" Pattern for Slasher Binaries (#8542) 2021-03-03 18:37:57 +00:00
README.md Reduce Usage of Eth2 Terminology in Prysm (#9104) 2021-06-26 19:00:33 +00:00

README.md

Slasher Implementation

This is the main project folder for a slasher implementation for Ethereum 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