The Bee team is happy to announce the latest release v1.5.0. This release comes with major changes to the way the bee node stores data locally.
We are proud to announce the introduction of sharky. Nodes upgrading from the older version will have to perform a migration to the new storage format. With sharky, the bee node will store chunks and indexes in separate storages. The indexes will be stored in levelDB and the chunks will be stored in sharky. Due to the drastic reduction in the size of levelDB, the database operations on indexes will be significantly faster. Also, with sharky, retrieving chunks will be optimized and hence we should see improvement in the overall performance and usability of the node. This change is not backward-compatible, so after the migration, the local storage will only work with v1.5.0 and up.
Along with the changes in storage, we are also including some other small features and bugfixes.
Hardening
- cc80f74 Allow duplicate handshakes (#2794)
- e46af6c Use
testing.TempDirto create temporary test directories (#2790) - 4ce3f7d Stamps endpoint
amountvalue OpenAPI specification (#2817) - 046c5e8 Introduce timeout for all make and beekeeper runs (#2811)
- d21bf5b Add test to validate max input stream behaviour in libp2p (#2809)
New features
- ebe988e Sharky store for fix-length blobs (#2685)
- 66f0799 Start bee node without a connected chain backend. This feature is still experimental and it will be completed by the next release. (#2783)
- 7849e33 bcrypt command to generate or validate bcrypt hashes (#2788)
- 0b77fa6 Security role inheritance (#2808)
Bugfixes
For a full PR rundown please consult the v1.5.0 milestone.