Skip to content

Releases: filecoin-project/lotus

v1.30.0-rc3

28 Oct 20:20
8a97012
Compare
Choose a tag to compare
v1.30.0-rc3 Pre-release
Pre-release

This is the third release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺.

Note

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).
  • You can follow this release issue for keeping up with the release dates, epochs, and updates: #12480.

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Krishang 2 +34106/-0 109
Rod Vagg 86 +10643/-8291 456
Masih H. Derkani 59 +7700/-4725 298
Steven Allen 55 +6113/-3169 272
kamuik16 7 +4618/-1333 285
Jakub Sztandera 10 +3995/-1226 94
Peter Rabbitson 26 +2313/-2718 275
Viraj Bhartiya 5 +2624/-580 50
Phi 7 +1337/-1519 257
Mikers 1 +1274/-455 23
Phi-rjan 29 +736/-600 92
Andrew Jackson (Ajax) 3 +732/-504 75
LexLuthr 3 +167/-996 8
Aarsh Shah 12 +909/-177 47
web3-bot 40 +445/-550 68
Piotr Galar 6 +622/-372 15
aarshkshah1992 18 +544/-299 40
Steve Loeppky 14 +401/-196 22
Frrist 1 +403/-22 5
Łukasz Magiera 4 +266/-27 13
winniehere 1 +146/-144 3
Jon 1 +209/-41 4
Aryan Tikarya 2 +183/-8 7
adlrocha 2 +123/-38 21
dependabot[bot] 11 +87/-61 22
Jiaying Wang 8 +61/-70 12
Ian Davis 2 +60/-38 5
Aayush Rajasekaran 2 +81/-3 3
hanabi1224 4 +46/-4 5
Laurent Senta 1 +44/-1 2
jennijuju 6 +21/-20 17
parthshah1 1 +23/-13 1
Brendan O'Brien 1 +25/-10 2
Jennifer Wang 4 +24/-8 6
Matthew Rothenberg 3 +10/-18 6
riskrose 1 +8/-8 7
linghuying 1 +5/-5 5
fsgerse 2 +3/-7 3
PolyMa 1 +5/-5 5
zhangguanzhang 1 +3/-3 2
luozexuan 1 +3/-3 3
Po-Chun Chang 1 +6/-0 2
Kevin Martin 1 +4/-1 2
simlecode 1 +2/-2 2
ZenGround0 1 +2/-2 2
GFZRZK 1 +2/-1 1
DemoYeti 1 +2/-1 1
qwdsds 1 +1/-1 1
Samuel Arogbonlo 1 +2/-0 2
Elias Rad 1 +1/-1 1

miner/v1.30.0-rc3

28 Oct 20:20
8a97012
Compare
Choose a tag to compare
miner/v1.30.0-rc3 Pre-release
Pre-release

This is the third release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺.

Note

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).
  • You can follow this release issue for keeping up with the release dates, epochs, and updates: #12480.

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Krishang 2 +34106/-0 109
Rod Vagg 86 +10643/-8291 456
Masih H. Derkani 59 +7700/-4725 298
Steven Allen 55 +6113/-3169 272
kamuik16 7 +4618/-1333 285
Jakub Sztandera 10 +3995/-1226 94
Peter Rabbitson 26 +2313/-2718 275
Viraj Bhartiya 5 +2624/-580 50
Phi 7 +1337/-1519 257
Mikers 1 +1274/-455 23
Phi-rjan 29 +736/-600 92
Andrew Jackson (Ajax) 3 +732/-504 75
LexLuthr 3 +167/-996 8
Aarsh Shah 12 +909/-177 47
web3-bot 40 +445/-550 68
Piotr Galar 6 +622/-372 15
aarshkshah1992 18 +544/-299 40
Steve Loeppky 14 +401/-196 22
Frrist 1 +403/-22 5
Łukasz Magiera 4 +266/-27 13
winniehere 1 +146/-144 3
Jon 1 +209/-41 4
Aryan Tikarya 2 +183/-8 7
adlrocha 2 +123/-38 21
dependabot[bot] 11 +87/-61 22
Jiaying Wang 8 +61/-70 12
Ian Davis 2 +60/-38 5
Aayush Rajasekaran 2 +81/-3 3
hanabi1224 4 +46/-4 5
Laurent Senta 1 +44/-1 2
jennijuju 6 +21/-20 17
parthshah1 1 +23/-13 1
Brendan O'Brien 1 +25/-10 2
Jennifer Wang 4 +24/-8 6
Matthew Rothenberg 3 +10/-18 6
riskrose 1 +8/-8 7
linghuying 1 +5/-5 5
fsgerse 2 +3/-7 3
PolyMa 1 +5/-5 5
zhangguanzhang 1 +3/-3 2
luozexuan 1 +3/-3 3
Po-Chun Chang 1 +6/-0 2
Kevin Martin 1 +4/-1 2
simlecode 1 +2/-2 2
ZenGround0 1 +2/-2 2
GFZRZK 1 +2/-1 1
DemoYeti 1 +2/-1 1
qwdsds 1 +1/-1 1
Samuel Arogbonlo 1 +2/-0 2
Elias Rad 1 +1/-1 1

