prysm-pulse/validator
Ivan Martinez 8b9138a76a
Accounts V2: Log and UX cleanup (#6955)
* Clena up password entry for importing
* Merge branch 'master' of github.com:prysmaticlabs/prysm into accounts-v2-cleanup
* Fix password entry
* Clean
* Merge branch 'master' of github.com:prysmaticlabs/prysm into accounts-v2-cleanup
* Change color
* Merge branch 'master' of github.com:prysmaticlabs/prysm into accounts-v2-cleanup
* Fix
* Merge branch 'master' of github.com:prysmaticlabs/prysm into accounts-v2-cleanup
* Fix
* Merge branch 'master' of github.com:prysmaticlabs/prysm into accounts-v2-cleanup
* Cleanup
* Clean go.mod
* Fix
2020-08-10 22:35:30 +00:00
..
accounts Accounts V2: Log and UX cleanup (#6955) 2020-08-10 22:35:30 +00:00
client Proposer: log graffiti (#6954) 2020-08-10 19:17:59 +00:00
db Fix multiple anti-patterns from DeepSource analysis (#6951) 2020-08-10 16:16:45 +00:00
flags Refactor Wallet Password Handling, Preventing Wallet Corruption (#6933) 2020-08-10 18:54:40 +00:00
keymanager Accounts V2: Log and UX cleanup (#6955) 2020-08-10 22:35:30 +00:00
node Refactor Wallet Password Handling, Preventing Wallet Corruption (#6933) 2020-08-10 18:54:40 +00:00
slashing-protection Make external slasher protection fail on load if slasher is not reachable (#6704) 2020-07-27 20:06:49 +00:00
testing Make external slasher protection fail on load if slasher is not reachable (#6704) 2020-07-27 20:06:49 +00:00
BUILD.bazel Avoid automaxprocs default logger to printf (#6524) 2020-07-11 00:57:43 +00:00
main.go Accounts V2: Remove unused passwords-dir and deprecate flag (#6916) 2020-08-07 00:02:30 +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 Accounts V2: Remove unused passwords-dir and deprecate flag (#6916) 2020-08-07 00:02:30 +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.