Nodes and consensus
Lighthouse
An Ethereum consensus client.
Green — compatible use if you keep the notices
- SPDX or status
- Apache-2.0
- Confidence
- high
- Maintainer
- Sigma Prime
- Runtime
- Ethereum consensus
- Repository
- sigp/lighthouse
GitHub licence API reported Apache-2.0 on 2026-10-01. Blockchain Lab has not audited this repository. A licence check is not a vulnerability scan, a dependency review, or a security audit.
Keep the Apache notice if you distribute it.
Reuse status
Research available. Reuse pending.
A permissive licence file was recorded. The reuse gates are unmet, so nothing from the repository is exported.
- Source class
- S3 candidate
- Commit
- Not pinned
- Source-derived demo
- Held
Available
- E0: Metadata
- E1: Research report
- E2: Citation bundle
- E3: Pattern blueprint
- E4: Test plan
- E5: Original scaffold
Not available
- E6: Source-derived demo pack — held
- E7: Full source bundle — held
- E8: Dataset export — held
- E9: Model-training pack — held
- E10: Production candidate pack — held
Lighthouse has a permissive file on record. That is not a cleared export. Non-commercial or demo use does not remove the licence duty. When in doubt, link — do not copy.
Use
- Running a consensus client beside an execution client
Do not use for
- A staking-as-a-yield product
- A claim about returns
Risks
- Running a validator is an operations and slashing problem.
- This client does not define a yield.
Reviews required
- Validator key ceremony and slashing runbook, if you run one
No source code is reproduced on this page. No commit SHA is published, because this release did not pin one.