v1.0.10

This release contains important security and performance improvements.

Note: You may have noticed that we've skipped a release version. While we did push v1.0.9 to the stable branch, we didn't make an official release or publish any binaries for it. v1.0.10 differs from v1.0.9 only in that it keep tracks of your attestations in both the old and the new database formats. This ensures you are able to safely rollback should you need to do so. If you're already running v1.0.9, upgrading to v1.0.10 is safe (we recommend you upgrade at your convenience); in order to be extra safe, please do not switch off doppelganger detection (it should be on by default).

---

Upgraded:

• 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
  (this version features a more up-to-date list of trusted root certificates)

• We're now consistent with the v1.0.1 Eth2 spec (which allows for Eth1 withdrawal credentials -- ethereum/consensus-specs#2149)

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 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 ---
    waiting for 2 epochs before attesting on launch will no longer be necessary.

  • To ensure a smooth upgrade and the possibility for emergency rollbacks between older and future Nimbus versions, v1.0.10 will keep track of your attestations in both the old and the new database formats. This extra load should be negligible for home stakers.

• Automatic configuration of external IP address when a public IP address is used or when a public IP address is provided as a listener address. This is active by default (--nat:any) and with the option --nat:none. It is deactivated when you pass in --nat:upnp, --nat:pmp or --nat:extip:<ip address>. In practice this means that if you run your node and are not behind NAT (e.g. cloud setups without docker), you should no longer need to provide --nat:extip:<ip address>