prysm-pulse/validator
Raul Jordan 3b2c514c06
Empty Committee Check in Submit Attestation (#5672)
* empty committee check
* Merge refs/heads/master into validator-id-errs
2020-04-29 02:44:51 +00:00
..
accounts validator/accounts: don't ask for keystore path if specified (#5641) 2020-04-27 16:26:51 +00:00
client Empty Committee Check in Submit Attestation (#5672) 2020-04-29 02:44:51 +00:00
db Align code base to v0.11 (#5127) 2020-04-14 20:27:03 +00:00
flags Change prometheus port for different parts of Prysm (#5504) 2020-04-19 08:36:19 +00:00
internal No More EthereumAPIs Patch (#5570) 2020-04-22 03:56:06 +00:00
keymanager Update remote signer for 0.11 (#5602) 2020-04-28 09:27:04 -05:00
node Change prometheus port for different parts of Prysm (#5504) 2020-04-19 08:36:19 +00:00
BUILD.bazel Remove old cross compile starlark rules (#5329) 2020-04-07 03:01:20 +00:00
main.go Change prometheus port for different parts of Prysm (#5504) 2020-04-19 08:36:19 +00: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 Deprecate span map cache flag (#5551) 2020-04-22 15:53:09 +00:00
usage.go Change prometheus port for different parts of Prysm (#5504) 2020-04-19 08:36:19 +00: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.