prysm-pulse/validator
Ivan Martinez e27ed8174b
Remove validator filename prefix from validator/client (#6387)
* Remove validator prefix from files
* Gaz
* Merge branch 'master' of github.com:prysmaticlabs/prysm into val-rename-files
2020-06-24 17:43:24 +00:00
..
accounts Fix validator creation path (#6271) 2020-06-15 12:27:45 -07:00
client Remove validator filename prefix from validator/client (#6387) 2020-06-24 17:43:24 +00:00
db Address best practices in validator client (#6375) 2020-06-24 09:53:01 +08:00
flags QSP-Docs All Documentation Improvements from Quantstamp Audit Report (#6367) 2020-06-23 21:11:20 +00:00
keymanager Force manual validator account creation (#6165) 2020-06-08 09:03:14 -05:00
node QSP-Docs All Documentation Improvements from Quantstamp Audit Report (#6367) 2020-06-23 21:11:20 +00:00
slashing-protection External slashing protection not requiring signature (#6252) 2020-06-23 16:46:48 +00:00
testing External slashing protection not requiring signature (#6252) 2020-06-23 16:46:48 +00:00
BUILD.bazel Stream Duties Client Implementation (#5867) 2020-06-18 13:30:05 -05:00
main.go Address best practices in validator client (#6375) 2020-06-24 09:53:01 +08: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 Move permanent globally needed flags to shared/cmd and makes them accessible (#6312) 2020-06-23 15:41:20 +00: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.