Nimbus
v23.1.0 was a
low-urgency upgrade,
introducing support for on-the-fly database pruning making the storage
requirements of Nimbus much more predictable on long-term time scales.
When pruning is enabled, a typical beacon node expected to consume
around 60 to 70 GB of storage. To take advantage of the new
functionality without facing any downtime, users are advised to sync a
fresh node through trusted node sync which now features a quicker
history backfilling implementation.
See the full release notes for more:
https://github.com/status-im/nimbus-eth2/releases/tag/v23.1.0Nimbus
v23.1.1 is a
high-urgency hotfix for users who have already enabled block history pruning after upgrading to
v23.1.0. It fixes an issue where the client may fail to start after the database has been pruned.
https://github.com/status-im/nimbus-eth2/releases/tag/v23.1.1Happy Staking!