prysm-pulse/validator
tzapu 0704ba685a
Return statuses on duties (#5069)
* try to return somethign for everything
* default to unknown
* debug
* moar debug
* move else to outer check
* working
* reorder imports
* cleanup
* fix TestGetDuties_NextEpoch_CantFindValidatorIdx
* Merge branch 'master' into return-statuses-on-duties
* Update validator/client/validator.go
* Merge branch 'master' into return-statuses-on-duties
* Merge branch 'master' into return-statuses-on-duties
2020-03-12 19:07:37 +00:00
..
accounts Warn rather than fail on incorrect keystore password (#5024) 2020-03-06 23:05:48 -06:00
client Return statuses on duties (#5069) 2020-03-12 19:07:37 +00:00
db Slasher proto and function renames (#4797) 2020-02-10 05:57:20 +00:00
flags Add a configurable flag for gRPC retries (#4926) 2020-02-24 18:00:22 +00:00
internal fuzz core/blocks package (#4907) 2020-03-03 19:02:14 +05:30
keymanager Use BeaconBlockHeader in place of BeaconBlock (#5049) 2020-03-09 21:08:30 +08:00
node Add Config Change for Validator (#5038) 2020-03-08 06:45:36 +00:00
BUILD.bazel Use correct image name for validator debug image (#4963) 2020-02-28 01:22:32 +00:00
main.go Add a configurable flag for gRPC retries (#4926) 2020-02-24 18:00:22 +00: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 Add a configurable flag for gRPC retries (#4926) 2020-02-24 18:00:22 +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.