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

Files

Shay Zluf 1315a15d9d Import proposal protection (#7430 )

* Import proposals protection db

* Import old proposal protection data structure to new one

* test empty slots

* Update validator/db/kv/new_proposal_history.go

Co-authored-by: Victor Farazdagi <simple.square@gmail.com>

* Update validator/db/kv/new_proposal_history_test.go

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
Co-authored-by: Victor Farazdagi <simple.square@gmail.com>

2020-10-08 11:51:50 +00:00

accounts

Fix deepsource findings (#7457 )

2020-10-08 08:36:47 +00:00

client

Miscellaneous code quality improvements (#7414 )

2020-10-04 15:03:10 +00:00

Import proposal protection (#7430 )

2020-10-08 11:51:50 +00:00

flags

Optional services flags (#7358 )

2020-09-30 20:55:56 +00:00

keymanager

Fix deepsource findings (#7457 )

2020-10-08 08:36:47 +00:00

node

Warn if user is not using a supported platform (#7381 )

2020-10-02 09:45:34 +03:00

rpc

Fix deepsource findings (#7457 )

2020-10-08 08:36:47 +00:00

slashing-protection

Better naming for constructor funcs (#7316 )

2020-09-23 08:59:49 +00:00

testing

Fix propose protect error handling (#7188 )

2020-09-11 09:53:53 -05:00

BUILD.bazel

Revert PR #7429 to fix building on windows (#7456 )

2020-10-07 19:09:40 +00:00

main.go

Revert PR #7429 to fix building on windows (#7456 )

2020-10-07 19:09:40 +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

Optional services flags (#7358 )

2020-09-30 20:55:56 +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.