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
18f8578d73
prysm-pulse/validator
History
Raul Jordan 18f8578d73
Derived Keymanager Has No Need to Store Accounts to Disk (#6790) 
* tests pass
* Merge branch 'master' into derive-no-store
* Merge refs/heads/master into derive-no-store
* gaz
* Merge branch 'derive-no-store' of github.com:prysmaticlabs/prysm into derive-no-store
* Merge refs/heads/master into derive-no-store
2020-07-30 23:23:18 +00:00
..
accounts Derived Keymanager Has No Need to Store Accounts to Disk (#6790) 2020-07-30 23:23:18 +00:00
client Return INVALID validator status if the BLS signature is invalid (#6576) 2020-07-28 23:19:07 -05:00
db Applies assertion funcs to validator tests (#6694) 2020-07-23 01:13:52 +00:00
flags Accounts Revamp Fixes: "Overall" Wallet Improvements (#6736) 2020-07-28 20:20:13 -05:00
keymanager Derived Keymanager Has No Need to Store Accounts to Disk (#6790) 2020-07-30 23:23:18 +00:00
node Accounts v2 as default (#6784) 2020-07-30 21:00:02 +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 Revamp Fixes: "Overall" Wallet Improvements (#6736) 2020-07-28 20:20:13 -05: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 Revamp Fixes: "Overall" Wallet Improvements (#6736) 2020-07-28 20:20:13 -05: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.