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
6fd6e989ec
prysm-pulse/validator
History
Nishant Das 37bc1c67be
Adding Basic Private Key Management (#671) 
* adding flags

* adding modified key utils

* adding more funcs

* more changes

* more changes

* documentation

* changes to node

* gazelle

* fixing bazel build

* gazelle

* adding tests

* more tests

* addressing terence's feedback

* adding geth header

* test

* changes

* fixedd it

* fixed marshalling

* adding more to tests

* gazelle

* adding more tests

* lint

* add cov

* cov

* fix imports
2018-11-08 11:22:31 +08:00
..
attester switch ethereum 2.0 to ethereum serenity (#714) 2018-11-01 07:02:01 -04:00
beacon fixed error strings (#708) 2018-10-31 23:05:55 +01:00
internal Validator Client Use Assignment Stream to Determine Responsibility (#566) 2018-09-27 14:46:07 -07:00
node Adding Basic Private Key Management (#671) 2018-11-08 11:22:31 +08:00
params Miscellaneous Fixes for Demo (#694) 2018-10-23 11:07:43 -05:00
proposer switch ethereum 2.0 to ethereum serenity (#714) 2018-11-01 07:02:01 -04:00
rpcclient RPC methods for Validators to Get ShardID, Index and Slot (#526) 2018-09-17 22:36:09 -04:00
txpool Migrate dependencies on @com_github_ethereum_go_ethereum//event (#601) 2018-10-02 21:49:01 -04:00
types Adding Basic Private Key Management (#671) 2018-11-08 11:22:31 +08:00
utils Validator Assignment RPC Beacon Node Stream (#563) 2018-09-26 21:34:35 -05:00
BUILD.bazel Renamed Client to Validator (#428) 2018-08-22 12:15:21 -07:00
main.go Adding Basic Private Key Management (#671) 2018-11-08 11:22:31 +08:00
README.md switch ethereum 2.0 to ethereum serenity (#714) 2018-11-01 07:02:01 -04: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.