// the find
OffchainLabs/prysm
Go implementation of Ethereum proof of stake
Prysm is Offchain Labs' Go implementation of the Ethereum proof-of-stake consensus layer — one of the major production beacon chain clients running on mainnet today. If you're building Ethereum infrastructure, running a validator, or studying consensus protocol implementation, this is the real thing.
The codebase is exceptionally well-structured for its scale: each subsystem (blockchain, cache, core, p2p) is a discrete package with its own mocks and test files, making it navigable despite being enormous. Test coverage is serious — fuzz tests, race condition tests, and spec-compliance tests are all present alongside unit tests. The Bazel build system alongside standard Go tooling means you can build individual targets without pulling the whole dependency graph. Consensus spec compliance is tracked explicitly (v1.4.0 badge, `.ethspecify.yml`) so protocol drift is detectable rather than accidental.
The repo recently moved from the original `prysmaticlabs` org to `OffchainLabs`, which means historical issues, PRs, and community context are split across two GitHub orgs — confusing if you're trying to understand the project's history or bug backlog. The dual build system (Bazel + Go modules) creates real friction: Bazel BUILD files must be kept in sync with Go code manually, and contributors who don't know Bazel will break the Buildkite CI without understanding why. The README is thin for a project of this complexity — it points to an external docs portal rather than giving you a mental model of the components, so onboarding a new contributor requires reading across three sources. Running a full node requires pairing with an execution client, but there's no quick-start in the repo itself that shows the complete setup.