v1.30.0-rc2

14 Oct 19:27
f8a5c82
Compare
Choose a tag to compare
v1.30.0-rc2 Pre-release
Pre-release

This is the second release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺. This release candidate sets the calibration network upgrade to epoch 207879, which corresponds to 2024-10-23T13:30:00Z. F3 is set to be automatically activated one day later at epoch 2081674, which corresponds to 2024-10-24T13:30:00Z.

Note

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).
  • You can follow this release issue for keeping up with the release dates, epochs, and updates: #12480

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Krishang 2 +34106/-0 109
Rod Vagg 86 +10643/-8291 456
Masih H. Derkani 59 +7700/-4725 298
Steven Allen 55 +6113/-3169 272
kamuik16 7 +4618/-1333 285
Jakub Sztandera 10 +3995/-1226 94
Peter Rabbitson 26 +2313/-2718 275
Viraj Bhartiya 5 +2624/-580 50
Phi 7 +1337/-1519 257
Mikers 1 +1274/-455 23
Phi-rjan 29 +736/-600 92
Andrew Jackson (Ajax) 3 +732/-504 75
LexLuthr 3 +167/-996 8
Aarsh Shah 12 +909/-177 47
web3-bot 40 +445/-550 68
Piotr Galar 6 +622/-372 15
aarshkshah1992 18 +544/-299 40
Steve Loeppky 14 +401/-196 22
Frrist 1 +403/-22 5
Łukasz Magiera 4 +266/-27 13
winniehere 1 +146/-144 3
Jon 1 +209/-41 4
Aryan Tikarya 2 +183/-8 7
adlrocha 2 +123/-38 21
dependabot[bot] 11 +87/-61 22
Jiaying Wang 8 +61/-70 12
Ian Davis 2 +60/-38 5
Aayush Rajasekaran 2 +81/-3 3
hanabi1224 4 +46/-4 5
Laurent Senta 1 +44/-1 2
jennijuju 6 +21/-20 17
parthshah1 1 +23/-13 1
Brendan O'Brien 1 +25/-10 2
Jennifer Wang 4 +24/-8 6
Matthew Rothenberg 3 +10/-18 6
riskrose 1 +8/-8 7
linghuying 1 +5/-5 5
fsgerse 2 +3/-7 3
PolyMa 1 +5/-5 5
zhangguanzhang 1 +3/-3 2
luozexuan 1 +3/-3 3
Po-Chun Chang 1 +6/-0 2
Kevin Martin 1 +4/-1 2
simlecode 1 +2/-2 2
ZenGround0 1 +2/-2 2
GFZRZK 1 +2/-1 1
DemoYeti 1 +2/-1 1
qwdsds 1 +1/-1 1
Samuel Arogbonlo 1 +2/-0 2
Elias Rad 1 +1/-1 1

miner/v1.30.0-rc2

14 Oct 19:27
f8a5c82
Compare
Choose a tag to compare
miner/v1.30.0-rc2 Pre-release
Pre-release

This is the second release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺. This release candidate sets the calibration network upgrade to epoch 207879, which corresponds to 2024-10-23T13:30:00Z. F3 is set to be automatically activated one day later at epoch 2081674, which corresponds to 2024-10-24T13:30:00Z.

