The Bee team is excited to announce the latest release which brings the storage incentives a step closer. The first phase of the implementation brings the need to upgrade the postage stamp contract. This is going to be a breaking release, meaning that the previous versions of Bee will not be able to connect to the new version of Bee, so node operators will need to upgrade as soon as possible.
One note of caution is that due to the overlay address calculation change, during the initial bootup after the upgrade, old full nodes will go through an overlay migration process, preventing the node from becoming available for some while.
Breaking changes
- Postage contract update. The new postage contract will make the postage batches redistributable. (#3159)
- Overlay address calculation change. (#3159)
- Depth Monitor service to dynamically adjust storage depth of node based on utilization. (#3061)
- Asynchoronous refreshments to allow non-blocking protocol interactions. (#2965)
- Handshake version update to prevent nodes running older version from connecting with the new ones. (#3159)
Hardening
- Restrict the transaction endpoint. (#3121)
- Cleanups related to API, extra information on errors. (#3170, #3148)
New features
- Introduce structural logging. Users can now enable/disable logging subsystems using the HTTP API. Please check the OpenAPI spec for details. (#2975, #3147)
- Background syncing of postage events for light node. This allows the node to serve other APIs immediately. (#3127)
- Added new
expiredproperty to the stamps queried on the stamps endpoint. This can be used to distinguish between stamps that were just created and the stamps that have expired. (#3162)
Bugfixes
- Fixed an out of memory error during GC. This is a rare case which could happen on large batch expirations. (#3247)
- Handle malformed manifest contents. (#3238)
For a full PR rundown please consult the v1.8.0 milestone.