0b35743d2c
* Merge branch 'master' of github.com:prysmaticlabs/prysm into update_validators # Conflicts: # slasher/flags/flags.go # slasher/main.go # slasher/service/data_update.go # slasher/service/service.go # slasher/service/service_test.go * proposal and attester store * day to status * comment change * one bucket * Merge branch 'master' of github.com:prysmaticlabs/prysm into attester_proposer_slashing_store # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit. added comments * comment * typo fix * raul review fix * raul review fix full * nishant feedback * test fix * fix tests and remove update gofmt goimports * remove blank line in imports * nishant fixes * comment and fir delete proposer slashings * avoid marshal twice * remove space * Update slasher/db/attester_slashings.go Co-Authored-By: terence tsao <terence@prysmaticlabs.com> * terence feedback Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com> Co-authored-by: terence tsao <terence@prysmaticlabs.com> |
||
|---|---|---|
| .. | ||
| db | ||
| flags | ||
| rpc | ||
| service | ||
| BUILD.bazel | ||
| main.go | ||
| README.md | ||
| usage_test.go | ||
| usage.go | ||
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:
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.