Merge remote-tracking branch 'origin/stable' into unstable

This commit is contained in:
Jacek Sieka 2021-03-15 17:29:43 +01:00
commit eb830c7968
No known key found for this signature in database
GPG Key ID: A1B09461ABB656B8
4 changed files with 35 additions and 14 deletions

View File

@ -1,32 +1,53 @@
2021-03-09 v1.0.9
=================
2021-03-10 v1.0.10
==================
This release includes important security fixes introduced in third-party
packages and brings further performance improvements.
This release contains important security and performance improvements.
-----
**We've upgraded:**
**Upgraded:**
* The BLST library is now version 0.3.3:
* We're now running version 0.3.3 of the BLST library:
https://github.com/supranational/blst/releases/tag/v0.3.3
* We've switched to a more recent version of BearSSL, featuring a more
up-to-date list of trusted root certificates.
* We've switched to a more recent version of BearSSL
(this version features a more up-to-date list of trusted root certificates)
* The Eth2 spec has been upgraded to 1.0.1.
* We're now consistent with the v1.0.1 Eth2 spec
**We've fixed:**
* A frequent crash occurring on certain hardware configurations after
building Nimbus from source.
* Long processing delays triggered by the reception of attestations that
reference already pruned states.
* LibP2P peer management issue leading to accumulation of inactive
* LibP2P peer management issue which led to an accumulation of inactive
connections.
* A false-positive in doppelganger detection triggered by rebroadcasted
older attestations arriving with a significant delay.
**New features**:
* A new improved format of the slashing protection database:
- Significantly reduces the disk load with a large number of validators (1000+).
- Makes it possible to enhance our doppelganger detection in the future such that
waiting for 2 epochs before attesting is not necessary.
To ensure smooth upgrade and emergency rollback between older and future Nimbus
versions, v1.0.10 will keep track of your attestation in both the old and the
new format. The extra load should be negligible for home stakers.
2021-03-09 v1.0.9
=================
This version was an internal release candidate build for the 1.0.10 release.
2021-02-22 v1.0.8
=================

View File

@ -128,7 +128,7 @@ type
slashingDbKind* {.
hidden
defaultValue: SlashingDbKind.v2
defaultValue: SlashingDbKind.both
desc: "The slashing DB flavour to use (v1, v2 or both)"
name: "slashing-db-kind" }: SlashingDbKind

View File

@ -9,13 +9,13 @@ when not defined(nimscript):
const
versionMajor* = 1
versionMinor* = 0
versionBuild* = 9
versionBuild* = 10
versionBlob* = "stateofus" # Single word - ends up in the default graffitti
useInsecureFeatures* = defined(insecure)
gitRevision* = strip(staticExec("git rev-parse --short HEAD"))
gitRevision* = strip(staticExec("git rev-parse --short HEAD"))[0..5]
nimBanner* = staticExec("nim --version | grep -v Compiled")

2
vendor/news vendored

@ -1 +1 @@
Subproject commit 37055371ecd222aff04bcb69ce68374c692e398c
Subproject commit 363dd4ca77582310f55d98569b9fd2a35678f17d