prysm-pulse/slasher
Raul Jordan a7325315a8
Include Beacon Client Package in Slasher (#4835)
* begin beacon client

* adding in the proper receivers

* include all parts of the beacon client

* all comments included

* visibility and package comment
2020-02-11 15:35:31 -06:00
..
beaconclient Include Beacon Client Package in Slasher (#4835) 2020-02-11 15:35:31 -06:00
cache Slasher committees cache (#4812) 2020-02-10 20:09:14 +00:00
db Slasher proto and function renames (#4797) 2020-02-10 05:57:20 +00:00
flags Slasher span cache (#4388) 2020-01-21 23:39:21 -06:00
rpc Slasher proto and function renames (#4797) 2020-02-10 05:57:20 +00:00
service Slasher committees cache (#4812) 2020-02-10 20:09:14 +00:00
BUILD.bazel Add Docker image for slasher (#4356) 2019-12-26 10:53:27 -06:00
main.go Slasher data update from archive (#4563) 2020-01-29 07:14:51 +05:30
README.md slasher grpc server (#3786) 2019-10-31 11:26:55 +08:00
usage_test.go slasher grpc server (#3786) 2019-10-31 11:26:55 +08:00
usage.go Slasher data update from archive (#4563) 2020-01-29 07:14:51 +05:30

Prysmatic Labs Hash Slinging Slasher Server Implementation

This is the main project folder for a slasher server implementation of Ethereum Serenity in Golang by Prysmatic Labs. A slasher listens to queries from a running beacon node in order to detect slashable attestations and block proposals. It is advised to run the slasher in a closed network and let only your beacon node connect to it while not exposing its endpoints to the public network as DOS attacks on the slasher are easy to accomplish as the lookup for certain can have serious overhead if spammed.

Before you begin, check out our main README and join our active chat room on Discord or Gitter below:

Discord Gitter

Also, read the latest sharding + casper design spec, this design spec serves as a source of truth for the beacon chain implementation we follow at prysmatic labs. Check out the FAQs. Refer this page on why we are combining sharding and casper together.