Book update post launch (#2131)
* fix systemd guide typo * Update update flow * update Pi guide: sync speed estimates * FAQ: wait two epochs to prevent slashing * Add to syncing logs * Pi guide: add link to USB3.0 issue and link to recommended workaround * Pi guide edits
This commit is contained in:
Sacha Saint-Leger
GitHub
parent
4feb0a308e
commit
3eab1f77aa
|
|
@ -45,7 +45,7 @@ Description=Nimbus beacon node
|
|||
|
||||
[Service]
|
||||
WorkingDirectory=<BASE-DIRECTORY>
|
||||
ExecStart==<BASE-DIRECTORY>/build/nimbus_beacon_node \
|
||||
ExecStart=<BASE-DIRECTORY>/build/nimbus_beacon_node \
|
||||
--non-interactive \
|
||||
--network=pyrmont \
|
||||
--data-dir=build/data/shared_pyrmont_0 \
|
||||
|
|
|
|||
|
|
@ -50,6 +50,10 @@ Limiting the maximum stake to 32 ETH encourages decentralization of power as it
|
|||
|
||||
Yes but, under normal conditions, you will lose an amount of ETH roughly equivalent to the amount of ETH you would have gained in that period. In other words, if you stood to earn ≈0.01 ETH, you would instead be penalised ≈0.01 ETH.
|
||||
|
||||
## I want to switch my validator keys to another machine, how long do I need to wait to avoid getting slashed?
|
||||
|
||||
We recommend waiting 2 epochs (around 15 minutes), before restarting Nimbus on a different machine.
|
||||
|
||||
## When should I top up my validator's balance?
|
||||
|
||||
The answer to this question very much depends on how much ETH you have at your disposal.
|
||||
|
|
|
|||
|
|
@ -8,7 +8,15 @@ To update to the latest version, run:
|
|||
git pull && make update
|
||||
```
|
||||
|
||||
Then [rebuild the beacon node.](./build.md)
|
||||
Followed by:
|
||||
|
||||
```
|
||||
make nimbus_beacon_node
|
||||
```
|
||||
|
||||
to [rebuild the beacon node](./build.md).
|
||||
|
||||
> ⚠️ In order to minimise downtime, we recommend updating and rebuilding the beacon node before restarting.
|
||||
|
||||
> **Note:** If your beacon node is already running, you'll need to disconnect and reconnect for the changes to take effect.
|
||||
|
||||
|
|
|
|||
|
|
@ -377,19 +377,30 @@ Enter your own secure websocket (`wss`) [Infura endpoint](./infura-guide.md).
|
|||
If you look near the top of the logs printed to your console, you should see confirmation that your beacon node has started, with your local validator attached:
|
||||
|
||||
```
|
||||
INF 2020-10-07 17:04:09.213+02:00 Initializing networking topics="networking" tid=11688398 file=eth2_network.nim:1335 hostAddress=/ip4/0.0.0.0/tcp/9000 network_public_key=0802122102defb020c8e47dd8f5da89f51ed6c3998aaa0dd59eeb2784e29d47fdbdab69235 announcedAddresses=@[/ip4/195.177.101.93/tcp/9000]
|
||||
WRN 2020-10-07 17:04:09.215+02:00 Ignoring invalid bootstrap address tid=11688398 file=eth2_discovery.nim:45 bootstrapAddr= reason="an empty string is not a valid bootstrap node"
|
||||
NOT 2020-10-07 17:04:09.231+02:00 Local validators attached topics="beacval" tid=11688398 file=validator_duties.nim:65 count=0
|
||||
NOT 2020-10-07 17:04:09.231+02:00 Starting beacon node topics="beacnde" tid=11688398 file=nimbus_beacon_node.nim:923 version="0.5.0 (1dec860b)" nim="Nim Compiler Version 1.2.6 [MacOSX: amd64] (bf320ed1)" timeSinceFinalization=0ns head=0814b036:0 finalizedHead=0814b036:0 SLOTS_PER_EPOCH=32 SECONDS_PER_SLOT=12 SPEC_VERSION=0.12.3 dataDir=build/data/shared_pyrmont_0
|
||||
INF 2020-12-01 11:25:33.487+01:00 Launching beacon node
|
||||
...
|
||||
INF 2020-12-01 11:25:34.556+01:00 Loading block dag from database topics="beacnde" tid=19985314 file=nimbus_beacon_node.nim:198 path=build/data/shared_pyrmont_0/db
|
||||
INF 2020-12-01 11:25:35.921+01:00 Block dag initialized
|
||||
INF 2020-12-01 11:25:37.073+01:00 Generating new networking key
|
||||
...
|
||||
NOT 2020-12-01 11:25:45.267+00:00 Local validator attached tid=22009 file=validator_pool.nim:33 pubKey=95e3cbe88c71ab2d0e3053b7b12ead329a37e9fb8358bdb4e56251993ab68e46b9f9fa61035fe4cf2abf4c07dfad6c45 validator=95e3cbe8
|
||||
...
|
||||
NOT 2020-12-01 11:25:59.512+00:00 Eth1 sync progress topics="eth1" tid=21914 file=eth1_monitor.nim:705 blockNumber=3836397 depositsProcessed=106147
|
||||
NOT 2020-12-01 11:26:02.574+00:00 Eth1 sync progress topics="eth1" tid=21914 file=eth1_monitor.nim:705 blockNumber=3841412 depositsProcessed=106391
|
||||
...
|
||||
INF 2020-12-01 11:26:31.000+00:00 Slot start topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:505 lastSlot=96566 scheduledSlot=96567 beaconTime=1w6d9h53m24s944us774ns peers=7 head=b54486c4:96563 headEpoch=3017 finalized=2f5d12e4:96479 finalizedEpoch=3014
|
||||
INF 2020-12-01 11:26:36.285+00:00 Slot end topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:593 slot=96567 nextSlot=96568 head=b54486c4:96563 headEpoch=3017 finalizedHead=2f5d12e4:96479 finalizedEpoch=3014
|
||||
```
|
||||
|
||||
To keep track of your syncing progress, have a look at the output at the very bottom of the terminal window in which your validator is running. You should see something like:
|
||||
|
||||
```
|
||||
peers: 35 ❯ finalized: ada7228a:8765 ❯ head: b2fe11cd:8767:2 ❯ time: 9900:7 (316807) ❯ sync: wPwwwwwDwwDPwPPPwwww:7:4.0627 (280512)
|
||||
peers: 15 ❯ finalized: ada7228a:8765 ❯ head: b2fe11cd:8767:2 ❯ time: 9900:7 (316807) ❯ sync: wPwwwwwDwwDPwPPPwwww:7:1.2313:1.0627:12h01m(280512)
|
||||
```
|
||||
|
||||
Keep an eye on the number of peers your currently connected to (in the above case that's `35`), as well as your [sync progress](./keep-an-eye.md#syncing-progress).
|
||||
Keep an eye on the number of peers your currently connected to (in the above case that's `15`), as well as your [sync progress](./keep-an-eye.md#syncing-progress).
|
||||
|
||||
> **Note:** 15 - 20 peers and an average sync speed of **0.5 - 1.0** blocks per second is normal on `Pyrmont` with a Pi. If you're sync speed is much slower than this, the root of the problem may be your USB3.0 to SSD adapter. See [this post](https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245931) for a recommended workaround.
|
||||
|
||||
### 20. End ssh session and logout
|
||||
|
||||
|
|
|
|||
|
|
@ -49,11 +49,17 @@ ws://127.0.0.1:8546
|
|||
Once you've entered your Web3 provider URL, you should see the following output:
|
||||
|
||||
```
|
||||
INF 2020-11-18 11:25:33.487+01:00 Launching beacon node
|
||||
INF 2020-12-01 11:25:33.487+01:00 Launching beacon node
|
||||
...
|
||||
INF 2020-11-18 11:25:34.556+01:00 Loading block dag from database topics="beacnde" tid=19985314 file=nimbus_beacon_node.nim:198 path=build/data/shared_pyrmont_0/db
|
||||
INF 2020-11-18 11:25:35.921+01:00 Block dag initialized
|
||||
INF 2020-11-18 11:25:37.073+01:00 Generating new networking key
|
||||
INF 2020-12-01 11:25:34.556+01:00 Loading block dag from database topics="beacnde" tid=19985314 file=nimbus_beacon_node.nim:198 path=build/data/shared_pyrmont_0/db
|
||||
INF 2020-12-01 11:25:35.921+01:00 Block dag initialized
|
||||
INF 2020-12-01 11:25:37.073+01:00 Generating new networking key
|
||||
...
|
||||
NOT 2020-12-01 11:25:59.512+00:00 Eth1 sync progress topics="eth1" tid=21914 file=eth1_monitor.nim:705 blockNumber=3836397 depositsProcessed=106147
|
||||
NOT 2020-12-01 11:26:02.574+00:00 Eth1 sync progress topics="eth1" tid=21914 file=eth1_monitor.nim:705 blockNumber=3841412 depositsProcessed=106391
|
||||
...
|
||||
INF 2020-12-01 11:26:31.000+00:00 Slot start topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:505 lastSlot=96566 scheduledSlot=96567 beaconTime=1w6d9h53m24s944us774ns peers=7 head=b54486c4:96563 headEpoch=3017 finalized=2f5d12e4:96479 finalizedEpoch=3014
|
||||
INF 2020-12-01 11:26:36.285+00:00 Slot end topics="beacnde" tid=21815 file=nimbus_beacon_node.nim:593 slot=96567 nextSlot=96568 head=b54486c4:96563 headEpoch=3017 finalizedHead=2f5d12e4:96479 finalizedEpoch=3014
|
||||
...
|
||||
```
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue