ecad5bbffc
* e2e: Provide e2e config yaml to web3signer * fix build for //testing/endtoend:go_default_test * Update with web3signer with teku fixes * buildifier * Add slasher case for web3signer * Update testing/endtoend/minimal_e2e_test.go * Update web3signer to 21.10.6 * Revert "Update web3signer to 21.10.6" This reverts commit bdf3c408f2a0432379fa1a735a2e3f70c62d11cc. * Remove slasher part of web3signer e2e tests * Revert "Remove slasher part of web3signer e2e tests" This reverts commit 24249802ae34fb7727b83dbfa187d73c1d97d2f8. * fix slasher web3signer test * fixing build * updating yaml to match testnet_e2e_config.go * trying a different order to the e2e test and adding a log * trying different way to kill process * handling unhandled error * testing changes to config WIP * fixing bazel WIP * fixing build * ignoring test for now to test * fixing bazel * Test only web3signer e2e * rolling back some commits to test * fixing bazel * trying an updated web3signer version * changing flag to match version * trying current version of develop for web3signer * testing not using the --network property * addressing build error * testing config change * reverting to go bakc to using the network file * testing adding epochs per sync committee period * rolling back configs * removing check to test * adding log to get sync committee duties and changing bellatrix fork epoch to something large and altair to epoch 1 * fixing bazel * updating epoch in config file * fixing more descrepencies between the configurations * removing un used yaml * removing goland added duplicates * reverting using network minimal * fixing bug * rolling back some changes * rolling back some changes * rolling back changes * making sure web3signer test doesn't make it to bellatrix fork yet * reverting changes I did not touch * undo comment * Update testing/endtoend/deps.bzl * Apply suggestions from code review * rm nl * fix //testing/endtoend:go_mainnet_test * Remove unnecessary dep * fix //testing/endtoend:go_mainnet_test * addressing review comments * fixing build and internal conflict * removing web3signer slasher test as it's unneeded due to the interface nature of key signing, the regular slashing test is enough * fix: The validator we fetch from the binary can only run before altair, if you add that and the web3signer then these things can never run together as the web3signer sets it to before bellatrix Co-authored-by: james-prysm <90280386+james-prysm@users.noreply.github.com> Co-authored-by: James He <james@prysmaticlabs.com> Co-authored-by: Nishant Das <nishdas93@gmail.com> Co-authored-by: Raul Jordan <raul@prysmaticlabs.com> |
||
---|---|---|
.github | ||
.well-known | ||
api | ||
async | ||
beacon-chain | ||
build/bazel | ||
cache/lru | ||
cmd | ||
config | ||
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.Dockerfile | ||
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 Prysmatic 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