prysm-pulse/validator
terence tsao 6e514b96fd
Remove unused code (#6065)
* Ran code cleanup from goland

* Typo

* Remove unused code

* Gazelle

* Delete comments
2020-05-31 15:47:15 -07:00
..
accounts Refactor dependencies, make Prysm "go gettable" (#6053) 2020-05-31 14:44:34 +08:00
client Merge validators enhancements (#6027) 2020-05-29 15:57:10 +00:00
db Remove unused code (#6065) 2020-05-31 15:47:15 -07:00
flags Remove unused code (#6065) 2020-05-31 15:47:15 -07:00
keymanager Remove unused code (#6065) 2020-05-31 15:47:15 -07:00
node Refactor dependencies, make Prysm "go gettable" (#6053) 2020-05-31 14:44:34 +08:00
slashing-protection External slashing protection (#5895) 2020-05-20 10:23:22 -05:00
BUILD.bazel Refactor dependencies, make Prysm "go gettable" (#6053) 2020-05-31 14:44:34 +08:00
main.go Ran code cleanup from goland (#6064) 2020-05-31 15:08:36 -05:00
README.md Updated why-combining-sharding-and-casper link in validator/README.md (#3810) 2019-10-20 19:43:30 -07:00
usage_test.go Refactor dependencies, make Prysm "go gettable" (#6053) 2020-05-31 14:44:34 +08:00
usage.go Refactor dependencies, make Prysm "go gettable" (#6053) 2020-05-31 14:44:34 +08:00

Prysmatic Labs Validator Client Implementation

This is the main project folder for a validator client implementation of Ethereum Serenity in Golang by Prysmatic Labs. A validator client attaches to a running beacon node in order to perform proposer/attester responsibilities and manage the lifecycle of a particular shard upon being assigned to one.

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.