mirror of https://github.com/OffchainLabs/prysm.git synced 2026-04-19 03:01:06 -04:00

Files

Ivan Martinez d7bcea7906 Allow creating new accounts to be non-interactive (#6602 )

* Allow accounts to be made non-interactively
* Merge branch 'master' of github.com:prysmaticlabs/prysm into make-accounts-noninteractive
* Update validator/node/node.go
* Update validator/accounts/v2/list.go

2020-07-14 23:00:58 +00:00

accounts

Allow creating new accounts to be non-interactive (#6602 )

2020-07-14 23:00:58 +00:00

client

Fix inconsistent pubkey formatting in logs (#6600 )

2020-07-14 20:37:01 +00:00

Remove unused functions in validator DB (#6557 )

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

flags

Allow creating new accounts to be non-interactive (#6602 )

2020-07-14 23:00:58 +00:00

keymanager

Allow creating new accounts to be non-interactive (#6602 )

2020-07-14 23:00:58 +00:00

node

Allow creating new accounts to be non-interactive (#6602 )

2020-07-14 23:00:58 +00: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

Avoid automaxprocs default logger to printf (#6524 )

2020-07-11 00:57:43 +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

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.