mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-24 12:27:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
6ed0539723
prysm-pulse/validator
History
Ivan Martinez 6ed0539723
Acconuts-V2: Allow importing from any valid keystore, regardless of name (#6992) 
* Allow importing from any file

* Fix log

* Add test

* Fix test
2020-08-13 14:45:56 -05:00
..
accounts Acconuts-V2: Allow importing from any valid keystore, regardless of name (#6992) 2020-08-13 14:45:56 -05:00
client Moves AssertLogsContains to assertions package (#6985) 2020-08-13 16:22:25 +00:00
db Fix multiple anti-patterns from DeepSource analysis (#6951) 2020-08-10 16:16:45 +00:00
flags Implement Accounts-V2 Backup for Direct Keymanager (#6936) 2020-08-11 23:15:06 +00:00
keymanager Moves AssertLogsContains to assertions package (#6985) 2020-08-13 16:22:25 +00:00
node ListBalances for validator RPC (#6975) 2020-08-12 18:33:15 -05:00
rpc ListStatuses for validator RPC (#6987) 2020-08-13 15:52:56 +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

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.