Overview
We're happy to announce the Boost v1.5.1 stable release, with several new features and fixes!
See our upgrade guide for details on upgrading.
Please review the Boost and Lotus compatibility matrix to plan your upgrade.
🌟 Highlights
Includes updates previously noted in RC builds of this release
IPFS retrieval support is here with Booster-bitswap!
booster-bitswapis a binary that runs alongside theboostdprocess, to serve retrievals over the Bitswap protocol, which is the data transfer protocol used in IPFS. This release provides tools for managing a bitswap service for serving retrievals.- Note that there is currently no payment method mechanism in booster-bitswap; this endpoint is intended to serve free content.
- Check out the docs on how to start serving Bitswap retrievals
Default Grafana dashboards and monitoring
- Boost now includes configured Grafana dashboards that SP's can enable with monitoring. See the monitoring tutorial in the docs for an example on how this is set up via docker. We plan to add more dashboards over time to improve visibility into the systems performance. Reach out in #boost-help on Slack if you have any questions!
| Boostd process overview dashboard | Booster-bitswap retrieval dashboard |
|---|---|
| 
|
New storage deal proposal flags
- The new storage deal proposal flags adds configurability options to indexer announcements and storing unsealed copies of data. The current default storage deal protocol behaviors remain the same.
- Check out the details in the Propose Storage Deal Protocol docs
HTTP Retrieval Updates
- HTTP retrieval URLs have been redesigned to support piece retrievals for Spade (previously slingshot-evergreen).
- We've simplified the /piece endpoint for ease of use, and optimized for existing user needs
- BREAKING CHANGE: We removed support for getting the piece by its PayloadCid and the ability to retrieve the payload. We may revisit adding support back if there is clear demand.
- We've added a new /info endpoint that includes versioning of booster-http to make it easier to track changes
- You can see the updated endpoints in the docs - https://boost.filecoin.io/experimental-features/http-retrieval.
And more!
- You can now use the boost client to retrieve data similar to lotus' retrieve command, example:
boost retrieve --provider=t01000 bafk2bzacedsnewk7clxwab2wgwyoi7u5tzdhldx7fkxpqdq7unrxz2zoy4d2g - Boostx now includes a utility command for unsealing a sector, example:
boostx sector unseal --api-fullnode=$FULLNODE_API_INFO --api-storage=$MINER_API_INFO 2
What's Changed
- Add wallet sign to boost cli by @jsmetana in #915
- add throttler to libp2p http server for estuary by @nonsense in #927
- Periodic logsDB cleanup based on configured duration by @LexLuthr in #929
- feat: add transparent gzip support for booster-http response by @LexLuthr in #932
- feat: retry offline deal after commp errors by @LexLuthr in #899
- feat: show datacap in
boost wallet listby @LexLuthr in #959 - Add meaningful default for start-epoch by @parkan in #982
- feat: introduce http api version by @LexLuthr in #972
- Surface retrieval logs in Web UI by @dirkmc in #961
- Inspect by non-root cid by @dirkmc in #998
- feat: client flag to not announce deals by @LexLuthr in #1051
- Sort sealing worker list by date by @dirkmc in #1074
- Add bitswap bytes served grafana dashboard by @dirkmc in #1117
- add overview dashboard by @nonsense in #1122
- Add the ability to filter certain properties in the deal list by @jacobheun in #1097
- Add more storage deal filter parameters by @dirkmc in #497
- port boost retrieve to main branch by @dirkmc in #1163
- Port unseal command to main by @dirkmc in #1155
- feat: add flags for bitswap server internals by @jacobheun in #1182
- Introduce deal proposal protocol v1.2.1 by @dirkmc in #1185
New Contributors
- @jsmetana made their first contribution in #915
- @parkan made their first contribution in #982
- @ribasushi made their first contribution in #1152
- @ischasny made their first contribution in #1159
Full Changelog: v1.5.0...v1.5.1