Skip to content

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 17, 2025

Bumps github.com/filecoin-project/lotus from 1.34.0-rc2 to 1.34.1.

Release notes

Sourced from github.com/filecoin-project/lotus's releases.

miner/v1.34.1

Node and Miner v1.34.1 / 2025-09-15

This is a non-critical patch release that fixes an issue with the Lotus v1.34.0 release where the incorrect version of filecoin-ffi was included. Lotus v1.34.0 used filecoin-ffi v1.34.0-dev when it should have used v1.34.0. This isn’t critical since it’s the same filecoin-ffi version used during the nv27 Calibration network upgrade, but for consistency with other Node implementations like Forest, we are creating this release. This ensures the inclusion of ref-fvm v4.7.3 update that was missing in v1.34.0. All users of v1.34.0 are encouraged to upgrade to v1.34.1.

Node and Miner v1.34.0 / 2025-09-11

This is a MANDATORY Lotus v1.34.0 release, which will deliver the Filecoin network version 27, codenamed “Golden Week” 🏮. This release candidate sets the upgrade epoch for the Mainnet network to Epoch 5348280: 2025-09-24T23:00:00Z. (See the local time for other timezones.)

☢️ Upgrade Warnings ☢️

  • All Lotus node and Storage Provider (SP) operators must upgrade to v1.34.x before the specified date for the Mainnet network.
  • The /v1 Ethereum APIs have "F3 awareness" for all Ethereum calls where "finalized" or "safe" are supplied. Nodes will likely return different (and likely more recent) results in v1.34.x+ than previous versions when these tags are used. See more info below.

🏛️ Filecoin network version 27 FIPs and FRCs

📦 v17 Builtin Actor Bundle

This release candidate uses v17.0.0.

🚚 Migration

All node operators, including storage providers, should be aware that ONE pre-migration is being scheduled 120 epochs before the network upgrade. The migration for the NV24 upgrade is expected to be light with no heavy pre-migrations:

  • Pre-Migration is expected to take less then 1 minute.
  • The migration on the upgrade epoch is expected to take less than 30 seconds on a node with a NVMe-drive and a newer CPU. For nodes running on slower disks/CPU, it is still expected to take less then 1 minute.
  • RAM usages is expected to be under 20GiB RAM for both the pre-migration and migration.

We recommend node operators (who haven’t enabled splitstore discard mode) that do not care about historical chain states, to prune the chain blockstore by syncing from a snapshot 1-2 days before the upgrade.

For certain node operators, such as full archival nodes or systems that need to keep large amounts of state (RPC providers), we recommend skipping the pre-migration and run the non-cached migration (i.e., just running the migration at the network upgrade epoch), and schedule for some additional downtime. Operators of such nodes can read the How to disable premigration in network upgrade tutorial.

