mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-22 03:30:35 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
8cfbf0309d
prysm-pulse/validator
History
terence tsao 1b5b8a57e0 Remove unused proto schemas (#3005) 
* Update io_kubernetes_build commit hash to 1246899

* Update dependency build_bazel_rules_nodejs to v0.33.1

* Update dependency com_github_hashicorp_golang_lru to v0.5.1

* Update libp2p

* Update io_bazel_rules_k8s commit hash to e68d5d7

* Starting to remove old protos

* Bazel build proto passes

* Fixing pb version

* Cleaned up core package

* Fixing tests

* 6 tests failing

* Update proto bugs

* Fixed incorrect validator ordering proto

* Sync with master

* Update go-ssz commit

* Removed bad copies from v1alpha1 folder

* add json spec json to pb handler

* add nested proto example

* proto/testing test works

* fix refactoring build failures

* use merged ssz

* push latest changes

* used forked json encoding

* used forked json encoding

* fix warning

* fix build issues

* fix test and lint

* fix build

* lint
2019-07-22 10:03:57 -04:00
..
accounts Remove unused feature flags (#3002) 2019-07-19 21:27:35 -04:00
client Remove unused proto schemas (#3005) 2019-07-22 10:03:57 -04:00
internal Remove unused proto schemas (#3005) 2019-07-22 10:03:57 -04:00
node added forgotten CertFlag flag processing (#2988) 2019-07-21 17:12:31 -04:00
types Added flag to disable rewards/penatlty logging (#2319) 2019-04-27 11:56:11 +08:00
BUILD.bazel Add rule to push docker images (#3006) 2019-07-20 20:40:03 -04:00
main.go added forgotten CertFlag flag processing (#2988) 2019-07-21 17:12:31 -04:00
README.md ETH 2.0 Design Specs have been moved (#959) 2018-11-23 22:02:35 -10:00
usage.go added forgotten CertFlag flag processing (#2988) 2019-07-21 17:12:31 -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.