prysm-pulse/validator
2020-05-05 14:42:53 +08:00
..
accounts Log out public key with accounts create (#5723) 2020-05-04 15:00:35 +00:00
client Use the custom HTR in a few more places (#5743) 2020-05-05 14:42:53 +08:00
db Refactor db teardown to testing.TB.Cleanup (#5725) 2020-05-04 01:14:34 +00:00
flags Other Package Godocs for Prysm (#5681) 2020-04-29 21:32:39 +00:00
internal Use stateutil.BlockRoot everywhere (#5739) 2020-05-05 04:30:24 +00:00
keymanager Log out important directories for validator client (#5653) 2020-04-30 23:17:06 +00:00
node Log out important directories for validator client (#5653) 2020-04-30 23:17:06 +00:00
BUILD.bazel Remove old cross compile starlark rules (#5329) 2020-04-07 03:01:20 +00:00
main.go Other Package Godocs for Prysm (#5681) 2020-04-29 21:32:39 +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.