sigp/lighthouse

Ethereum consensus client in Rust

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 28 minutes ago
Type:Server / PlatformCategory(s):Blockchains, Nodes & ProtocolsBlockchain & Web3
Added to GitGenius on September 20th, 2026
Created on July 6th, 2018
Open Issues & Pull Requests: 555 (+0)
GitHub issues: Enabled
Number of forks: 1,061
Total Stargazers: 3,473 (+0)
Total Subscribers: 69 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 261
New in 7 days: 14
Closed in 7 days: 3
Avg open age: 443 days
Stale 30+ days: 216
Stale 90+ days: 176

Recent activity

Opened in 7 days: 13
Closed in 7 days: 3
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (91)
  • das (82)
  • gloas (74)
  • optimization (74)
  • HTTP-API (59)
  • code-quality (56)
  • enhancement (54)
  • UX-and-logs (53)

Detailed Description

Lighthouse is an Ethereum consensus client written in Rust that enables participation in Ethereum proof-of-stake consensus.

Lighthouse solves the problem of needing a reliable, performant consensus client implementation for Ethereum's proof-of-stake network. The tool implements the Ethereum consensus specification in Rust, a language chosen for its memory safety guarantees and performance characteristics comparable to C++. The implementation has undergone continuous fuzzing and multiple external security reviews to ensure robustness for mainnet use.

Lighthouse is suitable for anyone running an Ethereum validator or node who wants a consensus client implementation prioritizing security and performance. The project maintains two permanent branches: a stable branch for production use and an unstable branch for development. The tool is ready for use on Ethereum consensus mainnet and is fully open-source. The team actively participates in specification work and security analysis for Ethereum's proof-of-stake consensus, meaning the implementation evolves alongside the protocol itself.

The project maintains a development blog with periodic progress updates and roadmap insights. The team actively welcomes contributors and provides documentation for both users and developers. Communication channels include a dedicated Discord server and a development updates mailing list for release notifications and network status information.