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

Update validator guide for mainnet (#1951)

Browse Source 
## Issue Addressed

NA

## Proposed Changes

Updates the validator guide to provide instructions for mainnet users.

## Additional Info

- ~~Blocked on #1751~~
This commit is contained in:
Paul Hauner
2020-11-24 04:42:17 +00:00
parent a171fb8843
commit e504645767
19 changed files with 304 additions and 253 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
book/src/faq.md
View File

@@ -86,10 +86,10 @@ It is not strictly required to open any ports for Lighthouse to connect and
participate in the network. Lighthouse should work out-of-the-box. However, if
your node is not publicly accessible (you are behind a NAT or router that has
not been configured to allow access to Lighthouse ports) you will only be able
to reach peers who have a set up that is publicly accessible.
to reach peers who have a set up that is publicly accessible.
There are a number of undesired consequences of not making your Lighthouse node
publicly accessible.
publicly accessible.
Firstly, it will make it more difficult for your node to find peers, as your
node will not be added to the global DHT and other peers will not be able
@@ -100,16 +100,16 @@ subscribing peers. The reason being, that peers that have correct port
forwarding (publicly accessible) are in higher demand than regular peers as other nodes behind NAT's
will also be looking for these peers.
Finally, not making your node publicly accessible degrades the overall network, making it more difficult for other
peers to join and degrades the overall connectivity of the global network.
peers to join and degrades the overall connectivity of the global network.
For these reasons, we recommend that you make your node publicly accessible.
For these reasons, we recommend that you make your node publicly accessible.
Lighthouse supports UPnP. If you are behind a NAT with a router that supports
UPnP you can simply ensure UPnP is enabled (Lighthouse will inform you in its
initial logs if a route has been established). You can also manually set up
port mappings in your router to your local Lighthouse instance. By default,
Lighthouse uses port 9000 for both TCP and UDP. Opening both these ports will
make your Lighthouse node maximally contactable.
make your Lighthouse node maximally contactable.
#### 4. I have a low peer count and it is not increasing
@@ -118,9 +118,9 @@ testnet configuration settings. Ensure that the network you wish to connect to
is correct (the beacon node outputs the network it is connecting to in the
initial boot-up log lines). On top of this, ensure that you are not using the
same `datadir` as a previous network. I.e if you have been running the
`medalla` testnet and are now trying to join a new testnet but using the same
`pyrmont` testnet and are now trying to join a new testnet but using the same
`datadir` (the `datadir` is also printed out in the beacon node's logs on
boot-up).
boot-up).
If you find yourself with a low peer count and is not reaching the target you
expect. Try setting up the correct port forwards as described in `3.` above.
expect. Try setting up the correct port forwards as described in `3.` above.