macOS
Homebrewverifiziert · 100%
brew install lighthouselocal Homebrew formula metadata
brew / Rang 3847
lighthouse mit Homebrew, apk, Nix installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für lighthouse in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Linux
Alpine Linux apkverifiziert · 92%
sudo apk add lighthouseAlpine Linux edge package indexes · lighthouse · Quelle: dl-cdn.alpinelinux.org
Nixverifiziert · 92%
nix profile install nixpkgs#lighthousenixpkgs package indexes · pkgs/by-name/li/lighthouse/package.nix · Quelle: api.github.com
Überblick
Paketzusammenfassung
Rust Ethereum 2.0 Client
Projektlinks
Befehle und Aliase
- lighthouse
Verlauf
Projektgeschichte und Nutzung
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.
Projektgeschichte
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.
Adoptionsgeschichte
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.
Wie es verwendet wird
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.
Warum Paket-Nerds sich dafür interessieren
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.
Zeitleiste
- 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.
Quellen
Sicherheitslage
Risikostufe: blue
broad file, network, media, or database tool signal.
Risikoklassifikator
blue Risiko · mittel Konfidenz · tool
Warum
- broad file, network, media, or database tool signal
Signale
- text:client
Installationsverhalten
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Homebrew-Bottle-Metadaten sind für 5 Plattformziele verfügbar.
- Build-Metadaten listen 3 Build-Abhängigkeiten.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
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
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
lighthouse | cli | globales Executable |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-11-04
Manager-Version8.3.2
Manager aktualisiert2026-10-23
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv8.3.2
https://github.com/sigp/lighthouse
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:lighthouse |
|---|---|
| Version | 8.3.2 |
| Paketmanager | Homebrew |
| Paketmanager-Seite | https://formulae.brew.sh/formula/lighthouse |
| Homepage | https://lighthouse.sigmaprime.io/ |
| Repository | https://github.com/sigp/lighthouse |
| Upstream-Dokumentation | https://lighthouse.sigmaprime.io/ |
| Lizenz | Apache-2.0 |
| Quellarchiv | https://github.com/sigp/lighthouse/archive/refs/tags/v8.3.2.tar.gz |
| Zuletzt aktualisiert | 2026-10-23T05:12:24Z |
| Pulse | updated |
| Build-Abhängigkeiten | cmake, protobuf, rust |
| Bottle | verfügbar (auf arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux) |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
Details aus der Quelldatenbank
| 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 |
|
Source-Datenbank-Treffer
Andere Paketmanager-Einträge
Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.
Nix95%
lighthouse
nix profile install nixpkgs#lighthouse- normalized package name match
- Abgeglichen nach: Lighthouse
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 Abhängigkeiten
- 1 stellt bereit
- normalized package name match
- Abgeglichen nach: Lighthouse
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
- Abgeglichen nach: Lighthouse
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- 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