prysm-pulse/validator
Marcin Górzyński 02966e64d8
Feature lru cache wrapper 2 (#9511)
* Add Wrapper to LRU Cache to handle Invalid Parameters #9461

* Regenerate BUILD.bazel and simplify tests using lru.Cache

* Fix: fuzz_exports.go build error

* Fix: block_fuzz.go

* Revert lru.Cache interface

* Remove redundant err check in pending_attestations_queue_test.go

* Add tests for lru wrapper

* Use lru package in prysm/shared instead of lruwrpr

* Fix: goimports

* Fix: BUILD.bazel

Co-authored-by: Nishant Das <nishdas93@gmail.com>
2021-09-02 18:36:54 +08:00
..
accounts Move Validator Accounts Protos Into Proper Place (#9416) 2021-08-18 21:24:01 +00:00
client Feature lru cache wrapper 2 (#9511) 2021-09-02 18:36:54 +08:00
db Fix Validator Backups (#9446) 2021-08-23 21:46:04 +00:00
graffiti Add Gosec Github Action (#9332) 2021-08-15 15:24:13 +00:00
keymanager Move Validator Accounts Protos Into Proper Place (#9416) 2021-08-18 21:24:01 +00:00
node Remove Canonical Attestations From Pool Correctly (#9444) 2021-08-24 00:33:17 +00:00
package Reduce Usage of Eth2 Terminology in Prysm (#9104) 2021-06-26 19:00:33 +00:00
rpc Remove Canonical Attestations From Pool Correctly (#9444) 2021-08-24 00:33:17 +00:00
slashing-protection Better Slashing Protection Import/Export User Experience (#9355) 2021-08-11 17:24:24 +00:00
testing Eliminate Proto V2 Namespace (#9297) 2021-07-28 21:23:44 +00:00
web Update web-ui to beta.4 (#9047) 2021-06-16 13:36:43 +00:00
BUILD.bazel Add Goland Standard "cmd" Pattern for Validator Binaries (#8541) 2021-03-02 12:58:40 -06:00
README.md Change Eth2 Repository Names (#9425) 2021-08-19 13:00:57 -05:00

Prysmatic Labs Validator Client Implementation

This is the main project folder for a validator client implementation of Ethereum written in Go by Prysmatic Labs. A validator client attaches to a running beacon node in order to perform proposer/attester responsibilities for eth.

You can also read our main README and join our active chat room on Discord.

Discord

To further understand the responsibilities of an Ethereum validator, we recommend reading the official specification here