fad118cb04
ValidateClock in ValidateAttestationTime is useless The check is that the attSlot is not > than the currentslot + 128 slots. Later there's a check that the attSlot start time is not > than current slot start time + clockDisparity. if attSlot > than currentSlot + 128 slots, then the second check would fail anyway. The lattest check already guarantees that the attSlot cannot be larger than the currentSlot, therefore it may never happen that attEpoch > currentEpoch. We just need to check for Deneb that attEpoch >= currentEpoch - 1. Removes also some duplicated variables like the attestation epoch being computed twice. |
||
|---|---|---|
| .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 | ||
| distroless_deps.bzl | ||
| fuzzbuzz.yaml | ||
| go.mod | ||
| go.sum | ||
| INTEROP.md | ||
| LICENSE.md | ||
| MODULE.bazel | ||
| MODULE.bazel.lock | ||
| 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