The Bee team is excited to announce the latest release which mostly consists of minor fixes to chunk syncing and improved uploading experience.
The important news is uploads with mutable batches (which are the most common type of batches) are no longer terminated when max utilization of the batch is reached, whereby newer chunks that belong to the batch will simply replace older chunks in the network.
Hardening
- The node is interruptible while it's waiting for the NAT initialization. (#3688)
- Batch synchronization can now be gracefully suspended on interrupt signal. (#3671)
- Removed old overlay mining logic from the codebase. (#3684)
- Added deferred header to allowed CORs headers. (#3669)
New features
- Uploads with mutable batches are not stopped when max utilization is reached. (#3685)
Bug Fixes
- Fixed the depthmonitor to track active syncing background jobs instead of chunks per second when choosing to reduce the syncing/storage radius. (#3680)
- Lowered the minimum required reserve size to maintain a stable storage radius from 50% of the capacity to 40%. (#3682)
For a full PR rundown please consult the v1.11.0 milestone.