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. |
||
---|---|---|
.github | ||
.well-known | ||
api | ||
async | ||
beacon-chain | ||
build | ||
cache | ||
cmd | ||
config | ||
consensus-types | ||
container | ||
contracts/deposit | ||
crypto | ||
encoding | ||
hack | ||
io | ||
math | ||
monitoring | ||
network | ||
proto | ||
runtime | ||
testing | ||
third_party | ||
time | ||
tools | ||
validator | ||
.bazelrc | ||
.bazelversion | ||
.buildkite-bazelrc | ||
.codecov.yml | ||
.deepsource.toml | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.golangci.yml | ||
.policy.yml | ||
.travis.yml | ||
bazel.sh | ||
BUILD.bazel | ||
CONTRIBUTING.md | ||
DEPENDENCIES.md | ||
deps.bzl | ||
fuzzbuzz.yaml | ||
go.mod | ||
go.sum | ||
INTEROP.md | ||
LICENSE.md | ||
nogo_config.json | ||
prysm.bat | ||
prysm.ps1 | ||
prysm.sh | ||
README.md | ||
SECURITY.md | ||
service-account.json.enc | ||
TERMS_OF_SERVICE.md | ||
WORKSPACE |
Prysm: An Ethereum Consensus Implementation Written in Go
This is the core repository for Prysm, a Golang implementation of the Ethereum Consensus specification, developed by Offchain Labs. See the Changelog for details of the latest releases and upcoming breaking changes.
Getting Started
A detailed set of installation and usage instructions as well as breakdowns of each individual component are available in the official documentation portal. If you still have questions, feel free to stop by our Discord.
Staking on Mainnet
To participate in staking, you can join the official eth2 launchpad. The launchpad is the only recommended way to become a validator on mainnet. You can explore validator rewards/penalties via Bitfly's block explorer: beaconcha.in, and follow the latest blocks added to the chain on beaconscan.
Contributing
Branches
Prysm maintains two permanent branches:
- master: This points to the latest stable release. It is ideal for most users.
- develop: This is used for development, it contains the latest PRs. Developers should base their PRs on this branch.
Guide
Want to get involved? Check out our Contribution Guide to learn more!
License
GNU General Public License v3.0