⭐ New Features highlight

  • feat(eth): use F3 for "finalized" and "safe" resolution in v1 APIs. This switches the /v1 Ethereum APIs to have the same resolution rules as /v2, enabling F3 awareness for all Ethereum calls where "finalized" or "safe" is supplied. See F3-aware Ethereum APIs via /v2 endpoint and improvements to existing /v1 APIs below for details of how the /v2 APIs work as introduced in the 1.33.0 release. Set the environment variable LOTUS_ETH_V1_DISABLE_F3_FINALITY_RESOLUTION to 1 to revert this behaviour but note that the option to revert will likely be removed in a future release (tracking issue). (filecoin-project/lotus#13298)
  • feat(f3): expose simple ChainGetFinalizedTipSet API on v1 (and gateway) that just returns the latest F3 finalized tipset, or falls back to EC finality if F3 is not operational on the node or if the F3 finalized tipset is further back than EC finalized tipset. This API can be used for follow-up state calls that clamp to a specific tipset to have assurance of state finality. (filecoin-project/lotus#13299)
  • feat: support for F3-aware snapshot v2 format per FRC-0108 (filecoin-project/lotus#13282)
    • snapshot export now defaults to v2 format with embedded F3 finality certificates, dramatically reducing F3 catchup time from ~8 hours
    • transparently imports both v1 and v2 snapshot formats
    • to export v1 snapshots, use lotus chain export --skip-old-msgs --recent-stateroots=2001 --snapshot-version=1 <filename>
  • feat(net): add LOTUS_ENABLE_MESSAGE_FETCH_INSTRUMENTATION=1 to turn on metrics and debugging for local vs bitswap message fetching during block validation (filecoin-project/lotus#13221)

👌 Improvements

... (truncated)

Changelog

Sourced from github.com/filecoin-project/lotus's changelog.

Node and Miner v1.34.1 / 2025-09-15

This is a non-critical patch release that fixes an issue with the Lotus v1.34.0 release where the incorrect version of filecoin-ffi was included. Lotus v1.34.0 used filecoin-ffi v1.34.0-dev when it should have used v1.34.0. This isn’t critical since it’s the same filecoin-ffi version used during the nv27 Calibration network upgrade, but for consistency with other Node implementations like Forest, we are creating this release. This ensures the inclusion of ref-fvm v4.7.3 update that was missing in v1.34.0. All users of v1.34.0 are encouraged to upgrade to v1.34.1.

Node and Miner v1.34.0 / 2025-09-11

This is a MANDATORY Lotus v1.34.0 release, which will deliver the Filecoin network version 27, codenamed “Golden Week” 🏮. This release candidate sets the upgrade epoch for the Mainnet network to Epoch 5348280: 2025-09-24T23:00:00Z. (See the local time for other timezones.)

☢️ Upgrade Warnings ☢️

  • All Lotus node and Storage Provider (SP) operators must upgrade to v1.34.x before the specified date for the Mainnet network.
  • The /v1 Ethereum APIs have "F3 awareness" for all Ethereum calls where "finalized" or "safe" are supplied. Nodes will likely return different (and likely more recent) results in v1.34.x+ than previous versions when these tags are used. See more info below.

🏛️ Filecoin network version 27 FIPs and FRCs

📦 v17 Builtin Actor Bundle

This release candidate uses v17.0.0.

🚚 Migration

All node operators, including storage providers, should be aware that ONE pre-migration is being scheduled 120 epochs before the network upgrade. The migration for the NV24 upgrade is expected to be light with no heavy pre-migrations:

  • Pre-Migration is expected to take less then 1 minute.
  • The migration on the upgrade epoch is expected to take less than 30 seconds on a node with a NVMe-drive and a newer CPU. For nodes running on slower disks/CPU, it is still expected to take less then 1 minute.
  • RAM usages is expected to be under 20GiB RAM for both the pre-migration and migration.

We recommend node operators (who haven’t enabled splitstore discard mode) that do not care about historical chain states, to prune the chain blockstore by syncing from a snapshot 1-2 days before the upgrade.

For certain node operators, such as full archival nodes or systems that need to keep large amounts of state (RPC providers), we recommend skipping the pre-migration and run the non-cached migration (i.e., just running the migration at the network upgrade epoch), and schedule for some additional downtime. Operators of such nodes can read the How to disable premigration in network upgrade tutorial.

⭐ New Features highlight

  • feat(eth): use F3 for "finalized" and "safe" resolution in v1 APIs. This switches the /v1 Ethereum APIs to have the same resolution rules as /v2, enabling F3 awareness for all Ethereum calls where "finalized" or "safe" is supplied. See F3-aware Ethereum APIs via /v2 endpoint and improvements to existing /v1 APIs below for details of how the /v2 APIs work as introduced in the 1.33.0 release. Set the environment variable LOTUS_ETH_V1_DISABLE_F3_FINALITY_RESOLUTION to 1 to revert this behaviour but note that the option to revert will likely be removed in a future release (tracking issue). (filecoin-project/lotus#13298)
  • feat(f3): expose simple ChainGetFinalizedTipSet API on v1 (and gateway) that just returns the latest F3 finalized tipset, or falls back to EC finality if F3 is not operational on the node or if the F3 finalized tipset is further back than EC finalized tipset. This API can be used for follow-up state calls that clamp to a specific tipset to have assurance of state finality. (filecoin-project/lotus#13299)
  • feat: support for F3-aware snapshot v2 format per FRC-0108 (filecoin-project/lotus#13282)
    • snapshot export now defaults to v2 format with embedded F3 finality certificates, dramatically reducing F3 catchup time from ~8 hours
    • transparently imports both v1 and v2 snapshot formats
    • to export v1 snapshots, use lotus chain export --skip-old-msgs --recent-stateroots=2001 --snapshot-version=1 <filename>
  • feat(net): add LOTUS_ENABLE_MESSAGE_FETCH_INSTRUMENTATION=1 to turn on metrics and debugging for local vs bitswap message fetching during block validation (filecoin-project/lotus#13221)

👌 Improvements

  • chore(docs): mark v0 API as "deprecated" and v1 as "stable" (filecoin-project/lotus#13264)
  • feat(api): add StateMinerCreationDeposit API method for FIP-0077 - calculates the deposit required for creating a new miner (filecoin-project/lotus#13308)
  • feat(spcli): correctly handle the batch logic of lotus-miner actor settle-deal (#13189)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/filecoin-project/lotus](https://github.com/filecoin-project/lotus) from 1.34.0-rc2 to 1.34.1.
- [Release notes](https://github.com/filecoin-project/lotus/releases)
- [Changelog](https://github.com/filecoin-project/lotus/blob/v1.34.1/CHANGELOG.md)
- [Commits](filecoin-project/lotus@v1.34.0-rc2...v1.34.1)

---
updated-dependencies:
- dependency-name: github.com/filecoin-project/lotus
  dependency-version: 1.34.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Sep 17, 2025
@dependabot dependabot bot added the go Pull requests that update Go code label Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

0 participants