8000 Releases · filecoin-project/lotus · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Releases: filecoin-project/lotus

v1.33.0

08 May 13:49
7bdccad
Compare
Choose a tag to compare

The Lotus v1.33.0 release introduces experimental v2 APIs with F3 awareness, featuring a new TipSet selection mechanism that significantly enhances how applications interact with the Filecoin blockchain. This release candidate also adds F3-aware Ethereum APIs via the /v2 endpoint. All of the /v2 APIs implement intelligent fallback mechanisms between F3 and Expected Consensus and are exposed through the Lotus Gateway.

Please review the detailed documentation for these experimental APIs, as they are subject to change and have important operational considerations for node operators and API providers.

☢️ Upgrade Warnings ☢️

  • There are no upgrade warnings for this release candidate.

⭐ Feature/Improvement Highlights:

Experimental v2 APIs with F3 awareness

The Lotus V2 APIs introduce a powerful new TipSet selection mechanism that significantly enhances how applications interact with the Filecoin blockchain. The design reduces API footprint, seamlessly handles both traditional Expected Consensus (EC) and the new F3 protocol, and provides graceful fallbacks.

Note

V2 APIs are highly experimental and subject to change without notice.

See Filecoin v2 APIs docs for an in-depth overview. /v2 APIs are exosed through Lotus Gateway.

