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

Files

Raul Jordan 3023f5dbd3 Accounts V2: Derived Keymanager Sign (#6667 )

* amend derived with secret keys cache
* all tests for sign
* Merge branch 'master' into sign-derived
* formatting
* Merge branch 'sign-derived' of github.com:prysmaticlabs/prysm into sign-derived
* initialize
* use seed
* fix build
* Merge refs/heads/master into sign-derived
* Merge refs/heads/master into sign-derived
* Update validator/keymanager/v2/derived/derived.go

2020-07-21 21:15:47 +00:00

accounts

Accounts V2: Derived Keymanager Sign (#6667 )

2020-07-21 21:15:47 +00:00

client

Applies assertion funcs to validator/client tests (#6654 )

2020-07-21 13:02:21 +00:00

Remove unused functions in validator DB (#6557 )

2020-07-11 17:23:30 +00:00

flags

Accounts V2: Create Wallet Non-Interactively + Add Test Coverage (#6611 )

2020-07-17 08:21:16 +00:00

keymanager

Accounts V2: Derived Keymanager Sign (#6667 )

2020-07-21 21:15:47 +00:00

node

Accounts V2: Create Wallet via CLI (#6543 )

2020-07-14 23:05:21 -05:00

slashing-protection

Move slashing protection code to separate files for proposing and attesting (#6406 )

2020-07-03 19:54:42 +00:00

testing

Move slashing protection code to separate files for proposing and attesting (#6406 )

2020-07-03 19:54:42 +00:00

BUILD.bazel

Avoid automaxprocs default logger to printf (#6524 )

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

main.go

Accounts V2: Create Wallet via CLI (#6543 )

2020-07-14 23:05:21 -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

Integrate Accounts v2 Keymanager Into Validator Client (#6489 )

2020-07-08 05:01:09 +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.