Note

  1. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).
  • You can follow this release issue for keeping up with the release dates, epochs, and updates: #12480

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Krishang 2 +34106/-0 109
Rod Vagg 86 +10643/-8291 456
Masih H. Derkani 59 +7700/-4725 298
Steven Allen 55 +6113/-3169 272
kamuik16 7 +4618/-1333 285
Jakub Sztandera 10 +3995/-1226 94
Peter Rabbitson 26 +2313/-2718 275
Viraj Bhartiya 5 +2624/-580 50
Phi 7 +1337/-1519 257
Mikers 1 +1274/-455 23
Phi-rjan 29 +736/-600 92
Andrew Jackson (Ajax) 3 +732/-504 75
LexLuthr 3 +167/-996 8
Aarsh Shah 12 +909/-177 47
web3-bot 40 +445/-550 68
Piotr Galar 6 +622/-372 15
aarshkshah1992 18 +544/-299 40
Steve Loeppky 14 +401/-196 22
Frrist 1 +403/-22 5
Łukasz Magiera 4 +266/-27 13
winniehere 1 +146/-144 3
Jon 1 +209/-41 4
Aryan Tikarya 2 +183/-8 7
adlrocha 2 +123/-38 21
dependabot[bot] 11 +87/-61 22
Jiaying Wang 8 +61/-70 12
Ian Davis 2 +60/-38 5
Aayush Rajasekaran 2 +81/-3 3
hanabi1224 4 +46/-4 5
Laurent Senta 1 +44/-1 2
jennijuju 6 +21/-20 17
parthshah1 1 +23/-13 1
Brendan O'Brien 1 +25/-10 2
Jennifer Wang 4 +24/-8 6
Matthew Rothenberg 3 +10/-18 6
riskrose 1 +8/-8 7
linghuying 1 +5/-5 5
fsgerse 2 +3/-7 3
PolyMa 1 +5/-5 5
zhangguanzhang 1 +3/-3 2
luozexuan 1 +3/-3 3
Po-Chun Chang 1 +6/-0 2
Kevin Martin 1 +4/-1 2
simlecode 1 +2/-2 2
ZenGround0 1 +2/-2 2
GFZRZK 1 +2/-1 1
DemoYeti 1 +2/-1 1
qwdsds 1 +1/-1 1
Samuel Arogbonlo 1 +2/-0 2
Elias Rad 1 +1/-1 1

v1.30.0-rc1

08 Oct 16:17
d09aaa5
Compare
Choose a tag to compare
v1.30.0-rc1 Pre-release
Pre-release

This is the first release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺.

Note

  1. This release candidate does NOT set a calibration network upgrade epoch. It will be added in the second release candidate (expected October 14th).
  2. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).
  • You can follow this release issue for keeping up with the release dates, epochs, and updates: #12480

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Krishang 2 +34106/-0 109
Rod Vagg 86 +10643/-8291 456
Masih H. Derkani 59 +7700/-4725 298
Steven Allen 55 +6113/-3169 272
kamuik16 7 +4618/-1333 285
Jakub Sztandera 10 +3995/-1226 94
Peter Rabbitson 26 +2313/-2718 275
Viraj Bhartiya 5 +2624/-580 50
Phi 7 +1337/-1519 257
Mikers 1 +1274/-455 23
Phi-rjan 29 +736/-600 92
Andrew Jackson (Ajax) 3 +732/-504 75
LexLuthr 3 +167/-996 8
Aarsh Shah 12 +909/-177 47
web3-bot 40 +445/-550 68
Piotr Galar 6 +622/-372 15
aarshkshah1992 18 +544/-299 40
Steve Loeppky 14 +401/-196 22
Frrist 1 +403/-22 5
Łukasz Magiera 4 +266/-27 13
winniehere 1 +146/-144 3
Jon 1 +209/-41 4
Aryan Tikarya 2 +183/-8 7
adlrocha 2 +123/-38 21
dependabot[bot] 11 +87/-61 22
Jiaying Wang 8 +61/-70 12
Ian Davis 2 +60/-38 5
Aayush Rajasekaran 2 +81/-3 3
hanabi1224 4 +46/-4 5
Laurent Senta 1 +44/-1 2
jennijuju 6 +21/-20 17
parthshah1 1 +23/-13 1
Brendan O'Brien 1 +25/-10 2
Jennifer Wang 4 +24/-8 6
Matthew Rothenberg 3 +10/-18 6
riskrose 1 +8/-8 7
linghuying 1 +5/-5 5
fsgerse 2 +3/-7 3
PolyMa 1 +5/-5 5
zhangguanzhang 1 +3/-3 2
luozexuan 1 +3/-3 3
Po-Chun Chang 1 +6/-0 2
Kevin Martin 1 +4/-1 2
simlecode 1 +2/-2 2
ZenGround0 1 +2/-2 2
GFZRZK 1 +2/-1 1
DemoYeti 1 +2/-1 1
qwdsds 1 +1/-1 1
Samuel Arogbonlo 1 +2/-0 2
Elias Rad 1 +1/-1 1