This work was primarily done in (filecoin-project/lotus#13003), (filecoin-project/lotus#13027), (filecoin-project/lotus#13034), (filecoin-project/lotus#13075), (filecoin-project/lotus#13066)

F3-aware Ethereum APIs via /v2 endpoint and improvements to existing /v1 APIs

Lotus now offers two versions of its Ethereum-compatible APIs (eth_*, trace_*, net_*, web3_* and associated Filecoin.* APIs including Filecoin-specific functions such as Filecoin.EthAddressToFilecoinAddress and Filecoin.FilecoinAddressToEthAddress) with different finality handling:

  • /v2 APIs (New & Experimental): These APIs consult the F3 subsystem (if enabled) for finality information.
    • "finalized" tag maps to the F3 finalized epoch.
    • "safe" tag maps to the F3 finalized epoch or 200 epochs behind head, whichever is more recent.
  • /v1 APIs (Existing & Recommended): These maintain behavior closer to pre-F3 Lotus (EC finality) for compatibility.
    • "finalized" tag continues to use a fixed 900-epoch delay from the head (EC finality).
    • "safe" tag uses a 30-epoch delay from the head.
    • One or both of these tags may be adjusted in a future upgrade to take advantage of F3 finality.
  • Note: Previously, "finalized" and "safe" tags referred to epochs N-1. This -1 offset has been removed in both V1 and V2.
  • Additional improvements affecting both /v1 and /v2 Ethereum APIs:
    • eth_getBlockTransactionCountByNumber now accepts standard Ethereum block specifiers (hex numbers or tags like "latest", "safe", "finalized").
    • Methods accepting BlockNumberOrHash now support all standard tags ("pending", "latest", "safe", "finalized"). This includes eth_estimateGas, eth_call, eth_getCode, eth_getStorageAt, eth_getBalance, eth_getTransactionCount, and eth_getBlockReceipts.
    • Removed internal Eth*Limited methods (e.g., EthGetTransactionByHashLimited) from the supported gateway API surface.
    • Improved error handling: block selection endpoints now consistently return ErrNullRound (and corresponding JSONRPC errors) for null tipsets.

This work was done in (filecoin-project/lotus#13026), (filecoin-project/lotus#13070).

Others

🐛 Bug Fix Highlights

📝 Changelog

For the full set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributors

Contributor Commits Lines ± Files Changed
Rod Vagg 19 +13805/-3639 129
Masih H. Derkani 19 +11910/-2369 119
Jakub Sztandera 14 +2528/-202 32
Phi-rjan 12 +1707/-79 42
Steve Loeppky 3 +1287/-32 8
Piotr Galar 2 +298/-3 4
Barbara Peric 3 +182/-73 5
ZenGround0 1 +191/-0 4
CoolCu 1 +15/-49 6
Volker Mische 1 +18/-31 5
Phi 3 +32/-14 10
dependabot[bot] 1 +15/-15 2
Amit Gaikwad 1 +19/-2 2
tom 1 +0/-14 2
xixishidibei 1 +2/-11 1
Tomass 1 +4/-4 2
tsinghuacoder 1 +3/-2 1
dropbigfish 1 +1/-1 1
James Niken 1 +1/-1 1
Hubert 1 +1/-0 1
Steven Allen 1 +0/-0 2

v1.33.0-rc1

01 May 18:41
6ecb79d
Compare
Choose a tag to compare
v1.33.0-rc1 Pre-release
Pre-release

The Lotus v1.33.0-rc1 release introduces experimental v2 APIs with F3 awareness, featuring a new TipSet selection mechanism that significantly enhances how applications interact with the Filecoin blockchain. This release candidate also adds F3-aware Ethereum APIs via the /v2 endpoint. All of the /v2 APIs implement intelligent fallback mechanisms between F3 and Expected Consensus and are exposed through the Lotus Gateway.

Please review the detailed documentation for these experimental APIs, as they are subject to change and have important operational considerations for node operators and API providers.

☢️ Upgrade Warnings ☢️

  • There are no upgrade warnings for this release candidate.

⭐ Feature/Improvement Highlights:

Experimental v2 APIs with F3 awareness

The Lotus V2 APIs introduce a powerful new TipSet selection mechanism that significantly enhances how applications interact with the Filecoin blockchain. The design reduces API footprint, seamlessly handles both traditional Expected Consensus (EC) and the new F3 protocol, and provides graceful fallbacks.

Note

V2 APIs are highly experimental and subject to change without notice.

See Filecoin v2 APIs docs for an in-depth overview. /v2 APIs are exosed through Lotus Gateway.

This work was primarily done in (filecoin-project/lotus#13003), (filecoin-project/lotus#13027), (filecoin-project/lotus#13034), (filecoin-project/lotus#13075), (filecoin-project/lotus#13066)

F3-aware Ethereum APIs via /v2 endpoint and improvements to existing /v1 APIs

Lotus now offers two versions of its Ethereum-compatible APIs (eth_*, trace_*, net_*, web3_* and associated Filecoin.* APIs including Filecoin-specific functions such as Filecoin.EthAddressToFilecoinAddress and Filecoin.FilecoinAddressToEthAddress) with different finality handling:

  • /v2 APIs (New & Experimental): These APIs consult the F3 subsystem (if enabled) for finality information.
    • "finalized" tag maps to the F3 finalized epoch.
    • "safe" tag maps to the F3 finalized epoch or 200 epochs behind head, whichever is more recent.
  • /v1 APIs (Existing & Recommended): These maintain behavior closer to pre-F3 Lotus (EC finality) for compatibility.
    • "finalized" tag continues to use a fixed 900-epoch delay from the head (EC finality).
    • "safe" tag uses a 30-epoch delay from the head.
    • One or both of these tags may be adjusted in a future upgrade to take advantage of F3 finality.
  • Note: Previously, "finalized" and "safe" tags referred to epochs N-1. This -1 offset has been removed in both V1 and V2.
  • Additional improvements affecting both /v1 and /v2 Ethereum APIs:
    • eth_getBlockTransactionCountByNumber now accepts standard Ethereum block specifiers (hex numbers or tags like "latest", "safe", "finalized").
    • Methods accepting BlockNumberOrHash now support all standard tags ("pending", "latest", "safe", "finalized"). This includes eth_estimateGas, eth_call, eth_getCode, eth_getStorageAt, eth_getBalance, eth_getTransactionCount, and eth_getBlockReceipts.
    • Removed internal Eth*Limited methods (e.g., EthGetTransactionByHashLimited) from the supported gateway API surface.
    • Improved error handling: block selection endpoints now consistently return ErrNullRound (and corresponding JSONRPC errors) for null tipsets.

This work was done in (filecoin-project/lotus#13026), (filecoin-project/lotus#13070).

Others

🐛 Bug Fix Highlights

📝 Changelog

For the full set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributors

Contributor Commits Lines ± Files Changed
Rod Vagg 19 +13805/-3639 129
Masih H. Derkani 19 +11910/-2369 119
Jakub Sztandera 14 +2528/-202 32
Phi-rjan 12 +1707/-79 42
Steve Loeppky 3 +1287/-32 8
Piotr Galar 2 +298/-3 4
Barbara Peric 3 +182/-73 5
ZenGround0 1 +191/-0 4
CoolCu 1 +15/-49 6
Volker Mische 1 +18/-31 5
Phi 3 +32/-14 10
dependabot[bot] 1 +15/-15 2
Amit Gaikwad 1 +19/-2 2
tom 1 +0/-14 2
xixishidibei 1 +2/-11 1
Tomass 1 +4/-4 2
tsinghuacoder 1 +3/-2 1
dropbigfish 1 +1/-1 1
James Niken 1 +1/-1 1
Hubert 1 +1/-0 1
Steven Allen 1 +0/-0 2

v1.32.3

29 Apr 12:52
837ff35
Compare
Choose a tag to compare

This Node v1.32.3 patch release contains a critical update for all node operators. This release ensures that the F3 initial power table CID is correctly set in your Lotus node now that F3 is activated on Mainnet. All node operators must upgrade to this release before their next node restart to ensure proper F3 functionality.

☢️ Upgrade Warnings ☢️

  • All node operators must upgrade to this release before their next node restart to ensure proper F3 functionality. Storage providers only needs to upgrade their Lotus chain node to this release.

📝 Changelog

For the set of changes since the last stable release:

Contributors

Contributor Commits Lines ± Files Changed
Jakub Sztandera 1 +7/-5 2
Phi 1 +2/-2 1

miner/v1.32.3

29 Apr 12:52
837ff35
Compare
Choose a tag to compare

This Node v1.32.3 patch release contains a critical update for all node operators. This release ensures that the F3 initial power table CID is correctly set in your Lotus node now that F3 is activated on Mainnet. All node operators must upgrade to this release before their next node restart to ensure proper F3 functionality.

☢️ Upgrade Warnings ☢️

  • All node operators must upgrade to this release before their next node restart to ensure proper F3 functionality. Storage providers only needs to upgrade their Lotus chain node to this release.

📝 Changelog

For the set of changes since the last stable release:

Contributors

Contributor Commits Lines ± Files Changed
Jakub Sztandera 1 +7/-5 2
Phi 1 +2/-2 1

v1.32.2

04 Apr 18:15
ff88d82
Compare
Choose a tag to compare

This Lotus v1.32.2 release is a MANDATORY patch release. After the Calibration network upgraded to nv25, a bug was discovered in the ref-fvm KAMT library affecting ERC-20 token minting operations. You can read the the full techincal breakdown of the issue here.

This patch release includes the following updates:

  • Schedules a mandatory Calibration upgrade, happening on 2025-04-07T23:00:00Z, to fix the ERC-20 token minting bug on the Calibration network.
  • Postpones the mandatory Mainnet nv25 upgrade by 4 days, to 2025-04-14T23:00:00Z

☢️ Upgrade Warnings ☢️

  • All Lotus node and Storage Provider (SP) operators must upgrade to this patch release before the specified dates for the Calibration and Mainnet networks.
  • Please check the upgrade warning section for the v1.32.1 release for more upgrade warnings if you are upgrading from a version prior to v1.32.0.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.0.1

🚚 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 NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 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 around 1 minute. 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.

Bug Fixes and Chores

📝 Changelog

For the set of changes since the last stable release:

miner/v1.32.2

04 Apr 18:15
ff88d82
Compare
Choose a tag to compare

This Lotus v1.32.2 release is a MANDATORY patch release. After the Calibration network upgraded to nv25, a bug was discovered in the ref-fvm KAMT library affecting ERC-20 token minting operations. You can read the the full techincal breakdown of the issue here.

This patch release includes the following updates:

  • Schedules a mandatory Calibration upgrade, happening on 2025-04-07T23:00:00Z, to fix the ERC-20 token minting bug on the Calibration network.
  • Postpones the mandatory Mainnet nv25 upgrade by 4 days, to 2025-04-14T23:00:00Z

☢️ Upgrade Warnings ☢️

  • All Lotus node and Storage Provider (SP) operators must upgrade to this patch release before the specified dates for the Calibration and Mainnet networks.
  • Please check the upgrade warning section for the v1.32.1 release for more upgrade warnings if you are upgrading from a version prior to v1.32.0.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.0.1

🚚 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 NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 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 around 1 minute. 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.

Bug Fixes and Chores

📝 Changelog

For the set of changes since the last stable release:

v1.32.1

28 Mar 15:34
42d68a5
Compare
Choose a tag to compare

The Lotus v1.32.1 release is a MANDATORY patch release, which will deliver the Filecoin network version 25, codenamed “Teep” 🦵. This release sets the upgrade epoch for the Mainnet to Epoch 4867320 - 2025-04-10T23:00:00Z, and correctly sets the F3 activationcontract address to 0xA19080A1Bcb82Bb61bcb9691EC94653Eb5315716. You can find more details about how the F3 activation on Mainnet will be executed in the F3 Activation Procedure.

☢️ Upgrade Warnings ☢️

  • The Lotus v1.32.0 release had an issue where the F3 activation contract address was not set correctly. This release corrects that issue.
  • If you are running the v1.30.0 version of Lotus, please go through the Upgrade Warnings section for the v1.31.0 releases and v1.31.1 before upgrading to this release.
  • The minimum supported Golang version is now 1.23.6 (filecoin-project/lotus#12910).
  • The SupportedProofTypes field has been removed from the Filecoin.StateGetNetworkParams method because it was frequently overlooked during proof type updates and did not accurately reflect the FVM's supported proofs (filecoin-project/lotus#12881).
  • Introduced Agent field to the Filecoin.Version response. Note that this change may be breaking, depending on the clients deserialization capabilities. (filecoin-project/lotus#12904).
  • The --only-cc option has been removed from the lotus-miner sectors extend command.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.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 NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 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 around 1 minute. 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

Improvements

Bug Fixes

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

| Contr...

Read more

miner/v1.32.1

28 Mar 15:34
42d68a5
Compare
Choose a tag to compare

The Lotus v1.32.1 release is a MANDATORY patch release, which will deliver the Filecoin network version 25, codenamed “Teep” 🦵. This release sets the upgrade epoch for the Mainnet to Epoch 4867320 - 2025-04-10T23:00:00Z, and correctly sets the F3 activationcontract address to 0xA19080A1Bcb82Bb61bcb9691EC94653Eb5315716. You can find more details about how the F3 activation on Mainnet will be executed in the F3 Activation Procedure.

☢️ Upgrade Warnings ☢️

  • The Lotus v1.32.0 release had an issue where the F3 activation contract address was not set correctly. This release corrects that issue.
  • If you are running the v1.30.0 version of Lotus, please go through the Upgrade Warnings section for the v1.31.0 releases and v1.31.1 before upgrading to this release.
  • The minimum supported Golang version is now 1.23.6 (filecoin-project/lotus#12910).
  • The SupportedProofTypes field has been removed from the Filecoin.StateGetNetworkParams method because it was frequently overlooked during proof type updates and did not accurately reflect the FVM's supported proofs (filecoin-project/lotus#12881).
  • Introduced Agent field to the Filecoin.Version response. Note that this change may be breaking, depending on the clients deserialization capabilities. (filecoin-project/lotus#12904).
  • The --only-cc option has been removed from the lotus-miner sectors extend command.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.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 NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 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 around 1 minute. 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

Improvements

Bug Fixes

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

| Contr...

Read more

v1.32.0-rc3

19 Mar 09:40
e1c97a1
Compare
Choose a tag to compare
v1.32.0-rc3 Pre-release
Pre-release

This is the third release candidate of the upcoming MANDATORY Lotus v1.32.0 release, which will deliver the Filecoin network version 25, codenamed “Teep” 🦵. This release candidate sets the upgrade epoch for the calibration network to Epoch 2523454 - 2025-03-26T23:00:00Z. This is equivalent to:

  • 16:00 in Los-Angeles
  • 23:00 in London
  • 07:00 in Beijing (NB: 2025-03-27 in CST)

You can follow this release issue for keeping up with the other expected release dates, epochs, and updates: (filecoin-project/lotus#12750)

Note

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected week of 2025-03-24).

☢️ Upgrade Warnings ☢️

  • If you are running the v1.30.0 version of Lotus, please go through the Upgrade Warnings section for the v1.31.0 releases and v1.31.1 before upgrading to this release.
  • The minimum supported Golang version is now 1.23.6 (filecoin-project/lotus#12910).
  • The SupportedProofTypes field has been removed from the Filecoin.StateGetNetworkParams method because it was frequently overlooked during proof type updates and did not accurately reflect the FVM's supported proofs (filecoin-project/lotus#12881).
  • Introduced Agent field to the Filecoin.Version response. Note that this change may be breaking, depending on the clients deserialization capabilities. (filecoin-project/lotus#12904).
  • The --only-cc option has been removed from the lotus-miner sectors extend command.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.0.0-rc3

🚚 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 NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 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 around 1 minute. 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

Improvements

Bug Fixes

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Rod Vagg 46 +16240/-12784 286
Masih H. Derkani 76 +5697/-2175 290
Jakub Sztandera 38 +2048/-1652 244
Aryan Tikarya 2 +1931/-1444 43
Phi-rjan 19 +1777/-1251 69
Piotr Galar 4 +1052/-261 14
Mikers 2 +664/-149 12
Steven Allen 8 +325/-148 31
dependabot[bot] 15 +190/-208 30
Phi 4 +214/-156 12
Viraj Bhartiya 2 +190/-49 13
Aarsh Shah 1 +104/-47 6
caseylove 1 +71/-67 1
asamuj 2 +39/-43 14
ZenGround0 1 +64/-0 1
Krishang Shah 1 +30/-30 2
tediou5 1 +38/-15 14
dockercui 1 +19/-19 19
XiaoBei 2 +15/-15 7
Hubert 1 +21/-5 9
wmjae 2 +9/-9 7
taozui472 1 +9/-9 6
Yash Jagtap 1 +7/-7 5
Peter Cover 1 +6/-6 4
Andi 1 +6/-6 2
root 1 +5/-5 4
growfrow 1 +3/-3 1
Łukasz Magiera 1 +4/-0 2
wgyt 1 +2/-2 1
web3-bot 2 +2/-2 2
parthshah1 1 +2/-2 1
leo 1 +2/-2 2
futreall 1 +2/-2 2
Pranav Konde 1 +2/-2 1
Steve Loeppky 1 +2/-0 1
LexLuthr 1 +2/-0 1

miner/v1.32.0-rc3

19 Mar 09:40
e1c97a1
Compare
Choose a tag to compare
miner/v1.32.0-rc3 Pre-release
Pre-release

This is the third release candidate of the upcoming MANDATORY Lotus v1.32.0 release, which will deliver the Filecoin network version 25, codenamed “Teep” 🦵. T 78DA his release candidate sets the upgrade epoch for the calibration network to Epoch 2523454 - 2025-03-26T23:00:00Z. This is equivalent to:

  • 16:00 in Los-Angeles
  • 23:00 in London
  • 07:00 in Beijing (NB: 2025-03-27 in CST)

You can follow this release issue for keeping up with the other expected release dates, epochs, and updates: (filecoin-project/lotus#12750)

Note

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected week of 2025-03-24).

☢️ Upgrade Warnings ☢️

  • If you are running the v1.30.0 version of Lotus, please go through the Upgrade Warnings section for the v1.31.0 releases and v1.31.1 before upgrading to this release.
  • The minimum supported Golang version is now 1.23.6 (filecoin-project/lotus#12910).
  • The SupportedProofTypes field has been removed from the Filecoin.StateGetNetworkParams method because it was frequently overlooked during proof type updates and did not accurately reflect the FVM's supported proofs (filecoin-project/lotus#12881).
  • Introduced Agent field to the Filecoin.Version response. Note that this change may be breaking, depending on the clients deserialization capabilities. (filecoin-project/lotus#12904).
  • The --only-cc option has been removed from the lotus-miner sectors extend command.

🏛️ Filecoin network version 25 FIPs

📦 v16 Builtin Actor Bundle

This release candidate uses the v16.0.0-rc3

🚚 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 NV25 upgrade is expected to be medium with a bit longer pre-migration compared to the two previous network upgrade.

Pre-Migration is expected to take between 4 to 8 minutes on a SplitStore node. The migration on the upgrade epoch is expected to take 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 around 1 minute. 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

Improvements

Bug Fixes

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Rod Vagg 46 +16240/-12784 286
Masih H. Derkani 76 +5697/-2175 290
Jakub Sztandera 38 +2048/-1652 244
Aryan Tikarya 2 +1931/-1444 43
Phi-rjan 19 +1777/-1251 69
Piotr Galar 4 +1052/-261 14
Mikers 2 +664/-149 12
Steven Allen 8 +325/-148 31
dependabot[bot] 15 +190/-208 30
Phi 4 +214/-156 12
Viraj Bhartiya 2 +190/-49 13
Aarsh Shah 1 +104/-47 6
caseylove 1 +71/-67 1
asamuj 2 +39/-43 14
ZenGround0 1 +64/-0 1
Krishang Shah 1 +30/-30 2
tediou5 1 +38/-15 14
dockercui 1 +19/-19 19
XiaoBei 2 +15/-15 7
Hubert 1 +21/-5 9
wmjae 2 +9/-9 7
taozui472 1 +9/-9 6
Yash Jagtap 1 +7/-7 5
Peter Cover 1 +6/-6 4
Andi 1 +6/-6 2
root 1 +5/-5 4
growfrow 1 +3/-3 1
Łukasz Magiera 1 +4/-0 2
wgyt 1 +2/-2 1
web3-bot 2 +2/-2 2
parthshah1 1 +2/-2 1
leo 1 +2/-2 2
futreall 1 +2/-2 2
Pranav Konde 1 +2/-2 1
Steve Loeppky 1 +2/-0 1
LexLuthr 1 +2/-0 1
0