Skip to content

v2.2.0-rc1

Pre-release
Pre-release
Compare
Choose a tag to compare
@LexLuthr LexLuthr released this 07 Mar 22:58
· 56 commits to main since this release
e73af16

Overview

We're excited to introduce Boost v2.2.0-rc1. This release enables Direct Data Onboarding (DDO) for Boost.

Compatibility

This release is compatible with Lotus versions v1.26.0-rc1 and v1.26.0-rc2. For the latest compatibility details, refer to the Boost and Lotus compatibility matrix.

⬆️ Upgrade

The upgrade guide/tutorial for upgrading to v2.2.0-rc1 can be found in the Boost documentation.

⚠️ Golang version

Boost v2.2.0-rc1 required Golang version v1.21.7 or higher.

👉 ⚠️❗ ❗ Warning: This release has breaking changes to configuration structure ❗ ❗

  1. Please save you current configuration to a file with boostd config update --diff and note down your pricing configuration from UI.
  2. Start boostd after upgrade and shutdown after a successful start
  3. Review the <boost repo>/config.toml for configuration parameters saved in step 1 and update them if they have been reset to default values. You should also restore your pricing configuration back from UI.

⚠️ ❗ ❗ Aggregate proving must be enabled in Lotus Miner for verified DDO deals to work properly❗ ❗

⭐ Highlights

DDO integration

  • Boost now support onboarding verified direct deals.
boostd import-direct --help
NAME:
   boostd import-direct - Import data for direct onboarding flow with Boost

USAGE:
   boostd import-direct [command options] <piececid> <file>

OPTIONS:
   --delete-after-import   whether to delete the data for the import after the data has been added to a sector (default: false)
   --client-addr value     
   --allocation-id value   (default: 0)
   --remove-unsealed-copy  (default: false)
   --skip-ipni-announce    indicates that deal index should not be announced to the IPNI(Network Indexer) (default: false)
   --start-epoch value     start epoch by when the deal should be proved by provider on-chain (default: 2 days from now) (default: 0)
   --help, -h              show help
  • Boost UI has a new deals page for direct deals.
  • The Boost client now offers extended functionality for handling data caps. Users can leverage the boostd client to create new data cap allocations, in addition to viewing a list of existing allocations. This streamlines the process of managing storage quotas for your direct deals.

LID clean up

  • A new process now runs every 6 hours to automatically clean up old deals from the LID. It reduces the storage footprint of the LID, improving overall performance and efficiency.
    By removing unnecessary data, the LID becomes more streamlined and easier to manage.
  • Deals that have been completed or have been penalized for violating storage commitments are no longer stored in the LID. Deals associated with the legacy system are removed once completed. Direct deals that have reached their maximum term are purged from the LID.
  • The cleanup process also removes any orphaned deals from the LID. These are deals that don't have a corresponding entry in the SQL database but are still attributed to a particular miner.

🏗️ Improvements

  • Users can advertise new deals and removal of old deals manually to IPNI.
  • Boost no longer uses go-fil-markets repo as a dependency. All the code for handling legacy deals had been purged from Boost.
  • Fixed a bug that resulted in an unexpected "End of File" (EOF) error during the parsing of segments for PODSI deals.
  • We've eliminated the practice of on-the-fly indexing for deals. This approach involved indexing deals whenever encountered through HTTP requests or Bitswap retrievals to reduce inefficiencies that could arise when dealing with unsealed sectors or inaccurate IPNI information.

What's Changed

Full Changelog: v2.1.2...v2.2.0-rc1