prysm-pulse/validator
terence tsao a19f08f7b6 Attestation Using Head State instead of Latest State (#2156)
* headRoot is a better name

* yay merged with master

* fixed attester server returning incorrect attestation field values

* revert stupid mock changes

* fixed and updated all the tests

* uncomment

* head start should handle skip blocks

* Raul's feedback
2019-04-05 09:41:49 -05:00
..
accounts Fix bash scripts for initializing beacon-chain (#2080) 2019-04-02 15:45:40 -05:00
client Attestation Using Head State instead of Latest State (#2156) 2019-04-05 09:41:49 -05:00
internal Revert "Treat Post & Pre-ChainStart Validators Equally in Assignments Fetching (#2074)" (#2086) 2019-03-26 22:30:22 -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.