prysm-pulse/validator
Preston Van Loon 2b3cb50461 Fix bug where proposer didn't also attest (#2073)
* fix bug, thanks @djrtwo

* remove unnecessary variable

* fix lint

* danny cfg
2019-03-26 00:14:03 -05:00
..
accounts Test Syncing with Another Fully Synced Service (#1594) 2019-02-23 11:36:20 +05:30
client Fix bug where proposer didn't also attest (#2073) 2019-03-26 00:14:03 -05:00
internal Validator: performing for multiple keys - update rpc proto (#2040) 2019-03-23 19:46:25 -05:00
node Create feature config for selective testing (#1997) 2019-03-20 22:57:25 -04:00
types Improve Validator Logging and Default Flags (#2013) 2019-03-18 09:45:28 -06:00
BUILD.bazel Create feature config for selective testing (#1997) 2019-03-20 22:57:25 -04:00
main.go Create feature config for selective testing (#1997) 2019-03-20 22:57:25 -04:00
README.md ETH 2.0 Design Specs have been moved (#959) 2018-11-23 22:02:35 -10:00
usage.go Create feature config for selective testing (#1997) 2019-03-20 22:57:25 -04: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.