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

Update docs for testnet3 (#773)

Browse Source 
* Start docker docs

* Add progress

* Update docker.md

* Add note about geth syncing

* Fix env to use geth

* Update docs

* Remove sigp goerli node

* Change text about eth1 syncing

* Address comments from @pscott

* Add links to beaconcha.in

* Add instructions for starting an eth1 node

* Fix typo

* Re-organise Syncing log
This commit is contained in:
Paul Hauner
2020-01-10 13:56:48 +11:00
committed by GitHub
parent efd73230cf
commit 698af6d7ec
8 changed files with 297 additions and 130 deletions
Download Patch File Download Diff File Expand all files Collapse all files

138
book/src/become-a-validator.md
View File

@@ -1,135 +1,33 @@
# Become an Ethereum 2.0 Validator*
---
**The lighthouse testnet is currently down, we expect to raise a new one soon.
See [Lighthouse Update #20](https://lighthouse.sigmaprime.io/update-20.html)
for more information.**
---
_* Testnet validator_
Running Lighthouse validator is easy if you're familiar with the terminal. It
runs on Linux, MacOS and Windows.
runs on Linux, MacOS and Windows and we have a Docker work-flow.
Before you start, you'll need [Metamask](https://metamask.io/) and 3.2 gETH
(Goerli ETH). We recommend the [mudit.blog
faucet](https://faucet.goerli.mudit.blog/) for those familiar with Goerli, or
[goerli.net](https://goerli.net/) for an overview of the testnet.
### 1. Download and install Lighthouse
## 1. Install and start Lighthouse
If you already have Rust installed, you can install Lighthouse with the
following three commands:
There are two, different ways to install and start a Lighthouse validator:
- `$ git clone https://github.com/sigp/lighthouse.git`
- `$ cd lighthouse`
- `$ make`
- [Using `docker-compose`](./become-a-validator-docker.md): this is the easiest method.
- [Building from source](./become-a-validator-source.md): this is a little more involved, however it
gives a more hands-on experience.
You've completed this step when you can run `$ lighthouse --help` and see the
help menu.
Once you have completed **only one** of these steps, move onto the next step.
> - If you're not familiar with Rust or you'd like more detailed instructions, see
> the [Installation Guide](./installation.md).
> - The [Docker Guide](./docker.md) is great if you have Docker installed and would
> like to avoid installing Rust.
### 2. Start your Beacon Node
The beacon node is the core component of Eth2, it connects to other peers over
the Internet and maintains a view of the chain.
Start your beacon node with:
```bash
$ lighthouse beacon --eth1 --http
```
Your beacon node has started syncing when you see the following (truncated)
log:
```
Dec 09 12:57:18.026 INFO Syncing distance: 16837 slots (2 days 8 hrs), ...
```
Don't be overly concerned about the "distance" because "est_time" for syncing will be much lower.
It has finished syncing once you see the following (truncated) log:
```
Dec 09 12:27:06.010 INFO Synced slot: 16835, ...
```
> - The `--http` flag enables the HTTP API for the validator client.
> - The `--eth1` flag tells the beacon node that it should sync with an Ethereum
> 1 node (e.g., Geth). This is only required if you wish to run a validator.
> - We are hosting a public Goerli archive node and have set this as the
> default, but you can specify your own Eth1 node using the `--eth1-endpoint`
> flag. Presently we require the node to be a full archive node, but we're
> working to [fix](https://github.com/sigp/lighthouse/issues/637) this.
### 3. Generate your validator key
Generate new validator BLS keypairs using:
```shell
$ lighthouse account validator new random
```
You've completed this step when you see the equivalent line:
```
Dec 02 21:42:01.337 INFO Generated validator directories count: 1, base_path: "/home/karl/.lighthouse/validators"
```
> - This will generate a new _validator directory_ in the `.lighthouse/validators`
> directory. Your validator directory will be identified by it's public key,
> which looks something like `0xc483de...`. You'll need to find this directory
> for the next step.
> - These keys are good enough for the Lighthouse testnet, however they shouldn't
> be considered secure until we've undergone a security audit (planned Jan
> 2020).
### 4. Start your validator client
For security reasons, the validator client runs separately to the beacon node.
The validator client stores private keys and signs messages generated by the
beacon node.
You'll need both your beacon node _and_ validator client running if you want to
stake.
Start the validator client with:
```bash
$ lighthouse validator
```
The validator client is running and has found your validator keys from step 3
when you see the following log:
```
Dec 09 13:08:59.171 INFO Loaded validator keypair store voting_validators: 1
Dec 09 13:09:09.000 INFO Awaiting activation slot: 17787, ...
```
If your beacon node hasn't finished syncing yet, you'll see some `ERRO`
messages indicating that your node isn't synced yet. It is safest to wait for
your node to sync before moving onto the next step, otherwise your validator
may activate before you're able to produce blocks and attestations. However, it
generally takes 4-8+ hours after deposit for a validator to become active. If
your `est_time` is less than 4 hours, you _should_ be fine to just move to the
next step. After all, this is a testnet and you're only risking Goerli ETH.
### 5. Submit your deposit
## 2. Submit your deposit to Goerli
<div class="form-signin" id="uploadDiv">
<p>Upload the <code>eth1_deposit_data.rlp</code> file from your validator
directory (created in step 3) to submit your 3.2 Goerli-ETH
directory (created in Step 1) to submit your 3.2 Goerli-ETH
deposit using Metamask.</p>
<p>Hint: it's generally in the <code>$HOME/.lighthouse/validators/0x...</code> directory</p>
<p>Hint: the method used in Step 1 will determine where this file is
located.</p>
<input id="fileInput" type="file" style="display: none">
<button id="uploadButton" class="btn btn-lg btn-primary btn-block"
type="submit">Upload and Submit Deposit</button>
@@ -150,15 +48,15 @@ next step. After all, this is a testnet and you're only risking Goerli ETH.
> This deposit is using gETH (Goerli ETH) which has no real value. Don't ever
> send _real_ ETH to our deposit contract!
## Next steps
## 3. Leave Lighthouse running
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 some time (minutes to 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:
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,
@@ -175,11 +73,13 @@ If you see any `ERRO` (error) logs, please reach out on
[Discord](https://discord.gg/cyAszAh) or [create an
issue](https://github.com/sigp/lighthouse/issues/new).
Don't forget to checkout the open-source block explorer for the Lighthouse
testnet at
[lighthouse-testnet3.beaconcha.in](https://lighthouse-testnet3.beaconcha.in/).
Happy staking!
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.1/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
<script charset="utf-8"