The Bee team is excited to announce release candidate v2.0.0-rc1! 🎉
In this release we introduce a brand new mechanism of data redundancy in Swarm with erasure coding, which, under the hood, makes use of Reed-Solomon erasure coding and dispersed replicas.
Erasure Coding
A new header Swarm-Redundancy-Level: n can be passed to upload requests to turn on erasure coding where n is [0, 4]. Refer to the table below for different levels and expected error rates.
| Redundancy Level | Pseudonym | Expected Chunk Retrieval Error Rate |
|---|---|---|
| 0 | None | 0% |
| 1 | Medium | 1% |
| 2 | Strong | 5% |
| 3 | Insane | 10% |
| 4 | Paranoid | 50% |
Changes for Lowering the Storage Radius
The triggering of a storage radius decrease now depends on the reserve size within the radius (chunks in the reserve with proximity order >= current radius), not the total reserve size, being lower than the 50% of the reserve capacity.
Updated Crypto Library
The btcd crypto library that Bee uses for things like signing chunks and maintaining keys has been updated.
Warning: this is an experimental release. Users only interested in trying out the features and changes in this release should update to this version.
For questions, comments, and feedback, reach out on Discord.
Features
- Uploads may now be equipped with erasure coding which brings a new level of data redundancy to Swarm. ( #4491 )
Bug fixes
- Fixed the storage radius metric being set incorrectly. ( #4518 )
- Fixed a bug where the storage radius does not decrease even though the true reserve size is lower than the threshold. ( #4514 )
Hardening
- Updated the btcd crypto library version. ( #4516 )