mirror of
https://github.com/sigp/lighthouse.git
synced 2026-03-11 18:04:18 +00:00
3070cb7c39
* linter * Add markdown linter * add env * only check markdown * Add token * Update .github/workflows/test-suite.yml * Markdown linter * Exit code * Update script * rename * mdlint * Add an empty line after end of file * Testing disable * add text * update mdlint.sh * ori validator inclusion * Add config yml file * Remove MD041 and fix advanced-datadir file * FIx validator inclusion file conflict * Merge branch 'unstable' into markdown-linter * change files * Merge branch 'markdown-linter' of https://github.com/chong-he/lighthouse into markdown-linter * mdlint * Remove MD025 * Remove MD036 * Remove MD045 * Removr MD001 * Set MD028 to false * Remove MD024 * Remove MD055 * Remove MD029 * Remove MD040 * Set MD040 to false * Set MD033 to false * Set MD013 to false * Rearrange yml file * Update mdlint.sh and test * Test remove fix * Test with fix * Test with space * Fix summary indentation * Test mdlint.sh * Update mdlint.sh * Test * Update * Test fix * Test again * Fix * merge into check-code * Update scripts/mdlint.sh Co-authored-by: Mac L <mjladson@pm.me> * Update scripts/mdlint.sh Co-authored-by: Mac L <mjladson@pm.me> * Remove set -e * Add comment * Merge pull request #7 from chong-he/unstable Merge unstable to markdown branch * mdlint * Merge branch 'unstable' into markdown-linter * mdlint
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](./docker.md).
|
|
- [Building from source](./installation-source.md).
|
|
|
|
Additionally, there are two extra guides for specific uses:
|
|
|
|
- [Raspberry Pi 4 guide](./pi.md). (Archived)
|
|
- [Cross-compiling guide for developers](./cross-compiling.md).
|
|
|
|
There are also community-maintained installation methods:
|
|
|
|
- [Homebrew package](./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/)). 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
|