Go to file
2022-01-20 10:37:27 +08:00
.github Make Radek and Nishant code owners of duplicated state code (#10079) 2022-01-13 21:16:42 +00:00
.well-known
api
async
beacon-chain make it better (#10101) 2022-01-20 10:37:27 +08:00
cache/lru
cmd
config
container
contracts/deposit
crypto
encoding
hack
io
math
monitoring
network
proto Web3Signer: Sign Method Implementation (#10084) 2022-01-18 14:31:58 -06:00
runtime
testing e2e: Add web3signer component (#10088) 2022-01-19 16:22:23 +00:00
third_party
time
tools
validator Web3Signer: Sign Method Implementation (#10084) 2022-01-18 14:31:58 -06:00
.bazelrc
.bazelversion
.buildkite-bazelrc
.codecov.yml
.deepsource.toml
.dockerignore
.gitattributes
.gitignore
.golangci.yml
.policy.yml Include Policy Bot Application (#7523) 2020-10-14 04:14:38 +00:00
.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 e2e: Add web3signer component (#10088) 2022-01-19 16:22:23 +00:00

Prysm: An Ethereum Consensus Implementation Written in Go

Build status Go Report Card Consensus_Spec_Version 1.1.8 Discord

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

Terms of Use