mirror of https://github.com/OffchainLabs/prysm.git synced 2026-05-02 03:02:54 -04:00

Files

Ivan Martinez d8c57541e4 Validator client cleanup (#5389 )

* Validator client status optimizations
* Reorder WaitForSync
* Change log to switch case
* Show activation epoch
* Change sync timing to half slot, inaccurate previously
* Merge branch 'master' into validator-imporve

2020-04-12 02:05:23 +00:00

accounts

Warn rather than fail on incorrect keystore password (#5024 )

2020-03-06 23:05:48 -06:00

client

Validator client cleanup (#5389 )

2020-04-12 02:05:23 +00:00

Replace boltdb imports with bbolt import (#5193 )

2020-03-24 20:00:54 +00:00

flags

Add gRPC headers flag support for validator client side (#5203 )

2020-03-25 11:29:04 -05:00

internal

fuzz core/blocks package (#4907 )

2020-03-03 19:02:14 +05:30

keymanager

Remove suprious error messages in wallet keymanager (#5090 )

2020-03-13 05:26:10 -07:00

node

Reduce noise in validator logs (#5307 )

2020-04-05 15:36:18 -04:00

BUILD.bazel

Remove old cross compile starlark rules (#5329 )

2020-04-07 03:01:20 +00:00

main.go

Add gRPC headers flag support for validator client side (#5203 )

2020-03-25 11:29:04 -05: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

Allow setting flags via yaml config file. (#4878 )

2020-03-19 14:46:44 -07:00

usage.go

Add gRPC headers flag support for validator client side (#5203 )

2020-03-25 11:29:04 -05: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:

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.