prysm-pulse/validator
Ivan Martinez ad8716a58e
Refactor validator protection for attesters (#5695)
* Finish refactor for attestation protection

* Finish refactor for proposal history

* Revert "Finish refactor for proposal history"

This reverts commit 2f13720063da8c9bd972d2007d673ab8b8f1b44e.

* Fix tests

* Implement UpdateProtections

* Implement refactor

* Fixes

* fix

* Undo proposer changes

* Fix test

* Final look through

* Add tests for protections function

* Add lock

* Add flag in front of attester protection code

* Add proper rwlocks and fix flags

* fix

* fix build

* Fix atestation tests

* Fix deprecated flags

* Add protect attester to standard attesting test

* Remove comment

* gofmt

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2020-05-08 10:16:53 -05:00
..
accounts Add confirm password to validator accounts create (#5762) 2020-05-06 19:50:19 -04:00
client Refactor validator protection for attesters (#5695) 2020-05-08 10:16:53 -05:00
db Refactor validator protection for attesters (#5695) 2020-05-08 10:16:53 -05:00
flags Update gateway max resv size to 16MB (#5756) 2020-05-06 21:01:23 +00:00
internal Implement Stream Duties Functionality (#5685) 2020-05-06 14:15:31 -05:00
keymanager libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
node Clean usage of cli.context in validator/node (#5758) 2020-05-07 10:14:08 -05:00
BUILD.bazel libfuzz based tests (#5095) 2020-05-05 07:22:26 +00:00
main.go Add confirm password to validator accounts create (#5762) 2020-05-06 19:50:19 -04: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 Deprecate span map cache flag (#5551) 2020-04-22 15:53:09 +00:00
usage.go Update gateway max resv size to 16MB (#5756) 2020-05-06 21:01:23 +00:00

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:

Discord Gitter

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.