mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-26 05:17:22 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
5b83dffbe4
prysm-pulse/slasher
History
Ivan Martinez 923d5fc903
Cleanup slasher codebase (#4698) 
* First wave of changes
* More changes
* More renames, changes
* Fix errors
* Merge branch 'master' of https://github.com/prysmaticlabs/Prysm into cleanup-slasher
* Fix errors, more cleaning
* Merge branch 'master' of https://github.com/prysmaticlabs/Prysm into cleanup-slasher
* Merge branch 'master' into cleanup-slasher
* fix err
* Merge branch 'cleanup-slasher' of https://github.com/0xKiwi/Prysm into cleanup-slasher
* Fix strings
* More cleanup
* Merge branch 'master' of https://github.com/prysmaticlabs/Prysm into cleanup-slasher
* Fix interface
* Fix
* Merge branch 'master' into cleanup-slasher
* Merge branch 'master' into cleanup-slasher
* Merge branch 'master' into cleanup-slasher
* Address comments
* Merge branch 'master' of https://github.com/prysmaticlabs/Prysm into cleanup-slasher
* Merge branch 'cleanup-slasher' of https://github.com/0xKiwi/Prysm into cleanup-slasher
2020-02-04 18:48:51 +00:00
..
db Cleanup slasher codebase (#4698) 2020-02-04 18:48:51 +00:00
flags Slasher span cache (#4388) 2020-01-21 23:39:21 -06:00
rpc Cleanup slasher codebase (#4698) 2020-02-04 18:48:51 +00:00
service Cleanup slasher codebase (#4698) 2020-02-04 18:48:51 +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

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.