prysm-pulse/validator
hyunchel 470ea6d717
Remove no-op cancel func (#13069)
This cancel function is currently a no-op due to the blank identifier.
One might argue that the cancel func should be restored from no-op by
replacing the blank identifier with the proper variable. When the parent
context is cancelled, however, all the functions down the call tree with
the context will be notified of the cancellation anyway. Removing the
cancel function would not change any outcome under the current
implementation.

Co-authored-by: Preston Van Loon <pvanloon@offchainlabs.com>
Co-authored-by: Radosław Kapka <rkapka@wp.pl>
2023-10-30 14:43:25 +00:00
..
accounts Refactor Error String Formatting According to Go Best Practices (#13092) 2023-10-23 07:57:25 +00:00
client Remove no-op cancel func (#13069) 2023-10-30 14:43:25 +00:00
db Refactor Exported Names to Follow Golang Best Practices (#13075) 2023-10-20 16:45:33 +00:00
graffiti Update to V4 🚀 (#12134) 2023-03-17 18:52:56 +00:00
helpers Update to V4 🚀 (#12134) 2023-03-17 18:52:56 +00:00
keymanager Refactor Exported Names to Follow Golang Best Practices (#13075) 2023-10-20 16:45:33 +00:00
node Refactor Exported Names to Follow Golang Best Practices (#13075) 2023-10-20 16:45:33 +00:00
package Update cross compile toolchains (#12069) 2023-03-07 20:09:46 +00:00
rpc HTTP Validator API: /eth/v1/validator/{pubkey}/feerecipient (#13085) 2023-10-24 16:55:45 +00:00
slashing-protection-history Update to V4 🚀 (#12134) 2023-03-17 18:52:56 +00:00
testing Remove remote slashing protection feature (#12989) 2023-10-04 04:15:06 +00:00
web Remove uses of deprecated go_embed rules_go (#12719) 2023-08-16 15:47:09 +00: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