Bee 2.2.0 Goes Live on Thursday, September 12th!
Bee version 2.2.0 launches in one week on Thursday, September 12th, introducing significant new features and improvements for both DAPP developers and node operators. These features unlock exciting new potential use cases for Swarm developers and come with important enhancements to the user experience and economics for node operators.
This article provides an overview of the major changes in Bee version 2.2.0 For a complete list of changes, refer to the release notes for 2.2 on GitHub.
Danger
Node Operators: Make sure to read the Node Operator's Guide fully to avoid loss of rewards or compromising your nodes' security. Also make sure not to upgrade your node to 2.2.0 before fully reading the instructions, as there are steps you must take before upgrading.
Access Control Trie (ACT)
The Access Control Trie (ACT) is a major new feature that gives DAPP developers specific control over who can access encrypted data on Swarm. ACT introduces two main roles: "content publishers" and "content viewers." Content publishers can grant or revoke access to content viewers on a fine-grained, chunk-by-chunk basis. Publishers can also establish and update group lists for managing access.
For example, a content creator could use ACT to grant access to subscribers of a newsletter while keeping the content private from non-subscribers. ACT also allows publishers to control which version of the content viewers can access.
You can find a detailed usage guide for ACT here, and you can read a high-level overview of the concepts and motivations for the ACT on the ACT page in the documentation.
Neighborhood Hopping
Previously, nodes were locked into the neighborhood they started staking in, which could lead to low chances of winning rewards in overcrowded neighborhoods. The new neighborhood hopping feature allows node operators to move their nodes to underpopulated neighborhood, improving their chances of winning rewards. Detailed instructions are available in the Node Operator's Guide.
Partially Withdrawable Stake
Previously, stake was non-withdrawable and set arbitrarily to 10 xBZZ. The new partial stake withdrawal feature allows operators to withdraw part of their stake, as long as the remaining stake meets the minimum requirement. See the Node Operator's Guide for specific instructions.
Bee Debug API Removal
With the 2.2.0 release, the Bee Debug API has been entirely removed, and its endpoints have been merged into the main Bee API. Additionally, the /auth and /refresh endpoints have been removed.
This removal, announced with the 2.1.0 release, is now fully implemented in 2.2.0. It simplifies development of the Bee client and streamlines operations for node operators.
Danger
Protect Your Bee API: If you haven't done so, ensure your Bee API is protected. Follow the Node Operator's Guide for specific instructions.
Optimized Peer Connections
Nodes will now connect with fewer peers, but these connections will be more stable, resulting in greater network stability and reduced bandwidth costs for node operators.