mirror of
https://github.com/sigp/lighthouse.git
synced 2026-07-03 21:04:28 +00:00
Merge branch 'unstable' into validator-manager
This commit is contained in:
@@ -41,7 +41,7 @@ drastically and use the (recommended) default.
|
||||
|
||||
### NAT Traversal (Port Forwarding)
|
||||
|
||||
Lighthouse, by default, used port 9000 for both TCP and UDP. Lighthouse will
|
||||
Lighthouse, by default, uses port 9000 for both TCP and UDP. Lighthouse will
|
||||
still function if it is behind a NAT without any port mappings. Although
|
||||
Lighthouse still functions, we recommend that some mechanism is used to ensure
|
||||
that your Lighthouse node is publicly accessible. This will typically improve
|
||||
@@ -54,6 +54,16 @@ node will inform you of established routes in this case). If UPnP is not
|
||||
enabled, we recommend you manually set up port mappings to both of Lighthouse's
|
||||
TCP and UDP ports (9000 by default).
|
||||
|
||||
> Note: Lighthouse needs to advertise its publicly accessible ports in
|
||||
> order to inform its peers that it is contactable and how to connect to it.
|
||||
> Lighthouse has an automated way of doing this for the UDP port. This means
|
||||
> Lighthouse can detect its external UDP port. There is no such mechanism for the
|
||||
> TCP port. As such, we assume that the external UDP and external TCP port is the
|
||||
> same (i.e external 5050 UDP/TCP mapping to internal 9000 is fine). If you are setting up differing external UDP and TCP ports, you should
|
||||
> explicitly specify them using the `--enr-tcp-port` and `--enr-udp-port` as
|
||||
> explained in the following section.
|
||||
|
||||
|
||||
### ENR Configuration
|
||||
|
||||
Lighthouse has a number of CLI parameters for constructing and modifying the
|
||||
|
||||
@@ -128,8 +128,9 @@ same `datadir` as a previous network. I.e if you have been running the
|
||||
`datadir` (the `datadir` is also printed out in the beacon node's logs on
|
||||
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 [here](./advanced_networking.md#nat-traversal-port-forwarding).
|
||||
If you find yourself with a low peer count and it's not reaching the target you
|
||||
expect. Try setting up the correct port forwards as described
|
||||
[here](./advanced_networking.md#nat-traversal-port-forwarding).
|
||||
|
||||
### What should I do if I lose my slashing protection database?
|
||||
|
||||
|
||||
@@ -1,13 +1,16 @@
|
||||
# Frequently Asked Questions
|
||||
|
||||
## 1. Where can I find my API token?
|
||||
## 1. Are there any requirements to run Siren?
|
||||
Yes, Siren requires Lighthouse v3.5.1 or higher to function properly. These releases can be found on the [releases](https://github.com/sigp/lighthouse/releases) page of the Lighthouse repository.
|
||||
|
||||
## 2. Where can I find my API token?
|
||||
The required Api token may be found in the default data directory of the validator client. For more information please refer to the lighthouse ui configuration [`api token section`](./ui-configuration.md#api-token).
|
||||
|
||||
## 2. How do I fix the Node Network Errors?
|
||||
## 3. How do I fix the Node Network Errors?
|
||||
If you recieve a red notification with a BEACON or VALIDATOR NODE NETWORK ERROR you can refer to the lighthouse ui configuration and [`connecting to clients section`](./ui-configuration.md#connecting-to-the-clients).
|
||||
|
||||
## 3. How do I change my Beacon or Validator address after logging in?
|
||||
## 4. How do I change my Beacon or Validator address after logging in?
|
||||
Once you have successfully arrived to the main dashboard, use the sidebar to access the settings view. In the top right hand corner there is a `Configurtion` action button that will redirect you back to the configuration screen where you can make appropriate changes.
|
||||
|
||||
## 4. Why doesn't my validator balance graph show any data?
|
||||
## 5. Why doesn't my validator balance graph show any data?
|
||||
If your graph is not showing data, it usually means your validator node is still caching data. The application must wait at least 3 epochs before it can render any graphical visualizations. This could take up to 20min.
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
|
||||
Siren runs on Linux, MacOS and Windows.
|
||||
|
||||
## Version Requirement
|
||||
The Siren app requires Lighthouse v3.5.1 or higher to function properly. These versions can be found on the [releases](https://github.com/sigp/lighthouse/releases) page of the Lighthouse repository.
|
||||
|
||||
## Pre-Built Electron Packages
|
||||
|
||||
@@ -16,7 +18,7 @@ Simply download the package specific to your operating system and run it.
|
||||
|
||||
### Requirements
|
||||
|
||||
Building from source requires `Node v18` and `yarn`.
|
||||
Building from source requires `Node v18` and `yarn`.
|
||||
|
||||
### Building From Source
|
||||
|
||||
|
||||
Reference in New Issue
Block a user