Skip to content

Releases: filecoin-project/boost

v2.4.0

10 Nov 10:55
@LexLuthr LexLuthr
v2.4.0
3965a2c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.4.0 Latest
Latest

Overview

We're excited to introduce Boost v2.4.0. This release enables the Filecoin Network upgrade to NV24 for Boost.
Please refer to Curio documentation and getting started guide for Curio <> Boost configuration.

Compatibility

This release is compatible with Lotus versions v1.30.0. For the latest compatibility details, refer to the Boost compatibility matrix.

What's Changed

New Contributors

Full Changelog: v2.3.0...v2.4.0

Contributors

strahe, dependabot, and 3 other contributors
Assets 2
Loading

v2.4.0-rc1

16 Oct 11:13
@LexLuthr LexLuthr
v2.4.0-rc1
e67fcd8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.4.0-rc1 Pre-release
Pre-release

Overview

We're excited to introduce Boost v2.4.0-rc1. This release enables the Filecoin Network upgrade to NV24 for Boost.
Please refer to Curio documentation and getting started guide for Curio <> Boost configuration.

Compatibility

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

⚠️ Golang version

Boost v2.4.0-rc1 required Golang version v1.22.3 or higher.

What's Changed

New Contributors

Full Changelog: v2.3.0...v2.4.0-rc1

Contributors

strahe, dependabot, and 3 other contributors
Assets 2
Loading

v2.3.0

30 Jul 08:52
@LexLuthr LexLuthr
v2.3.0
15f5241
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.3.0

Overview

We're excited to introduce Boost v2.3.0. This release enable the Filecoin Network upgrade to NV23(🧇) for Boost.
It also focuses on compatibility with Curio.
Please refer to Curio documentation and getting started guide for Curio <> Boost configuration.

Compatibility

This release is compatible with Lotus versions v1.28.1. For the latest compatibility details, refer to the Boost compatibility matrix.

⚠️ Golang version

Boost v2.3.0 required Golang version v1.22.3 or higher.

What's Changed

New Contributors

Full Changelog: v2.2.0...v2.3.0

Contributors

ZenGround0, jmg-duarte, and 4 other contributors
Assets 2
Loading

v2.3.0-rc2

13 Jun 11:22
@LexLuthr LexLuthr
v2.3.0-rc2
448710d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.3.0-rc2 Pre-release
Pre-release

Overview

We're excited to introduce Boost v2.3.0-rc2. This release focuses on compatibility with Curio.
Please refer to Curio documentation and getting started guide for Curio <> Boost configuration.

Compatibility

This release is compatible with Lotus versions v1.27.0. For the latest compatibility details, refer to the Boost compatibility matrix.

⚠️ Golang version

Boost v2.3.0-rc2 required Golang version v1.22.3 or higher.

What's Changed

Full Changelog: v2.3.0-rc1...v2.3.0-rc2

Contributors

dependabot and LexLuthr
Assets 2
Loading

v2.3.0-rc1

29 May 09:42
@LexLuthr LexLuthr
v2.3.0-rc1
4e7692d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.3.0-rc1 Pre-release
Pre-release

Overview

We're excited to introduce Boost v2.3.0-rc1. This release focuses on compatibility with Lotus v1.27.0 and some minor bug fixes.

Compatibility

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

⚠️ Golang version

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

What's Changed

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

Contributors

dependabot and LexLuthr
Assets 2
Loading

v2.2.0

03 Apr 17:25
@LexLuthr LexLuthr
v2.2.0
16a4de2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.2.0

Overview

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

Compatibility

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

⬆️ Upgrade

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

⚠️ Golang version

Boost v2.2.0 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 updated --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.

🗄️ Curio compatibility

This Boost release will be fully compatible with upcoming Curio release. Curio is the new improved Lotus-miner alternative with a distributed scheduling. You can read more about Curio here.

🏗️ 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.
  • Boost client can be used to extend the existing verified claims for old and new verified deal.
  • Boost UI page is updated to show all the relevant information for DDO deals.
  • Some minor fixes to improve the DDO deal workflow in Boost.

What's Changed

Full Changelog: v2.1.2...v2.2.0

Contributors

nonsense, dependabot, and LexLuthr
Assets 2
Loading

v2.2.0-rc2

26 Mar 17:56
@LexLuthr LexLuthr
v2.2.0-rc2
e9a50bb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.2.0-rc2 Pre-release
Pre-release

Overview

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

Compatibility

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

⬆️ Upgrade

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

⚠️ Golang version

Boost v2.2.0-rc2 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❗ ❗

🏗️ Improvements

  • Boost client can be used to extend the existing verified claims for old and new verified deal.
  • Boost UI page is updated to show all the relevant information for DDO deals.
  • Some minor fixes to improve the DDO deal workflow in Boost.

What's Changed

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

Contributors

dependabot and LexLuthr
Assets 2
Loading

v2.2.0-rc1

07 Mar 22:58
@LexLuthr LexLuthr
v2.2.0-rc1
e73af16
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.2.0-rc1 Pre-release
Pre-release

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

Contributors

nonsense and LexLuthr
Assets 2
Loading

v2.1.2

22 Jan 15:05
@LexLuthr LexLuthr
v2.1.2
baf26c6
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.1.2

Overview

We're excited to introduce Boost v2.1.2. This release focuses on reducing the resource usage utilisation for boostd-data service.

This is a recommended release for everyone on Boost v2.x

Compatibility

This release is compatible with Lotus versions v1.24.0 and v1.25.0. For the latest compatibility details, refer to the Boost and Lotus compatibility matrix.

⭐ Highlights

  1. A new command to send a removal advertisement to IPNI. This can be used to clean up any old records from network indexers.
  2. Performance improvements in piece doctor.
  3. Piece doctor can now be disabled in configuration.
  4. UI enhancements for deal lifecycle and sector lifecycle separation.

What's Changed

Full Changelog: v2.1.1...v2.1.2

Contributors

nonsense, masih, and 4 other contributors
Assets 2
Loading

v2.1.1

30 Nov 15:16
@LexLuthr LexLuthr
v2.1.1
e9d18ac
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.1.1

Overview

We're excited to introduce Boost v2.1.1. This release focuses on reducing the resource usage utilisation for boostd-data service.

Compatibility

This release is compatible with Lotus versions v1.24.0 and v1.25.0. For the latest compatibility details, refer to the Boost and Lotus compatibility matrix.

⚠️ Important Upgrade Notice

👉 Before updating, carefully read the release notes and documentation. Storage providers will need to set up a database service and undergo a database migration process. Incorrect procedures can lead to permanent data loss.

⭐ Highlights

  • The high CPU usage by boostd-data service is now fixed
  • Deal indexing has been improved to avoid deals getting stuck in "Announcing" state
  • Boost UI should not display the momentary searching message: %!w(<nil>) message anymore

What's Changed

Full Changelog: v2.1.0...v2.1.1

Contributors

nonsense, ischasny, and LexLuthr
Assets 2
Loading