miner/v1.30.0-rc1

08 Oct 16:18
d09aaa5
Compare
Choose a tag to compare
miner/v1.30.0-rc1 Pre-release
Pre-release

This is the first release candidate of the upcoming MANDATORY Lotus v1.30.0 release, which will deliver the Filecoin network version 24, codenamed Tuk Tuk 🛺.

Note

  1. This release candidate does NOT set a calibration network upgrade epoch. It will be added in the second release candidate (expected October 14th).
  2. This release candidate does NOT set the mainnet network upgrade epoch. It will be added in the final release (expected October 30th).
  • You can follow this release issue for keeping up with the release dates, epochs, and updates: #12480

☢️ Upgrade Warnings ☢️

  • If you are running the v1.28.x version of Lotus, please go through the Upgrade Warnings section for the v1.28.* releases and v1.29.*, before upgrading to this RC.
  • This release requires a minimum Go version of v1.22.7 or higher.
  • The releases branch has been deprecated with the 202408 split of 'Lotus Node' and 'Lotus Miner'. See https://github.com/filecoin-project/lotus/blob/master/LOTUS_RELEASE_FLOW.md#why-is-the-releases-branch-deprecated-and-what-are-alternatives for more info and alternatives for getting the latest release for both the 'Lotus Node' and 'Lotus Miner' based on the Branch and Tag Strategy.
    • To get the latest Lotus Node tag: git tag -l 'v*' | sort -V -r | head -n 1
    • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

📦 v15 Builtin Actor Bundle

This release candidate uses the v15.0.0-rc1

🚚 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.

📝 Changelog

For the set of changes since the last stable release:

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
Krishang 2 +34106/-0 109
Rod Vagg 86 +10643/-8291 456
Masih H. Derkani 59 +7700/-4725 298
Steven Allen 55 +6113/-3169 272
kamuik16 7 +4618/-1333 285
Jakub Sztandera 10 +3995/-1226 94
Peter Rabbitson 26 +2313/-2718 275
Viraj Bhartiya 5 +2624/-580 50
Phi 7 +1337/-1519 257
Mikers 1 +1274/-455 23
Phi-rjan 29 +736/-600 92
Andrew Jackson (Ajax) 3 +732/-504 75
LexLuthr 3 +167/-996 8
Aarsh Shah 12 +909/-177 47
web3-bot 40 +445/-550 68
Piotr Galar 6 +622/-372 15
aarshkshah1992 18 +544/-299 40
Steve Loeppky 14 +401/-196 22
Frrist 1 +403/-22 5
Łukasz Magiera 4 +266/-27 13
winniehere 1 +146/-144 3
Jon 1 +209/-41 4
Aryan Tikarya 2 +183/-8 7
adlrocha 2 +123/-38 21
dependabot[bot] 11 +87/-61 22
Jiaying Wang 8 +61/-70 12
Ian Davis 2 +60/-38 5
Aayush Rajasekaran 2 +81/-3 3
hanabi1224 4 +46/-4 5
Laurent Senta 1 +44/-1 2
jennijuju 6 +21/-20 17
parthshah1 1 +23/-13 1
Brendan O'Brien 1 +25/-10 2
Jennifer Wang 4 +24/-8 6
Matthew Rothenberg 3 +10/-18 6
riskrose 1 +8/-8 7
linghuying 1 +5/-5 5
fsgerse 2 +3/-7 3
PolyMa 1 +5/-5 5
zhangguanzhang 1 +3/-3 2
luozexuan 1 +3/-3 3
Po-Chun Chang 1 +6/-0 2
Kevin Martin 1 +4/-1 2
simlecode 1 +2/-2 2
ZenGround0 1 +2/-2 2
GFZRZK 1 +2/-1 1
DemoYeti 1 +2/-1 1
qwdsds 1 +1/-1 1
Samuel Arogbonlo 1 +2/-0 2
Elias Rad 1 +1/-1 1

