mirror of
https://github.com/sigp/lighthouse.git
synced 2026-03-18 04:13:00 +00:00
3f6c11db0e
* #6447 - Move some deprecated pages to a new section under `Archived` - Remove fallback log in mev as the log will not be present after VC using `/eth/v3/validator/blocks` endpoint by default - Add warning against using Btrfs file system (thank you @ChosunOne for the report) - Add data shared by @mcdee on tree states API queries time - Rename partial withdrawals to validator sweep to differentiate it from the upcoming execution layer partial withdrawals - Update NAT API response - Update docs on IPv6 - Rename .md files to follow a standard prefix section name, e.g., installation_*.md, advanced_*.md - Standardise .md files using underscore `_` instead of hyphen `-` to be consistent with other files naming conventions.
36 lines
2.3 KiB
Markdown
36 lines
2.3 KiB
Markdown
# 📦 Installation
|
|
|
|
Lighthouse runs on Linux, macOS, and Windows.
|
|
|
|
There are three core methods to obtain the Lighthouse application:
|
|
|
|
- [Pre-built binaries](./installation_binaries.md).
|
|
- [Docker images](./installation_docker.md).
|
|
- [Building from source](./installation_source.md).
|
|
|
|
Additionally, there are two extra guides for specific uses:
|
|
|
|
- [Raspberry Pi 4 guide](./archived_pi.md). (Archived)
|
|
- [Cross-compiling guide for developers](./installation_cross_compiling.md).
|
|
|
|
There are also community-maintained installation methods:
|
|
|
|
- [Homebrew package](./installation_homebrew.md).
|
|
- Arch Linux AUR packages: [source](https://aur.archlinux.org/packages/lighthouse-ethereum),
|
|
[binary](https://aur.archlinux.org/packages/lighthouse-ethereum-bin).
|
|
|
|
## Recommended System Requirements
|
|
|
|
Before [The Merge](https://ethereum.org/en/roadmap/merge/), Lighthouse was able to run on its own with low to mid-range consumer hardware, but would perform best when provided with ample system resources.
|
|
|
|
After [The Merge](https://ethereum.org/en/roadmap/merge/) on 15<sup>th</sup> September 2022, it is necessary to run Lighthouse together with an execution client ([Nethermind](https://nethermind.io/), [Besu](https://www.hyperledger.org/use/besu), [Erigon](https://github.com/ledgerwatch/erigon), [Geth](https://geth.ethereum.org/), [Reth](https://github.com/paradigmxyz/reth)). The following system requirements listed are therefore for running a Lighthouse beacon node combined with an execution client , and a validator client with a modest number of validator keys (less than 100):
|
|
|
|
- CPU: Quad-core AMD Ryzen, Intel Broadwell, ARMv8 or newer
|
|
- Memory: 32 GB RAM*
|
|
- Storage: 2 TB solid state drive
|
|
- Network: 100 Mb/s download, 20 Mb/s upload broadband connection
|
|
|
|
> *Note: 16 GB RAM is becoming rather limited due to the increased resources required. 16 GB RAM would likely result in out of memory errors in the case of a spike in computing demand (e.g., caused by a bug) or during periods of non-finality of the beacon chain. Users with 16 GB RAM also have a limited choice when it comes to selecting an execution client, which does not help with the [client diversity](https://clientdiversity.org/). We therefore recommend users to have at least 32 GB RAM for long term health of the node, while also giving users the flexibility to change client should the thought arise.
|
|
|
|
Last update: April 2023
|