status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
nimbus-eth2/CHANGELOG.md

2.8 KiB
Raw Blame History

Next

  • Avoid pcre dependency

2020-11-12 v0.6.2

A bugfix release addressing issues discovered in the Toledo network.

New additions:

  • Added an estimated syncing time to the beacon node status bar.

  • Added metadata for the upcoming Pyrmont network. This will be a short-lived network with parameters very closely resembling mainnet.

  • Switched to version 1.1 of the GossipSub protocol.

  • Added an JSON-RPC method setLogLevel for dynamically changing the log level of selected components at run-time.

Bug fixes:

  • Fixed a bug preventing the node from proposing blocks when connected to a web3 provider

  • Fixed an invalid "corrupted database" error message appearing on start-up

  • Fixed incorrectly set message-ids in gossip message causing other clients to penalise and potentially disconnect our nodes from the network.

  • Improved the behaviour of Nimbus when paired with a Geth node which is not fully synced.

2020-11-09 Hope (v0.6.0)

Nimbus eth2 0.6.0 was the first externally audited and stable release of our beacon node software. When compared to the 0.5x series, it features significant reductions in storage and memory requirements, a faster sync speed, and a plethora of usability and security enhancements across the board. Under normal network conditions, the delivery rate of attestations and block proposals is expected to be above 99%. Going forward, our release schedule will start to accelerate, with multiple new releases expected before the Eth2 mainnet launch.

Changelog highlights include:

  • Full support for the 1.0 Eth2 phase0 spec and the monitoring of the mainnet validator deposit contract.

  • LibP2P and GossipSub fixes which drastically improve the delivery of attestations and blocks (nearly 100% expected rate of delivery).

  • Fixes for all major resource leaks: you no longer need to restart your node to improve its performance.

  • Efficient caching and storage mechanisms: ensures our memory consumption remains comparatively low both during smooth and turbulent network conditions.

  • Several storage and networking optimisations leading to an order of magnitude improvement in beacon chain sync speed.

  • Audits to our codebase by ConsenSys Diligence, NCC Group and Trail of Bits. More than 60 of the security findings have already been addressed. The remaining items will be resolved before mainnet launch.

  • Support for pairing with a locally running Geth instance to allow for decentralised monitoring of the validator deposit contract.

  • An extensive user guide for managing the beacon node.

  • Slashing protection mechanisms + database.

  • Support for storing the validator signing keys in a separate process, isolated from the network, with a minimal attack surface.