prysm-pulse/slasher
Nishant Das d5181496c4 Add Docker image for slasher (#4356)
* add docker image for slasher

* load docker rules

* change to c base image

* switch off pure builds
2019-12-26 10:53:27 -06:00
..
db Remove proto/sharding and move slashing to own dir (#4332) 2019-12-20 21:47:00 -06:00
flags Slasher Grpc client (#4230) 2019-12-13 07:31:37 +00:00
rpc Remove proto/sharding and move slashing to own dir (#4332) 2019-12-20 21:47:00 -06:00
service Remove proto/sharding and move slashing to own dir (#4332) 2019-12-20 21:47:00 -06:00
BUILD.bazel Add Docker image for slasher (#4356) 2019-12-26 10:53:27 -06:00
main.go Slasher Grpc client (#4230) 2019-12-13 07:31:37 +00:00
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 grpc server (#3786) 2019-10-31 11:26:55 +08:00

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.