NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1352 by repository stars
Latest stable
v1.18.2
Last release 3 years ago
no release in 18 months
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 53 of 53 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
689 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
⚠️ Bee v0.6.1 contains a few important improvements over v0.6.0, but is not stable. Node operators are advised to continue operating v0.5.3 until furt
⚠️ Bee v0.6.1 contains a few important improvements over v0.6.0, but is not stable. Node operators are advised to continue operating v0.5.3 until further notice in our Discord channel
The long-awaited v0.6.0 release is out. This release contains many new features and improvements, all focused on hardening your Bee node and the network.
Users should be aware that updating your node includes a migration path to ensure that there is no content stored by your node that does not have postage stamps. Users who pin content need to manually migrate their data.
The release also features a brand-new documentation and will soon be followed by releases of bee-js and the swarm-cli and bee-dashboard
full-node flag.<path_to_data-dir>/localstore. As part of this change, the db-capacity flag was changed to cache-capacity. Lastly, there exists a known issue that may cause the loss of locally pinned chunks when a node is not properly shut downPATCH /bzz/{address} endpoint (#1705)free bandwidth allowance feature now allows starting a node without a chequebook. Please take note that nodes which deployed their chequebook with bee v0.5.0 will have to be started with the --transaction TXHASH flag where TXHASH is any Ethereum transaction on goerli network sent from the bee node's Ethereum address. The hash of the chequebook deployment transaction can be used for this and can be looked up on etherscan. For nodes which first started with v0.5.1 or higher no action is necessary, as their chequebook deployment transaction will be automatically picked-up by the Bee node. (#1655)/files and /dirs endpoints. Individual files can now be uploaded on the /bzz endpoint (#1501)./cashout endpoint updated to make it easier to manage uncashed cheques. If you programatically manage your uncashed cheques, be sure to update it (#1402)./topolgy endpoint in the debugAPI now exposes metrics, allowing you to know more about your peer connections (#1658)bee version to stdout instead of stderr. (#1660)bee-clef to be v0.4.12 or higher if you don't have a chequebook deployed yet (#1539).block-time configuration parameter. Adjustment of this parameter is not advised on the Goerli network (1697)docker pull ethersphere/bee:0docker pull ethersphere/bee:0.6docker pull ethersphere/bee:0.6.1docker pull ethersphere/bee:latestdocker pull ethersphere/bee:betadocker pull quay.io/ethersphere/bee:0docker pull quay.io/ethersphere/bee:0.6docker pull quay.io/ethersphere/bee:0.6.1docker pull quay.io/ethersphere/bee:latestdocker pull quay.io/ethersphere/bee:betaNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The long-awaited v0.6.0 release is out. This release contains many new features and improvements, all focused on hardening your Bee node and the netwo
The long-awaited v0.6.0 release is out. This release contains many new features and improvements, all focused on hardening your Bee node and the network.
Users should be aware that updating your node includes a migration path to ensure that there is no content stored by your node that does not have postage stamps. Users who pin content need to manually migrate their data.
The release also features a brand-new documentation and will soon be followed by releases of bee-js and the swarm-cli and bee-dashboard
full-node flag.<path_to_data-dir>/localstore. As part of this change, the db-capacity flag was changed to cache-capacity. Lastly, there exists a known issue that may cause the loss of locally pinned chunks when a node is not properly shut downPATCH /bzz/{address} endpoint (#1705)free bandwidth allowance feature now allows starting a node without a chequebook. Please take note that nodes which deployed their chequebook with bee v0.5.0 will have to be started with the --transaction TXHASH flag where TXHASH is any Ethereum transaction on goerli network sent from the bee node's Ethereum address. The hash of the chequebook deployment transaction can be used for this and can be looked up on etherscan. For nodes which first started with v0.5.1 or higher no action is necessary, as their chequebook deployment transaction will be automatically picked-up by the Bee node. (#1655)/files and /dirs endpoints. Individual files can now be uploaded on the /bzz endpoint (#1501)./cashout endpoint updated to make it easier to manage uncashed cheques. If you programatically manage your uncashed cheques, be sure to update it (#1402)./topolgy endpoint in the debugAPI now exposes metrics, allowing you to know more about your peer connections (#1658)bee version to stdout instead of stderr. (#1660)bee-clef to be v0.4.12 or higher if you don't have a chequebook deployed yet (#1539).block-time configuration parameter. Adjustment of this parameter is not advised on the Goerli network (1697)docker pull ethersphere/bee:0docker pull ethersphere/bee:0.6docker pull ethersphere/bee:0.6.0docker pull ethersphere/bee:latestdocker pull ethersphere/bee:betadocker pull quay.io/ethersphere/bee:0docker pull quay.io/ethersphere/bee:0.6docker pull quay.io/ethersphere/bee:0.6.0docker pull quay.io/ethersphere/bee:latestdocker pull quay.io/ethersphere/bee:betaNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Dear Swarm supporters and Bee users, over the past few weeks we've been looking into various issues that have been reported by the community in an eff
Dear Swarm supporters and Bee users, over the past few weeks we've been looking into various issues that have been reported by the community in an effort to improve the user experience and resource usage of bee. This release has plenty of improvements to performance, node configurability, metrics as well as the usual refactorings and cleanups. We'd like to thank all of you for your significant contributions, be they with bug reports, PRs of all sorts, debugging profiles and just test driving version candidates on our Discord channels! We're humbled by your engagement and we hope you enjoy this latest release <3
We've exposed some of the underlying leveldb configuration parameters through new CLI flags of bee. You can now tweak your setup without having to rebuild the image every time you'd like to adjust a parameter. Important to note: since the Swarm working set is over 20 gigabytes of data, leveldb has to have enough open file limit allowance for it not to be overburdened by continuous opening and closing of file handles to retrieve blocks. We therefore recommend node operators to set the number of open file limit to at least 7200 open files. We did not set this value by default as this might be out of bound for certain setups and operating systems, resulting in a setup which is broken by default, however you are highly encouraged to set this number anywhere between 7200-12000. If you experience high I/O you can also toggle the disable seeks compaction option. Block cache and write buffer are also adjustable, and you are free to experiment with them and see what works best for your setup.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The 0.5.2 release includes two essential patches
The 0.5.2 release includes two essential patches
payment-threshold field as a copy, instead of a reference (#1329)There was one minor patch, making it possible for MacOS users who use brew to update their bee node (#1334)
Lastly, the deploy command was added to bee. This command deploys a chequebook if needed, thus reducing the time for the main service to start up and allowing bee to start in environments which have strict requirements on boot-up time (such as Windows) (#1314)
docker pull ethersphere/bee:0docker pull ethersphere/bee:0.5docker pull ethersphere/bee:0.5.2docker pull ethersphere/bee:latestdocker pull ethersphere/bee:betaThis release is mostly characterized by bug fixes 🐛, but also includes some minor new features 🎉.
This release is mostly characterized by bug fixes 🐛, but also includes some minor new features 🎉.
FEATURES 🎉:
nat-addr option to enable usage of dynamic DNS (#1278)swap-endpoint updating the default values to be in line with the new defaults of the bee node and enabling the clef-signer by default. (#1230, #1327) Note: we reccomend setting the swap-endpoint to an endpoint which you maintain yourself.BUG FIXES 🐛:
bee-get-addr command now directs the user to the bzzaar (#1228)docker pull ethersphere/bee:0docker pull ethersphere/bee:0.5docker pull ethersphere/bee:0.5.1docker pull ethersphere/bee:latestdocker pull ethersphere/bee:betaNothing published for this version
Nothing published for this version
Nothing published for this version
the /chunks endpoint has two notable breaking changes: i) it will only _accept_ content-addressed chunk uploads, and ii) it does not require a precalc…
This Bee release is a breaking release. We kindly ask all node operators to update their nodes as soon as possible to ensure continuity of the network.
bee-handshake so that the security properties of the signing module can be improved. You will be seeing incompatible stream: protocol not supported error messages in your terminal output until all nodes in the network have been upgraded./chunks endpoint has two notable breaking changes: i) it will only accept content-addressed chunk uploads, and ii) it does not require a precalculated BMT hash in order to upload a chunk. The node will calculate the BMT hash for the given span and chunk content, and will return the BMT hash in the response. For uploading single-owner chunks, please refer to the /soc endpoint documentation in our OpenAPI spec./bzz endpoint.tags./chunks endpoint. Please create your custom tag and attach it to all chunks that belong to a single upload./blocklist debugAPI endpoint which shows what peers are banned from interacting with your node.This release of Bee adds the following features and improvements:
This release of Bee adds the following features and improvements:
dirs endpoint are now idempotent, meaning that uploading the same content twice will result in the same Swarm hashThis release contains 3 essential improvements to the Bee:
This release contains 3 essential improvements to the Bee:
This release of Bee contains important new features, maintainability improvements, bug fixes, and performance increases.
This release of Bee contains important new features, maintainability improvements, bug fixes, and performance increases.
Nothing published for this version
Nothing published for this version
This release addresses some of the problems discovered in the v0.3.0 release:
This release addresses some of the problems discovered in the v0.3.0 release:
Breaking changes on protocol level (TL;DR - just update your nodes)
Bee Beta contains the required features to build rich applications on top of Swarm. This release adds:
We invite you to try it out and get in touch at our BeeHive or Telegram.
Bee's third release marks a major milestone of the Bee project; we believe that developers can now unleash rich applications over Swarm with a good balance of performance and security. We understand that as the Swarm ecosystem develops, developers might need access to low-level APIs in order to develop a rich application experience, we therefore also offer a set of low-level APIs that allow you to interact with the Swarm network in your own, custom way.
We invite you to use our APIs. Your feedback would be beneficial for us to further improve them in the future.
Several breaking changes were introduced with this version. You are advised to update your nodes promptly.
Bee Beta contains the basis for the Swarm bandwidth incentives. You will now earn gBZZ (Görli BZZ) by running your Swarm node. Conversely, you are required to pay with gBZZ in order to upload and download content. You can get gBZZ at our faucet - check our documentation on how to fund your node's chequebook.
Bee Beta releases the second iteration of Pss (Postage service over swarm). Pss is zero-leak messaging over Swarm that allows for confidential, anonymous and untraceable node-to-node communication. Pss comes with a websocket API that allows clients to send a message to a recipient on an overlay address as well as to subscribe to a topic and receive messages.
Bee now supports an external signer (Clef) for security reasons to allow private keys not to be exposed to client process.
Uploading and downloading data to Bee is now significantly more performant than it used to be(e).
All new features are documented in our documentation.
As mentioned, we invite you to start building your applications on top of Swarm. We welcome discussions and collaborations. Get in touch with us via Telegram or the Beehive.
Nothing published for this version
The second release (AKA Bee Summer) of Bee improves the utility of the DISC (as released in v0.1.0) and lays the foundation for Swarm bandwidth incent
The second release (AKA Bee Summer) of Bee improves the utility of the DISC (as released in v0.1.0) and lays the foundation for Swarm bandwidth incentives. To that end, we:
This release of Bee comes with a new documentation.
More in detail, the added features are (grouped per category):
Create unstoppable applications with: a. Manifests: a way to represent a collection in Swarm. Use this feature to upload directories or websites to Swarm. b. Single owner chunks: A special type of chunk where the address is identified as the hash of the owner and a configurable identifier. You can play with the identifier to create all kinds of funky chunks (e.g. feeds) in your virtual personal Swarm address space. c. Seek in content: Added the necessary nuts and bolts so you can seek in content that is hosted in Swarm. This allows you, among others, to play video content in your browser. d. name resolution: Content addresses are hard to read and even harder to memorize. That is why you can add name resolution. ENS and RNS name resolution is supported out-of-the-box. e. encryption: encrypt content by the Bee node before uploading.
Persistence of content with help of: a. Local pinning: ensures that certain chunks are not garbage collected on your node. b. Global pinning: makes locally pinned chunks globally discoverable.
Improved UX of existing features: b. Tags: follow the status of your upload with tags. c. Printconfig: a new command to the bee node, allows you to print the current configuration (including all default values to the console) d. Install script. This handy install script detects what system you run and makes installing bee a breeze
Swarm bandwidth incentives through: a. Accounting in retrieval and push sync: Bee nodes will count the services (download and upload) received and utilized per peer connection b. Mock settlement protocol: when the accounting signals that there is a big difference in services consumed versus provided per peer connection, the mock settlement protocol allows for sending and receiving mock payments to set the balance back to zero.
All new features and UX improvements are thoroughly documented in the new documentation.
As always you can reach out to us with bug reports and support requests through GitHub and Mattermost.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.