mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-28 14:17:17 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
214121b0ab
prysm-pulse/slasher
History
Raul Jordan b99779fe94
Implementing Slasher Node Runtime (#4856) 
* include slasher node
* slasher node runtime added
* added in register for beacon client
* streaming blocks fixed up
* all subs working
* gazelle
* handle errors
* Merge branch 'master' into slasher-node
* Update slasher/node/BUILD.bazel
* x up slasher test
* Merge refs/heads/master into slasher-node
* Merge refs/heads/master into slasher-node
* add in force clear into usage
* Merge refs/heads/master into slasher-node
* usage
* Merge refs/heads/master into slasher-node
* Fix streamblocks test
* Merge refs/heads/master into slasher-node
* Fix docker image compile
* Merge branch 'slasher-node' of https://github.com/prysmaticlabs/Prysm into slasher-node
2020-02-14 07:09:54 +00:00
..
beaconclient Implementing Slasher Node Runtime (#4856) 2020-02-14 07:09:54 +00:00
cache Slasher committees cache (#4812) 2020-02-10 20:09:14 +00:00
db Add spans to Slasher DB functions (#4855) 2020-02-13 13:51:30 -06:00
flags Slasher span cache (#4388) 2020-01-21 23:39:21 -06:00
node Implementing Slasher Node Runtime (#4856) 2020-02-14 07:09:54 +00:00
rpc Add spans to Slasher DB functions (#4855) 2020-02-13 13:51:30 -06:00
service Add spans to Slasher DB functions (#4855) 2020-02-13 13:51:30 -06:00
BUILD.bazel Implementing Slasher Node Runtime (#4856) 2020-02-14 07:09:54 +00:00
main.go Implementing Slasher Node Runtime (#4856) 2020-02-14 07:09:54 +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 Implementing Slasher Node Runtime (#4856) 2020-02-14 07:09:54 +00:00

README.md

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.