Consensus Clients: Lighthouse

Currently Lighthouse is used by >33% of the network.

Client diversity is extremely important for the network health of Ethereum: A bug in a client with a share of over 33% can cause Ethereum to go offline. If the client has a supermajority (>66%), a bug could cause the chain to incorrectly split, potentially leading to slashing.

If at all possible, consider running another client at this time to help protect yourself and the network.

Lighthouse

A consensus client with a heavy focus on speed and security. Built by Sigma Prime, an information security and software engineering firm who have funded Lighthouse along with the Ethereum Foundation, Consensys, and private individuals.More on Lighthouse and Sigma Prime

Language information

Lighthouse is built in Rust and offered under an Apache 2.0 License.

Become a validator with Lighthouse

Lighthouse installation documentation

Key management

Lighthouse has dedicated tooling to make the transfer from the Launchpad as easy as possible.Specifically, when starting your lighthouse validator client, you can point it at the directory with your keystores and it will import your keystores and interactively ask for your password(s). If you do not supply a password, lighthouse will ask for it again every time it starts up.
lighthouse account validator import --directory staking-deposit-cli/validator_keys
Once the process is complete, you should see the following:
Successfully moved keystore.Successfully updated validator_definitions.yml.Successfully imported 1 validators.

Running the validator client

Now that the keys are imported, all that is left to do (assuming your beacon node is already running) is to run the validator client.
lighthouse vc

Troubleshooting

Importing from Launchpad documentation

Documentation

Documentation on running Lighthouse