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

Files

Ivan Martinez 607d5fdf4e Accounts-V2: Change accounts-v2 import to use directory of keystores (#6742 )

* Finish implementation of importing dir of keystores

* Fix

* Fix importing

* Finish testing import account

* Update validator/accounts/v2/accounts_import.go

* Fix

* Fix

* fix

* Fix prompt

Co-authored-by: Raul Jordan <raul@prysmaticlabs.com>

2020-07-28 09:18:22 -05:00

accounts

Accounts-V2: Change accounts-v2 import to use directory of keystores (#6742 )

2020-07-28 09:18:22 -05:00

client

Make external slasher protection fail on load if slasher is not reachable (#6704 )

2020-07-27 20:06:49 +00:00

Applies assertion funcs to validator tests (#6694 )

2020-07-23 01:13:52 +00:00

flags

Accounts-V2: Change accounts-v2 import to use directory of keystores (#6742 )

2020-07-28 09:18:22 -05:00

keymanager

Accounts-V2: Change keystore filename to include timestamp (#6741 )

2020-07-28 00:02:29 +00:00

node

Fix Validator Accounts-V2 Runtime (#6714 )

2020-07-24 21:36:28 +00:00

slashing-protection

Make external slasher protection fail on load if slasher is not reachable (#6704 )

2020-07-27 20:06:49 +00:00

testing

Make external slasher protection fail on load if slasher is not reachable (#6704 )

2020-07-27 20:06:49 +00:00

BUILD.bazel

Avoid automaxprocs default logger to printf (#6524 )

2020-07-11 00:57:43 +00:00

main.go

Better gRPC retry including stream retry (#6670 )

2020-07-21 22:45:52 -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

Refactor dependencies, make Prysm "go gettable" (#6053 )

2020-05-31 14:44:34 +08:00

usage.go

Better gRPC retry including stream retry (#6670 )

2020-07-21 22:45:52 -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.