Running a Lighthouse validator on the Altona multi-client testnet is easy if you're familiar with the terminal.
Lighthouse runs on Linux, MacOS and Windows and has a Docker work-flow to make things as simple as possible.
If this is your first time using Metamask and/or interacting with an ethereum test network, we recommend going through the beginning of this guide first (up to the Signing your first transaction with MetaMask section).
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've completed either one of these steps, you can move onto the next step.
eth1_deposit_data.rlp file from your validator
directory (created in the previous step) to submit your 3.2 Goerli-ETH
deposit using Metamask.
Note that the method you used in step 1 will determine where this file is located.
Your validator deposit was submitted and this step is complete.
Please refresh to reupload.
This deposit is made using gETH (Goerli ETH) which has no real value. Please 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 stays synced with the network while 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.