filecoin-project/boost v1.7.3-rc1

on GitHub

Overview

We're happy to announce the Boost v1.7.3-rc1 release.

⚠️ The minimum required Golang version for Boost is now v1.19.7, and Golang 1.20.x is Highly Recommended due to known potential panics ⚠️

Golang versions are now included in the compatibility matrix.

This release is compatible with the Lotus v1.23.0 release. See the Boost and Lotus compatibility matrix for up to date information to plan your upgrade.

⚠️ If you have not yet upgraded to Boost 1.7.0 or later, please see the 1.7.0 release notes before upgrading. ⚠️

🌟 Highlights

Option to disable tagging of wallet funds

• By default, Boost tags funds for each deal with the value defined by MaxPublishDealsFee, and untags the funds when the deal is published. This is to prevent SPs from accepting too many deals and then not being able to publish them due to a lack of funds.
• Some SPs would prefer to manage their wallet funds themselves.
• Tagging can now be disabled by setting the following variable in Boost config

   	// Whether to enable tagging of funds. If enabled, each time a deal is
	// accepted boost will tag funds for that deal so that they cannot be used
	// for any other deal.
	FundsTaggingEnabled bool

Fix for stalled Graphsync retrievals

• When a deal is announced, the network indexer queries boost to get the cids of each block in the deal data
• There was an issue with the code that could cause retrievals to stall.
• Requests made via the network indexers, like cid.contact, are now routed through the simplified graphsync retrieval pathways as opposed to the legacy retrievals which is prone to stalling, and is less performant.

Improvements

• A listen address can be provided for GraphQL service. This should mitigate security risks for publicly exposed Boost nodes.
• Offline deals waiting for data can be cancelled from the UI.
• Boost will now fail the deal if a snap-deal sector reverts to Proving at any point of the sealing process. Earlier, Boost would incorrectly mark such deals as successfully sealed.
• Boost now supports local commp calculation for 64 GiB sectors.

What's Changed

• Add a config flag to disable funds tagging by @dirkmc in #1367
• chore:add graphql server listen address config by @rickiey in #1327
• put g.activeRetrievals behind a lock everywhere by @nonsense in #1404
• fix: mpool all messages panic by @LexLuthr in #1405
• feat: add cancel button for offline deals waiting for data by @LexLuthr in #1413
• chore: enable files gateway in devnet by default by @jacobheun in #1420
• car size required only for online deals by @anjor in #1421
• Don't throw error if deal already announced by @dirkmc in #1426
• fix: use new retrieval code path for indexers by @jacobheun in #1425
• fix usage comments on boostd data-transfers commands by @dirkmc in #1437
• fix download block link spacing by @dirkmc in #1438
• fix: fail deal if snap-deal sectors fails sealing by @LexLuthr in #1419
• fix: 64 GiB local commp by @LexLuthr in #1439

New Contributors

• @rickiey made their first contribution in #1327

Full Changelog: v1.7.2...v1.7.3-rc1