prysm-pulse/validator
terence tsao d26839c1f2 Add aggregator indices to logs (#4385)
* Add validator_log.go

* Use new logging scheme

* Go fmt

* Better name

* Tests

* Tests

* Add wg.done, moved logging before span end

* Add aggregator indices to submit attestation log

* Rename

* Fixed test

* Add proposer index

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2020-01-02 17:45:48 -06:00
..
accounts Minor fixes to create keys errors (#4330) 2019-12-19 19:44:06 +00:00
client Add aggregator indices to logs (#4385) 2020-01-02 17:45:48 -06:00
flags fix order (#4228) 2019-12-09 22:31:53 +08:00
internal Update ethereumapis (#4142) 2019-11-29 16:44:51 +00:00
node Graffiti flag (#4213) 2019-12-07 19:13:56 +00:00
BUILD.bazel Build docker images for non-root user (#4320) 2019-12-18 20:52:25 +00:00
main.go Minor fixes to create keys errors (#4330) 2019-12-19 19:44:06 +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 Cold start for interop (#3437) 2019-09-11 13:38:35 -05:00
usage.go Graffiti flag (#4213) 2019-12-07 19:13:56 +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.