mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2025-01-18 15:54:13 +00:00
a94f2b93e3
* `filterAndCacheActiveKeys`: Add test cases - Validator is in unknown status (to be fitered out) - Validator is in pending status, with activation period > current period (to be filtered out) - Validator is in pending status, with activation period == current period (to be kept) * `filterAndCacheActiveKeys`: Keep exiting keys Initially: ------- If a validator is in exiting (so, with status==EXITING != ACTIVE) state, it will be filtered out by the `filterAndCacheActiveKeys` function. The validator won't be registered to the beacon node. If this exiting validator has to propose a block: - the block will be proposed using local block building only. - the fee recipient will be the one set in the beacon node. (Additionally, if the beacon node Prysm without any fee recipient defined at the beacon node level, the fee recipient will default on the `0x00000...` burn address.) This commit modifies the `filterAndCacheActiveKeys` function by stopping filtering out exiting validators. |
||
|---|---|---|
| .. | ||
| accounts | ||
| client | ||
| db | ||
| graffiti | ||
| helpers | ||
| keymanager | ||
| node | ||
| package | ||
| rpc | ||
| slashing-protection-history | ||
| testing | ||
| web | ||
| README.md | ||
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.
To further understand the responsibilities of an Ethereum validator, we recommend reading the official specification here