prysm-pulse/validator
Marius Kjærstad 635e20529a Updated why-combining-sharding-and-casper link in validator/README.md (#3810)
Updated why-combining-sharding-and-casper link in validator/README.md
2019-10-20 19:43:30 -07:00
..
accounts make the print the same number of characters (#3626) 2019-09-28 09:41:02 +08:00
client Tidy up logging (#3784) 2019-10-16 06:37:43 -07:00
flags Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
internal Batch Validator Performance Requests (#3520) 2019-09-18 11:47:14 -05:00
node Clean up feature flag namings (#3715) 2019-10-07 14:11:49 +09:00
BUILD.bazel Use demo config for accounts create (#3627) 2019-09-27 15:48:49 -07:00
main.go Clean up feature flag namings (#3715) 2019-10-07 14:11:49 +09: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 Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
usage.go Cold start for interop (#3437) 2019-09-11 13:38:35 -05: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.