# Install lighthouse with Homebrew, apk, Nix Rust Ethereum 2.0 Client. Version 8.2.0 via Homebrew; verified 2026-06-22. ## Install ```sh sudo av install brew:lighthouse ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install lighthouse ``` Evidence: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add lighthouse ``` Evidence: Alpine Linux edge package indexes: lighthouse from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Nix (92%): ```sh nix profile install nixpkgs#lighthouse ``` Evidence: nixpkgs package indexes: pkgs/by-name/li/lighthouse/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:lighthouse - **Package manager:** Homebrew - **Package manager page:** - **Version:** 8.2.0 - **Source summary:** Rust Ethereum 2.0 Client - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-06-22T14:05:10-07:00 - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - lighthouse (cli) - lighthouse (alias) ## Build dependencies - cmake - protobuf - rust ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 8.2.0 - Package-manager updated: 2026-06-22 - Local data: ok - Upstream repository: https://github.com/sigp/lighthouse - Upstream latest detected: v8.2.0 (current) ## 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 Notes broad file, network, media, or database tool signal. - **Geiger risk:** blue / medium - broad file, network, media, or database tool signal ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** lighthouse - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Nix - lighthouse: normalized package name match | nixpkgs package indexes: pkgs/by-name/li/lighthouse/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - apk - lighthouse - 8.1.3-r0: normalized package name match | Alpine Linux edge package indexes: lighthouse from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Ethereum 2.0 Client | https://lighthouse.sigmaprime.io/ - apk - lighthouse-doc - 8.1.3-r0: normalized package name match | Alpine Linux edge package indexes: lighthouse-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Ethereum 2.0 Client (documentation) | https://lighthouse.sigmaprime.io/ ## Related links - [Secret-risk packages](https://www.automicvault.com/pkg/secret-risk-packages/) - Has protected-tool coverage, approval-gate, or non-low Geiger security signals. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [cmake](https://www.automicvault.com/pkg/brew/cmake/) - Build dependency declared by Homebrew. - [protobuf](https://www.automicvault.com/pkg/brew/protobuf/) - Build dependency declared by Homebrew. - [rust](https://www.automicvault.com/pkg/brew/rust/) - Build dependency declared by Homebrew. - [teku](https://www.automicvault.com/pkg/brew/teku/) - Shares av.db curated category or tags: blockchain, cli, consensus-client, ethereum, networking. - [btcli](https://www.automicvault.com/pkg/brew/btcli/) - Shares av.db curated category or tags: blockchain, cli, networking. - [hsd](https://www.automicvault.com/pkg/brew/hsd/) - Shares av.db curated category or tags: blockchain, cli, networking. - [oasis](https://www.automicvault.com/pkg/brew/oasis/) - Shares av.db curated category or tags: blockchain, cli, networking. - [stellar-core](https://www.automicvault.com/pkg/brew/stellar-core/) - Shares av.db curated category or tags: blockchain, cli, networking. - [floresta](https://www.automicvault.com/pkg/brew/floresta/) - Shares av.db curated category or tags: blockchain, cli, networking. - [ord](https://www.automicvault.com/pkg/brew/ord/) - Shares av.db curated category or tags: blockchain, cli, networking. - [asuka](https://www.automicvault.com/pkg/brew/asuka/) - Shares av.db curated category or tags: cli, networking, rust. - [lighthouse](https://www.automicvault.com/pkg/npm/lighthouse/) - Same normalized package name in another local ecosystem. ## Combined YAML source View the package source record on GitHub. [combined/lighthouse.yml](https://github.com/automic-vault/db/blob/main/combined/lighthouse.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph