mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-25 12:57:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
7aaefd123e
prysm-pulse/validator
History
Raul Jordan 7abc1feaf5
Update Ethdo Keystore Deps (#7537) 
* include old crypto code

* update gomod

* delete new util

* add versioning for determining derivation strategy

* add versioning

* tidy and gazelle viz

* fix tests

* fix broken

* workspace fix

* fix workspace

* revert

* fix test

* derived test fix
2020-10-15 15:33:10 -05:00
..
accounts/v2 Add show-private-keys flag to accounts-v2 list (#7487) 2020-10-15 16:08:52 +00:00
client Use new proposal protection format (#7518) 2020-10-15 19:35:31 +00:00
db Use new proposal protection format (#7518) 2020-10-15 19:35:31 +00:00
flags Add show-private-keys flag to accounts-v2 list (#7487) 2020-10-15 16:08:52 +00:00
keymanager/v2 Update Ethdo Keystore Deps (#7537) 2020-10-15 15:33:10 -05:00
node Use new proposal protection format (#7518) 2020-10-15 19:35:31 +00:00
rpc Update error usage patterns to go1.13+ (#7529) 2020-10-14 17:39:52 +00:00
slashing-protection Better naming for constructor funcs (#7316) 2020-09-23 08:59:49 +00:00
testing Various code inspection resolutions (#7438) 2020-10-12 08:11:05 +00:00
web Resolve Web UI Beta Testing Bugs (#7471) 2020-10-10 02:07:28 +00:00
BUILD.bazel Add terms of use acceptance requirement (#7527) 2020-10-15 02:05:30 +00:00
main.go Add terms of use acceptance requirement (#7527) 2020-10-15 02:05: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 Add terms of use acceptance requirement (#7527) 2020-10-15 02:05: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.