mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-25 21:07:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
18f28e2840
prysm-pulse/validator
History
Ivan Martinez 10c0d5b569
Remove unused functions in validator DB (#6557) 
* Remove unused functions in validator DB
* Iface
* Merge branch 'master' into reomve-unused-val-db
* Merge branch 'master' into reomve-unused-val-db
* Merge refs/heads/master into reomve-unused-val-db
2020-07-11 17:23:30 +00:00
..
accounts Remote Keymanager: Proto Definitions and Basic Client Implementation (#6526) 2020-07-10 05:49:56 +00:00
client Remote Keymanager: Proto Definitions and Basic Client Implementation (#6526) 2020-07-10 05:49:56 +00:00
db Remove unused functions in validator DB (#6557) 2020-07-11 17:23:30 +00:00
flags Implement Accounts-v2 List: Direct Keymanager (#6510) 2020-07-08 19:21:54 +00:00
keymanager Remote Keymanager: Proto Definitions and Basic Client Implementation (#6526) 2020-07-10 05:49:56 +00:00
node Direct Keymanager: Proper Keystore.json Formatting (#6527) 2020-07-09 16:23:53 +00:00
slashing-protection Move slashing protection code to separate files for proposing and attesting (#6406) 2020-07-03 19:54:42 +00:00
testing Move slashing protection code to separate files for proposing and attesting (#6406) 2020-07-03 19:54:42 +00:00
BUILD.bazel Avoid automaxprocs default logger to printf (#6524) 2020-07-11 00:57:43 +00:00
main.go Avoid automaxprocs default logger to printf (#6524) 2020-07-11 00:57:43 +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 Refactor dependencies, make Prysm "go gettable" (#6053) 2020-05-31 14:44:34 +08:00
usage.go Integrate Accounts v2 Keymanager Into Validator Client (#6489) 2020-07-08 05:01:09 +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.