prysm-pulse/validator
Nishant Das 7d88e1e15e Allow Client to Retrieve Multiple Validator Statuses (#2474)
* multiple validator statuses

* gazelle

* context

* fixing bugs

* remove old way of checking

* fix logging

* make activation queue more accurate

* fix rpc test

* add test

* fix remaining tests

* lint

* comment

* review comments
2019-05-03 12:13:34 -05:00
..
accounts Add Caching to Tree Hashing Algorithm (#1929) 2019-04-24 13:39:02 +08:00
client Allow Client to Retrieve Multiple Validator Statuses (#2474) 2019-05-03 12:13:34 -05:00
internal ValidatorStatus Estimating Activation RPC Server (#2469) 2019-05-02 14:14:25 -05:00
node Added flag to disable rewards/penatlty logging (#2319) 2019-04-27 11:56:11 +08:00
types Added flag to disable rewards/penatlty logging (#2319) 2019-04-27 11:56:11 +08:00
BUILD.bazel Interactive Validator Client Onboarding (#2362) 2019-04-23 21:29:06 -07:00
main.go Added flag to disable rewards/penatlty logging (#2319) 2019-04-27 11:56:11 +08:00
README.md ETH 2.0 Design Specs have been moved (#959) 2018-11-23 22:02:35 -10:00
usage.go Added flag to disable rewards/penatlty logging (#2319) 2019-04-27 11:56:11 +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.