mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2024-12-25 04:47:18 +00:00
16bccf05cf
* add --enable --disable flags for validator accounts * refactor DeleteAccountConfig into AccountConfig to be used for enable and disable feature * add `disable` flag for validator accounts * [wip] add method to disable account * refactor account delete * add disable & enable with proper filters * fix keymanager unit tests * update DisabledPublicKeys to be a string instead of [][]byte * fix FetchValidatingPrivateKeys to only fetch active keys with new string format * fix FetchValidationPrivateKeys with new DisabledPublicKeys format (as a string) * rename file + update AccountsConfig to include Disable, Enable and Delete distinct attributes * rename accounts_activation -> accounts_enable_disable * revert changes from using string to [][]byte for DisabledPublicKeys * add FetchAllValidatingPublicKeys to preserve the functionality for accounts list, backup and delete * fix unit tests * convert publickeys from [][]byte to str before passing it to pb message * add unit tests for disable keys * add unit tests for EnableAccounts * revert WORKSPACE LLM for now * ran gazelle * move function to convert KeymanagerOpts to Config inside rpc and run gazelle * add unit tests for FetchAllValidatingPublicKeys * fix keymanageropts for InteropKey * Fix mistake for enable accounts * add docstring to DisableAccountsCli and EnableAccountsCli * remove previous testnet and add toledo & pyrmont |
||
---|---|---|
.. | ||
accounts | ||
client | ||
db | ||
flags | ||
keymanager | ||
node | ||
rpc | ||
slashing-protection | ||
testing | ||
web | ||
BUILD.bazel | ||
main.go | ||
README.md | ||
usage_test.go | ||
usage.go |
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.