prysm-pulse/validator
2019-01-11 10:19:58 +08:00
..
attester Remove Use of Proto .GetX for Value Getters (#1235) 2019-01-04 21:58:19 -06:00
beacon Reformat Configs for Readability (#1256) 2019-01-05 20:36:05 -08:00
internal Modifying Block Proposals for Validator Clients (#1224) 2019-01-10 10:56:26 +08:00
node Better printing of version number when starting nodes (#1294) 2019-01-11 10:19:58 +08:00
proposer Modifying Block Proposals for Validator Clients (#1224) 2019-01-10 10:56:26 +08:00
rpcclient Health check endpoints for services (#1183) 2018-12-30 16:20:43 -05:00
txpool Health check endpoints for services (#1183) 2018-12-30 16:20:43 -05:00
types Config Updates to Latest Spec (#868) 2018-11-20 17:41:20 -08:00
utils Validator Assignment RPC Beacon Node Stream (#563) 2018-09-26 21:34:35 -05:00
BUILD.bazel Add simple version to binaries via golink (#1286) 2019-01-09 23:19:33 -05:00
main.go Add simple version to binaries via golink (#1286) 2019-01-09 23:19:33 -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.