prysm-pulse/validator
terence tsao 3b65cb6d0b
Consistent BLS function inputs (#5969)
* Make function input consistent

* Change back

* Typo

* Fixed test

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2020-05-25 16:08:12 -05:00
..
accounts Merge validator databases (#5968) 2020-05-25 11:20:35 -05:00
client Merge validator databases (#5968) 2020-05-25 11:20:35 -05:00
db Merge validator databases (#5968) 2020-05-25 11:20:35 -05:00
flags Merge validator databases (#5968) 2020-05-25 11:20:35 -05:00
keymanager Consistent BLS function inputs (#5969) 2020-05-25 16:08:12 -05:00
node Merge validator databases (#5968) 2020-05-25 11:20:35 -05:00
slashing-protection External slashing protection (#5895) 2020-05-20 10:23:22 -05:00
BUILD.bazel Command to fetch validator statuses + MultipleValidatorStatus (#5784) 2020-05-19 05:13:37 +00:00
main.go Merge validator databases (#5968) 2020-05-25 11:20:35 -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 Deprecate span map cache flag (#5551) 2020-04-22 15:53:09 +00:00
usage.go Merge validator databases (#5968) 2020-05-25 11:20: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.