gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-03-23 23:04:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

Book modifications to include testnet param (#1418)

Browse Source 
## Issue Addressed

N/A

## Proposed Changes

Update the lighthouse book to accommodate the new `--testnet` CLI param. 

## Additional Info
This commit is contained in:
Age Manning
2020-07-31 02:14:50 +00:00
parent a37e75f44b
commit 2ede9caaa6
6 changed files with 46 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
book/src/become-a-validator-source.md
View File

@@ -45,9 +45,14 @@ the internet and maintains a view of the chain.
Start your beacon node with:
```bash
lighthouse beacon --eth1 --http
lighthouse --testnet medalla beacon --eth1 --http
```
> The `--testnet` parameter is optional. Omitting it will default to the
> current public testnet. Set the value to the testnet you wish to run on.
> Current values are either `altona` or `medalla`. This is true for all the
> following commands in this document.
>Note: the `--http` flag enables the HTTP API for the validator client. And the `--eth1` flag tells the beacon node that it should sync with an Ethereum1 node (e.g. Geth). These flags are only required if you wish to run a validator.
@@ -81,7 +86,7 @@ validator](./validator-create.md). A two-step example follows:
Create a wallet with:
```bash
lighthouse account wallet create --name my-validators --passphrase-file my-validators.pass
lighthouse --testnet medalla account wallet create --name my-validators --passphrase-file my-validators.pass
```
The output will look like this:
@@ -117,7 +122,7 @@ used to restore your validator if there is a data loss.
Create a validator from the wallet with:
```bash
lighthouse account validator create --wallet-name my-validators --wallet-passphrase my-validators.pass --count 1
lighthouse --testnet medalla account validator create --wallet-name my-validators --wallet-passphrase my-validators.pass --count 1
```
The output will look like this:
@@ -140,6 +145,12 @@ information.
## 5. Start your validator client
> Note: If you are participating in the genesis of a network (the network has
> not launched yet) you should skip this step and re-run this step two days before
> the launch of the network. The beacon node does not expose its HTTP API until
> the genesis of the network is known (approx 2 days before the network
> launches).
Since the validator client stores private keys and signs messages generated by the beacon node, for security reasons it runs separately from it.
You'll need both your beacon node _and_ validator client running if you want to
@@ -148,7 +159,7 @@ stake.
Start the validator client with:
```bash
lighthouse validator --auto-register
lighthouse --testnet medalla validator --auto-register
```
The `--auto-register` flag registers your signing key with the slashing protection database, which
@@ -164,7 +175,7 @@ Dec 09 13:09:09.000 INFO Awaiting activation slot: 17787, ..
```
To find an estimate for how long your beacon node will take to finish syncing, lookout for the following logs:
To find an estimate for how long your beacon node will take to finish syncing, lookout for the following logs:
```bash
beacon_node_1 | Mar 16 11:33:53.979 INFO Syncing
@@ -186,7 +197,7 @@ However, since it generally takes somewhere between [4 and 8 hours](./faq.md) af
## Installation complete!
In the [next step](become-a-validator.html#2-submit-your-deposit-to-goerli) you'll need to upload your validator's deposit data. This data is stored in a file called `eth1_deposit_data.rlp`.
In the [next step](become-a-validator.html#2-submit-your-deposit-to-goerli) you'll need to upload your validator's deposit data. This data is stored in a file called `eth1_deposit_data.rlp`.
You'll find it in `/home/.lighthouse/validators` -- in the sub-directory that corresponds to your validator's public key.