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

Files

Ivan Martinez 6351d187ef Accounts V2: Remove unused passwords-dir and deprecate flag (#6916 )

* Remove passwords dir
* Deprecate flag
* Merge branch 'master' of github.com:prysmaticlabs/prysm into remove-passwords-dir
* Properly deprecate flag
* Merge branch 'master' into remove-passwords-dir
* Merge refs/heads/master into remove-passwords-dir
* Merge refs/heads/master into remove-passwords-dir

2020-08-07 00:02:30 +00:00

accounts

Accounts V2: Remove unused passwords-dir and deprecate flag (#6916 )

2020-08-07 00:02:30 +00:00

client

Update SignRequest for key manager (#6917 )

2020-08-06 18:18:38 -05:00

Code quality issues - Remove unused code (#6864 )

2020-08-05 13:59:46 +02:00

flags

Accounts V2: Remove unused passwords-dir and deprecate flag (#6916 )

2020-08-07 00:02:30 +00:00

keymanager

Accounts V2: Remove unused passwords-dir and deprecate flag (#6916 )

2020-08-07 00:02:30 +00:00

node

Load config after Configure config (#6821 )

2020-08-01 00:46:55 +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

Accounts V2: Remove unused passwords-dir and deprecate flag (#6916 )

2020-08-07 00:02:30 +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

Accounts V2: Remove unused passwords-dir and deprecate flag (#6916 )

2020-08-07 00:02: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:

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.