mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2025-01-13 21:48:19 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
6b40fa01ec
prysm-pulse/slasher
History
Ivan Martinez 6b40fa01ec
Add detection package for slashing detection functions (#4861) 
* Move detection to its own package

* Fix renames

* More fixes

* Revert "Fix renames"

This reverts commit 3200f89a1b81bbffffdbd1bdca0fad73e0e8bc17.

* Fix

* Fix renames again

* Fix another rename

* Fix comment

* unused

* add comment

* gazelle

* Add spans

* Unexport helper functions

Co-authored-by: Raul Jordan <raul@prysmaticlabs.com>
2020-02-14 10:46:55 -06: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
detection Add detection package for slashing detection functions (#4861) 2020-02-14 10:46:55 -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 detection package for slashing detection functions (#4861) 2020-02-14 10:46:55 -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.