mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-24 20:37:17 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
59575bcac9
prysm-pulse/validator
History
shayzluf 59575bcac9
fuzz core/blocks package (#4907) 
* fuzz core/blocks package

* gaz goimports

* fix test

* terence feedback

* terence feedback

* add error to domain. halfway through

* adding error to domain

* goimports

* added error handling to test

* error instead of continue

* terence and nishant feedback

* domain error handling

* domain error handling

* handle nil validator in ReadOnlyValidator creation

* goinmports

* [4]byte domain type

* [4]byte domain type

* [4]byte domain type fix tests

* fix tests

Co-authored-by: Raul Jordan <raul@prysmaticlabs.com>
Co-authored-by: terence tsao <terence@prysmaticlabs.com>
2020-03-03 19:02:14 +05:30
..
accounts Fix typos and inconsistencies (#4453) 2020-01-07 20:36:55 -06:00
client fuzz core/blocks package (#4907) 2020-03-03 19:02:14 +05:30
db Slasher proto and function renames (#4797) 2020-02-10 05:57:20 +00:00
flags Add a configurable flag for gRPC retries (#4926) 2020-02-24 18:00:22 +00:00
internal fuzz core/blocks package (#4907) 2020-03-03 19:02:14 +05:30
keymanager Add location option for wallet keymanager (#4788) 2020-02-06 23:03:33 -06:00
node Add a configurable flag for gRPC retries (#4926) 2020-02-24 18:00:22 +00:00
BUILD.bazel Use correct image name for validator debug image (#4963) 2020-02-28 01:22:32 +00:00
main.go Add a configurable flag for gRPC retries (#4926) 2020-02-24 18:00:22 +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 Add a configurable flag for gRPC retries (#4926) 2020-02-24 18:00:22 +00:00

README.md

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.