install

Additional install commands

macOS

Homebrewverified · 100%

brew install lighthouse

local Homebrew formula metadata

Linux

Alpine Linux apkverified · 92%

sudo apk add lighthouse

Alpine Linux edge package indexes · lighthouse · source: dl-cdn.alpinelinux.org

Nixverified · 92%

nix profile install nixpkgs#lighthouse

nixpkgs package indexes · pkgs/by-name/li/lighthouse/package.nix · source: api.github.com

overview

Package summary

Rust Ethereum 2.0 Client

Project links

Commands and aliases

lighthouse

history

Project history and usage

Lighthouse is Sigma Prime's Rust implementation of an Ethereum proof-of-stake consensus client. It supplies the beacon-node and validator-client software used to participate in Ethereum consensus, following the ethereum/consensus-specs work rather than defining a separate chain protocol.

Project history

The project grew out of the multi-client Ethereum 2.0 effort, where independent clients were built in several languages to avoid network-level monoculture. Lighthouse's identity has remained tied to Rust, security review, fuzzing, and operational documentation for validators.

The v1.0.0 release on November 24, 2020 marked the transition to a production/stable development phase for genesis staking, with mainnet genesis state included in the binary. After Ethereum's proof-of-stake chain became operational, Lighthouse continued as one of the major consensus-layer implementations alongside clients such as Prysm, Teku, Nimbus, and Lodestar.

Adoption history

Lighthouse was adopted by Ethereum node operators and solo stakers because it packaged a beacon node, validator client, validator-account tooling, Docker images, and detailed operator documentation in one client family. Distribution through Homebrew and other package managers made it unusually easy for Unix users to install a consensus client from the same workflow used for ordinary developer tools.

How it is used

Typical usage is running a Lighthouse beacon node beside an Ethereum execution client, then running a validator client for staking keys when the operator is validating. The command-line surface also includes account and validator utilities, making the package relevant both to long-running infrastructure and to one-off validator administration.

Why package nerds care

For package maintainers, Lighthouse is a good example of a blockchain daemon that is not just a single executable: releases are tied to protocol upgrades, binary distribution matters for validators, and operational correctness depends on pairing it with the right execution-layer and networking configuration.

Timeline

2020-11-24: Lighthouse v1.0.0 marked the production/stable phase for Ethereum mainnet genesis staking.
2022: Ethereum's move to proof of stake made consensus clients such as Lighthouse part of the normal full-node stack.
2026: Lighthouse documentation described it as an Ethereum consensus client implementing the ethereum/consensus-specs repository.

Related projects

Lighthouse is related to the ethereum/consensus-specs repository, the Ethereum execution clients it must pair with, and other consensus clients including Prysm, Teku, Nimbus, and Lodestar. Sigma Prime also maintains Siren, a user interface for Lighthouse beacon-node and validator-client installations.

Sources

security posture

Risk level: blue

broad file, network, media, or database tool signal.

Risk classifier

blue risk · medium confidence · tool

Why

broad file, network, media, or database tool signal

Signals

text:client

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 5 platform targets.
Build metadata lists 3 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix: ~/.lighthouse/{network}/validators/validator_definitions.yml

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix: ~/.lighthouse/{network}/validators/**/voting-keystore.json~/.lighthouse/{network}/secrets/*~/.lighthouse/{network}/validators/api-token.txt

executables

Installed executables

Command	Kind	Exposure	Note
`lighthouse`	cli	global executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-11-04

manager version8.3.2

manager updated2026-10-23

local dataok

upstreamcurrent

latest detectedv8.3.2

https://github.com/sigp/lighthouse

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:lighthouse
Version	8.3.2
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/lighthouse
Homepage	https://lighthouse.sigmaprime.io/
Repository	https://github.com/sigp/lighthouse
Upstream docs	https://lighthouse.sigmaprime.io/
License	Apache-2.0
Source archive	https://github.com/sigp/lighthouse/archive/refs/tags/v8.3.2.tar.gz
Last updated	2026-10-23T05:12:24Z
Pulse	updated
Build dependencies	cmake, protobuf, rust
Bottle	available (on arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	lighthouse
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

lighthouse

nix profile install nixpkgs#lighthouse

normalized package name match
Matched by: Lighthouse

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/li/lighthouse/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

apk95%

lighthouse 8.2.2-r0

Ethereum 2.0 Client

https://lighthouse.sigmaprime.io/

sudo apk add lighthouse

License: Apache-2.0
Architecture: x86_64
Source Package: lighthouse
1 dependencies
1 provides
normalized package name match
Matched by: Lighthouse

Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: lighthouse from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

apk95%

lighthouse-doc 8.2.2-r0

Ethereum 2.0 Client (documentation)

https://lighthouse.sigmaprime.io/

sudo apk add lighthouse-doc

License: Apache-2.0
Architecture: x86_64
Source Package: lighthouse
normalized package name match
Matched by: Lighthouse

Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: lighthouse-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Combined YAML source

View the package source record on GitHub.

combined/lighthouse.yml

Used sources

Geiger risk classifier
cross-ecosystem install command graph
curated configuration and credential file locations
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment
pkg.so package database
pkgdb category and tag curation

Install lighthouse with Homebrew, apk, Nix