prysm-pulse/validator
terence tsao 2e56a59473
attestations in pool count metrics (#4930)
* Add metrics
* Use it
* Use it
* Expose getters
2020-02-23 22:30:52 +00:00
..
accounts Fix typos and inconsistencies (#4453) 2020-01-07 20:36:55 -06:00
client attestations in pool count metrics (#4930) 2020-02-23 22:30:52 +00:00
db Slasher proto and function renames (#4797) 2020-02-10 05:57:20 +00:00
flags add prometheus metrics for validator accounts (#4724) 2020-02-05 11:49:27 -06:00
internal Slasher data update from archive (#4563) 2020-01-29 07:14:51 +05:30
keymanager Add location option for wallet keymanager (#4788) 2020-02-06 23:03:33 -06:00
node add prometheus metrics for validator accounts (#4724) 2020-02-05 11:49:27 -06:00
BUILD.bazel Define debug images for Prysm beacon chain and validator binaries (#4893) 2020-02-17 14:13:34 -08:00
main.go Add command to display private keys from keystore (#4793) 2020-02-10 13:47:54 -06:00
README.md Updated why-combining-sharding-and-casper link in validator/README.md (#3810) 2019-10-20 19:43:30 -07:00
usage_test.go Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
usage.go add prometheus metrics for validator accounts (#4724) 2020-02-05 11:49:27 -06: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.