prysm-pulse/slasher
Raul Jordan 0326be86b5 Apply Patch Rules to Use EthereumAPIs Generated Protos in Prysm (#4112)
* starting on patch
* finish determining all required patches
* properly redefine the patch rules
* new patch
* rem double semicolon
* fix patch file
* Merge branch 'master' of github.com:prysmaticlabs/prysm into deprecate-eth-protos
* building the deps
* test target passes using ethereumapis
* compile gateway
* attempting to build everything
* e2e use ethereumapis
* more fixes for slasher
* other item
* getting closer to compiling slasher
* build slasher package
* Merge branch 'master' into deprecate-eth-protos
* Merge branch 'master' into deprecate-eth-protos
* fix benches
* lint gazelle
* Merge branch 'deprecate-eth-protos' of github.com:prysmaticlabs/prysm into deprecate-eth-protos
* proper gateway
* lint
* Merge branch 'master' into deprecate-eth-protos
* fix build
* Merge branch 'deprecate-eth-protos' of github.com:prysmaticlabs/prysm into deprecate-eth-protos
* use swag
* resolve
* ignore change
* include new patch changes
* fix test
* builds
* fix e2e
* gaz
2019-11-27 05:08:18 +00:00
..
db Apply Patch Rules to Use EthereumAPIs Generated Protos in Prysm (#4112) 2019-11-27 05:08:18 +00:00
flags slasher grpc server (#3786) 2019-10-31 11:26:55 +08:00
rpc Apply Patch Rules to Use EthereumAPIs Generated Protos in Prysm (#4112) 2019-11-27 05:08:18 +00:00
service Apply Patch Rules to Use EthereumAPIs Generated Protos in Prysm (#4112) 2019-11-27 05:08:18 +00:00
BUILD.bazel slasher grpc server (#3786) 2019-10-31 11:26:55 +08:00
main.go slasher grpc server (#3786) 2019-10-31 11:26:55 +08: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.