|
| 1 | +2020-12-03 v1.0.2 |
| 2 | +================= |
| 3 | + |
| 4 | +A release that fixes an issue regarding the occasional missed block proposal. |
| 5 | + |
| 6 | +Proposing a block is arguably the most important duty you have as a validator. |
| 7 | +So it's important you update at your earliest convenience. |
| 8 | + |
| 9 | +----- |
| 10 | + |
| 11 | +**New additions:** |
| 12 | + |
| 13 | +* 8 new JSON-RPC calls that bring us to feature parity with the official |
| 14 | + beacon node API. |
| 15 | + |
| 16 | +**We've fixed:** |
| 17 | + |
| 18 | +* A deposit merkle proofs generation issue which occasionally resulting |
| 19 | + in missed block proposals shortly after a new Eth1 head was selected. |
| 20 | + |
| 21 | +* Slow status bar updates in the absense of logging messages. |
| 22 | + |
| 23 | + |
1 | 24 | 2020-12-02 v1.0.1 |
2 | 25 | ================= |
3 | 26 |
|
4 | | -A point release fixing a number of issues reported after the Mainnet launch. |
| 27 | +A release with a number of important fixes and optimisations. |
5 | 28 |
|
6 | | -New additions: |
| 29 | +**Please update** at your earliest convenience. |
7 | 30 |
|
8 | | -* Better pacing of our Eth1 syncing requests less likely to go over the |
9 | | - maximum allowed burst rates with the Infura free plans. More resiliency |
10 | | - in case of errors. |
| 31 | +In order to minimise downtime, we recommend updating and rebuilding |
| 32 | +the beacon node **before restarting.** |
11 | 33 |
|
12 | | -We've fixed: |
| 34 | +----- |
| 35 | + |
| 36 | +**New additions:** |
| 37 | + |
| 38 | +* More conservative Eth1 syncing requests to reduce the likelihood of |
| 39 | + going over the maximum allowed burst rates under the Infura free plan |
| 40 | + (predominantly aimed at those running Nimbus on resource-restricted |
| 41 | + device like Raspberry Pi's) + more resiliency in case of errors. |
| 42 | + |
| 43 | +**We've fixed:** |
13 | 44 |
|
14 | | -* A crash reported by multiple users with the following error message: |
15 | | - "Only one concurrent read allowed". |
| 45 | +* A "Only one concurrent read allowed" crash reported by multiple users. |
16 | 46 |
|
17 | 47 | * An error in the default configuration preventing the node from discovering |
18 | | - peers on mainnet unless `--network=mainnet` was explicitly specified on the |
19 | | - command-line. |
| 48 | + peers on mainnet unless the `--network=mainnet` flag was passed. Please note |
| 49 | + that this not affect users starting their node with the `./run-mainnet-beacon-node` |
| 50 | + command. |
20 | 51 |
|
21 | | -* An incorrect value for the fractional part of your ETH balance in the |
22 | | - Nimbus status bar. |
| 52 | +* The fractional part of the ETH balance in the Nimbus status bar |
| 53 | + (the value displayed should now be correct). |
23 | 54 |
|
24 | | -* An issue that may cause the Eth1 syncing process to get stuck before |
25 | | - reaching the head of the chain. |
| 55 | +* An issue that occasionally caused the Eth1 syncing process to get stuck |
| 56 | + before reaching the head of the chain. |
26 | 57 |
|
27 | 58 | * Unnecessary network traffic related to GossipSub `IHAVE`. |
28 | 59 |
|
29 | | -* Incorrect gossipsub pruning which could result in messages getting lost. |
| 60 | +* Incorrect gossipsub pruning which occasionally resulted in messages |
| 61 | + getting lost. |
30 | 62 |
|
31 | | -* An issue where an excessively long graffiti string could cause a crash |
32 | | - upon startup. |
| 63 | +* An issue where an excessively long graffiti string could cause a crash on |
| 64 | + startup. |
33 | 65 |
|
34 | | -* A Linux-only issue causing the `deposits import` command to ignore its |
35 | | - supplied arguments. |
| 66 | +* A Linux-only issue that resulted in the `deposits import` command ignoring |
| 67 | + its supplied arguments. |
36 | 68 |
|
37 | 69 |
|
38 | 70 | 2020-11-29 v1.0.0-stateofus |
|
0 commit comments