prysm-pulse/validator
Nishant Das d597410d9b MultiLocking in Operations Service (#3470)
* add lock

* add cache

* modify lock retrieval
2019-09-15 13:51:37 -05:00
..
accounts Include Prysm Tool to Generate Unencrypted Keys (#3324) 2019-08-28 11:07:31 -05:00
client Update to spec v0.8.3 (#3355) 2019-09-08 12:41:52 -07:00
flags Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
internal MultiLocking in Operations Service (#3470) 2019-09-15 13:51:37 -05:00
node Support Starting Validator Binary from Unencrypted Keys JSON (#3308) 2019-08-26 16:07:09 -05:00
BUILD.bazel Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
interop.go Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
main.go Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
README.md ETH 2.0 Design Specs have been moved (#959) 2018-11-23 22:02:35 -10:00
usage_test.go Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
usage.go Cold start for interop (#3437) 2019-09-11 13:38:35 -05: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.