prysm-pulse/validator
Preston Van Loon c30913266c
Remove paths to go-ethereum crypto in validator (#1635)
* remove a few references that tie the validator binary to the go-ethereum crypto library

* fixes

* remove unused vars

* gazelle

* nosec on this crypto library
2019-02-19 01:17:27 -05:00
..
accounts Print a better copy/paste version of the deposit data (#1629) 2019-02-18 15:06:55 -08:00
client Fetch the Correct Chain Head During AttestHead (#1596) 2019-02-18 23:49:56 -06:00
internal Pending Attestations RPC Server/Client Implementation (#1617) 2019-02-15 18:36:40 -06:00
node Provide Real Keystore to Validator Service for Public/Private Key Access at Runtime (#1570) 2019-02-13 17:49:06 -06:00
types Validator Secret Initialization (#1436) 2019-01-31 12:57:57 +01:00
BUILD.bazel Remove paths to go-ethereum crypto in validator (#1635) 2019-02-19 01:17:27 -05:00
main.go remove old keystore flag (#1610) 2019-02-15 17:50:25 -05:00
README.md ETH 2.0 Design Specs have been moved (#959) 2018-11-23 22:02:35 -10: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.