* Testnet validator
The lighthouse testnet is currently down. We expect to bring it up again in late-January or early-February. Thanks to all who participated in the testnet, we look forward to having your input again in the future.
Running Lighthouse validator is easy if you're familiar with the terminal. It runs on Linux, MacOS and Windows and we have a Docker work-flow.
There are two, different ways to install and start a Lighthouse validator:
docker-compose: this is the easiest method.
- Building from source: this is a little more involved, however it gives a more hands-on experience.
Once you have completed only one of these steps, move onto the next step.
eth1_deposit_data.rlp file from your validator
directory (created in Step 1) to submit your 3.2 Goerli-ETH
deposit using Metamask.
Hint: the method used in Step 1 will determine where this file is located.
Your validator deposit was submitted and this step is complete.
This deposit is using gETH (Goerli ETH) which has no real value. Don't ever send real ETH to our deposit contract!
Leave your beacon node and validator client running and you'll see logs as the beacon node keeps synced with the network and the validator client produces blocks and attestations.
It will take 4-8+ hours for the beacon chain to process and activate your validator, however you'll know you're active when the validator client starts successfully publishing attestations each slot:
Dec 03 08:49:40.053 INFO Successfully published attestation slot: 98, committee_index: 0, head_block: 0xa208…7fd5,
Although you'll produce an attestation each slot, it's less common to produce a block. Watch for the block production logs too:
Dec 03 08:49:36.225 INFO Successfully published block slot: 98, attestations: 2, deposits: 0, service: block
Don't forget to checkout the open-source block explorer for the Lighthouse testnet at lighthouse-testnet3.beaconcha.in.