prysm-pulse/validator
Ivan Martinez bf548d1670
Fix validator creation path (#6271)
Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2020-06-15 12:27:45 -07:00
..
accounts Fix validator creation path (#6271) 2020-06-15 12:27:45 -07:00
client Fix pubkey used in validator metrics (#6246) 2020-06-14 08:28:26 +00:00
db go fmt (#6101) 2020-06-03 06:42:22 -07:00
flags Default BeaconRPCProvider for Validator Should Match Beacon Node's Host (#6268) 2020-06-15 16:52:15 +00:00
keymanager Force manual validator account creation (#6165) 2020-06-08 09:03:14 -05:00
node Add Host Flags for All Servers running in Prysm (#6202) 2020-06-10 16:04:32 +00:00
slashing-protection No sig slasher rpc (#6174) 2020-06-11 18:50:12 +00:00
BUILD.bazel Add dockerhub image endpoints (#6230) 2020-06-12 17:06:12 +00:00
main.go Fix validator creation path (#6271) 2020-06-15 12:27:45 -07: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 Refactor dependencies, make Prysm "go gettable" (#6053) 2020-05-31 14:44:34 +08:00
usage.go Add Host Flags for All Servers running in Prysm (#6202) 2020-06-10 16:04:32 +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.