v1.29.2

03 Oct 10:05
30d9e73
Compare
Choose a tag to compare

This is the stable release for Lotus node v1.29.2. Key updates in this release include:

  • 🆕 New API Support: Added support for EthGetBlockReceipts RPC method to retrieve transaction receipts for a specified block. This method allows users to obtain Ethereum format receipts of all transactions included in a given tipset as specified by its Ethereum block equivalent. (filecoin-project/lotus#12478)
  • 🆙 Dependency Update: Upgraded go-libp2p to version v0.35.5 (filecoin-project/lotus#12511), and go-multiaddr-dns to v0.4.0 (filecoin-project/lotus#12540).
  • 🐛 Bug Fix: Legacy/historical Drand lookups via StateGetBeaconEntry now work again for all historical epochs. StateGetBeaconEntry now uses the on-chain beacon entries and follows the same rules for historical Drand round matching as StateGetRandomnessFromBeacon and the get_beacon_randomness FVM syscall. Be aware that there will be some some variance in matching Filecoin epochs to Drand rounds where null Filecoin rounds are involved prior to network version 14. (filecoin-project/lotus#12428).

☢️ Upgrade Warnings ☢️

📝 Changelog

See v1.29.1...release/v1.29.2 for the set of changes since the last release.

👨‍👩‍👧‍👦 Contributors

Contributor Commits Lines ± Files Changed
aarshkshah1992 2 +1753/-662 12
Viraj Bhartiya 1 +770/-38 18
Rod Vagg 1 +480/-83 14
Phi-rjan 2 +20/-13 9
Phi 2 +6/-25 7

v1.29.2-rc1

27 Sep 13:29
4004ca6
Compare
Choose a tag to compare
v1.29.2-rc1 Pre-release
Pre-release

This is the first release candidate for Lotus node v1.29.2. Key updates in this release include:

  • New API Support: Added support for EthGetBlockReceipts RPC method to retrieve transaction receipts for a specified block. This method allows users to obtain Ethereum format receipts of all transactions included in a given tipset as specified by its Ethereum block equivalent. (filecoin-project/lotus#12478)
  • Dependency Update: Upgraded go-libp2p to version v0.35.5 (filecoin-project/lotus#12511)
  • Bug Fix: Legacy/historical Drand lookups via StateGetBeaconEntry now work again for all historical epochs. StateGetBeaconEntry now uses the on-chain beacon entries and follows the same rules for historical Drand round matching as StateGetRandomnessFromBeacon and the get_beacon_randomness FVM syscall. Be aware that there will be some some variance in matching Filecoin epochs to Drand rounds where null Filecoin rounds are involved prior to network version 14. (filecoin-project/lotus#12428).

📝 Changelog

See v1.29.1...release/v1.29.2-rc1 for the set of changes since the last release.

v1.29.1

16 Sep 19:36
Compare
Choose a tag to compare

This is a Lotus Node patch release that addresses a critical sync issue affecting users of the v1.29.0 release. The primary fix in this release is:

  • Downgrade of a dependency that was causing invalid BLS signatures, leading to sync failures for many Lotus nodes. See #12467 for more information about the bug.

We strongly recommend that all users currently running Lotus v1.29.0 upgrade to this version to resolve the syncing problems.

Contributors

Contributor Commits Lines ± Files Changed
Phi 1 +14/-6 7
Jiaying Wang 1 +9/-2 3

v1.28.3

16 Sep 19:16
Compare
Choose a tag to compare

This hot patch fixes the invalid BLS signature bug that was causing many lotus nodes to fail in syncing (see #12467).