prysm-pulse/validator
Raul Jordan d5b1f9f1f9
Implement Stream Duties Functionality (#5685)
* add test for stream duties

* rem gomock

* context cancelation test

* use interface for epoch ticker in duties

* fix build

* compute duties on first call

* pass tests for streams

* gaz

* ss stream duties

* ensure only stream across epoch-wide reorgs

* regen mock for validator

* Update beacon-chain/blockchain/head.go

* Update beacon-chain/rpc/validator/server.go

* update workspac

* pregenesis check

* tests pass

* build fix

* Revert "tests pass"

This reverts commit 9029d63ef38437b388a6982e81a94c85da769ed5.

* ethereumapis

* gaz

* Update beacon-chain/rpc/validator/assignments.go

* test for reorg

* fix up required tests

* fmt

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
Co-authored-by: Preston Van Loon <preston@prysmaticlabs.com>
2020-05-06 14:15:31 -05:00
..
accounts Remove flag requirement from accounts keys (#5757) 2020-05-06 01:55:25 -04:00
client libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
db libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
flags libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
internal Implement Stream Duties Functionality (#5685) 2020-05-06 14:15:31 -05:00
keymanager libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
node Add Chain Config File for Validator (#5751) 2020-05-05 22:19:27 +00:00
BUILD.bazel libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
main.go Remove flag requirement from accounts keys (#5757) 2020-05-06 01:55:25 -04: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 Add Chain Config File for Validator (#5751) 2020-05-05 22:19:27 +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.