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
07e7e030d9
prysm-pulse/validator
History
Raul Jordan a81c863ddb
Rename Accounts-V2 to Accounts (#7545) 
* rename accounts v2

* rename keymanager and fix imports

* rename accounts-v2 instances

* imports

* build

* build fix

* deepsource

* fix up broken aliases

* imports

* gaz

* Update validator/accounts/accounts_import_test.go

Co-authored-by: Ivan Martinez <ivanthegreatdev@gmail.com>

* fmt

Co-authored-by: Ivan Martinez <ivanthegreatdev@gmail.com>
2020-10-15 22:31:52 +00:00
..
accounts Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31:52 +00:00
client Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31:52 +00:00
db Use new proposal protection format (#7518) 2020-10-15 19:35:31 +00:00
flags Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31:52 +00:00
keymanager Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31:52 +00:00
node Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31:52 +00:00
rpc Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31: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 Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31:52 +00:00
main.go Rename Accounts-V2 to Accounts (#7545) 2020-10-15 22:31:52 +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.