Get help and resources
Ask for help
- Discord: The Prysm Discord is the fastest place to ask questions and follow release announcements.
- Execution client problems: the team behind your execution client (Besu, Erigon, Geth, Nethermind, Reth…) knows it best, so ask them on their own Discord or GitHub.
Report a bug
Open an issue on GitHub using the bug report template. Include your Prysm version (beacon-chain --version), operating system, how you run Prysm, the flags you use, and the relevant logs.
Report a security vulnerability
Don't open a public issue for a vulnerability. Follow the security policy: it points to the signed security.txt, which lists the reporting address, prysm@offchainlabs.com, and the encryption keys.
Block explorers
Look up your validators, blocks, and the network:
- beaconcha.in (mainnet) and hoodi.beaconcha.in (Hoodi)
- beaconscan.com
Security audits
Prysm's Phase 0 code was audited before the beacon chain launched in 2020:
- Quantstamp report (completed October 13, 2020)
- Trail of Bits report (completed October 6, 2020)
Incident reports
The Prysm team publishes postmortems of incidents that affected Prysm:
Contribute to Prysm
Prysm is open source. Read CONTRIBUTING.md in the Prysm repository for how to set up your environment, test your changes, and submit a pull request. Issues labeled help-wanted are a good place to start, and for anything beyond a small fix, open an issue to discuss it first.
License
Prysm is licensed under the GNU General Public License v3.0.
Further reading
- ethereum.org staking guide
- Ethereum consensus specifications
- Staking Launchpad (mainnet) and Hoodi Launchpad
- Client diversity: why running a minority client helps the network
- Other consensus clients: Grandine, Lighthouse, Lodestar, Nimbus, Teku