This Lotus release candidate introduces the new ChainIndexer subsystem, enhancing the indexing of Filecoin chain state for improved RPC performance. Several bug fixes in the block production loop are also included. Please review the upgrade warnings and documentation for any important changes affecting RPC providers, node operators and storage providers.

☢️ Upgrade Warnings ☢️

• The introduction of the new ChainIndexer subsystem replaces the existing MsgIndex, EthTxHashLookup, and EventIndex implementations. This change may affect RPC providers and node operators who use or expose Ethereum and/or events APIs. It is crucial to review the ChainIndexer documentation for operators to understand how to enable, configure, and use the new Indexer.

⭐ New Feature Highlights:

• New ChainIndexer subsystem to index Filecoin chain state such as tipsets, messages, events and ETH transactions for accurate and faster RPC responses. The ChainIndexer replaces the existing MsgIndex, EthTxHashLookup and EventIndex implementations in Lotus, which suffer from a multitude of known problems. If you are an RPC provider or a node operator who uses or exposes Ethereum and/or events APIs, please refer to the ChainIndexer documentation for operators for information on how to enable, configure and use the new Indexer. While there is no automated data migration and one can upgrade and downgrade without backups, there are manual steps that need to be taken to backfill data when upgrading to this Lotus version, or downgrading to the previous version without ChainIndexer. Please be aware that that this feature removes some options in the Lotus configuration file, if these have been set, Lotus will report an error when starting. See the documentation for more information
• lotus chain head now supports a --height flag to print just the epoch number of the current chain head (filecoin-project/lotus#12609)
• Implement EthGetTransactionByBlockNumberAndIndex (eth_getTransactionByBlockNumberAndIndex) and EthGetTransactionByBlockHashAndIndex (eth_getTransactionByBlockHashAndIndex) methods. (filecoin-project/lotus#12618)
• lotus-shed indexes inspect-indexes now performs a comprehensive comparison of the event index data for each message by comparing the AMT root CID from the message receipt with the root of a reconstructed AMT. Previously inspect-indexes simply compared event counts. Comparing AMT roots instead confirms all the event data is byte-perfect. (filecoin-project/lotus#12570)
• Reduce size of embedded genesis CAR files by removing WASM actor blocks and compressing with zstd. This reduces the lotus binary size by approximately 10 MiB. (filecoin-project/lotus#12439)

🐛 Bug Fix Highlights

• Add logic to check if the miner's owner address is delegated (f4 address). If it is delegated, the lotus-shed sectors termination-estimate command now sends the termination state call using the worker ID. This fix resolves the issue where termination-estimate did not function correctly for miners with delegated owner addresses. (filecoin-project/lotus#12569)
• The mining loop will now correctly "stick" to the same upstream lotus node for all operations pertaining to mining a single block (filecoin-project/lotus#12665).
• The Lotus Miner will now always mine on the latest chain head returned by lotus, even if that head has less "weight" than the previously seen head. This is necessary because F3 may end up finalizing a tipset with a lower weight, although this situation should be rare on the Filecoin mainnet. (filecoin-project/lotus#12659)
• Make the ordering of event output for eth_ APIs and GetActorEventsRaw consistent, sorting ascending on: epoch, message index, event index and original event entry order. (filecoin-project/lotus#12623)
• Event APIs (Eth events and actor events) should only return reverted events if client queries by specific block hash / tipset. Eth and actor event subscription APIs should always return reverted events to enable accurate observation of real-time changes. (filecoin-project/lotus#12585)
• Fix a bug in the lotus-shed indexes backfill-events command that may result in either duplicate events being backfilled where there are existing events (such an operation should be idempotent) or events erroneously having duplicate logIndex values when queried via ETH APIs. (filecoin-project/lotus#12567)

📝 Changelog

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

• Node: v1.30.0...v1.31.0-rc1
• Miner: v1.30.0...miner/v1.31.0-rc1

👨‍👩‍👧‍👦 Contributors

This Lotus release candidate introduces the new ChainIndexer subsystem, enhancing the indexing of Filecoin chain state for improved RPC performance. Several bug fixes in the block production loop are also included. Please review the upgrade warnings and documentation for any important changes affecting RPC providers, node operators and storage providers.

☢️ Upgrade Warnings ☢️

• The introduction of the new ChainIndexer subsystem replaces the existing MsgIndex, EthTxHashLookup, and EventIndex implementations. This change may affect RPC providers and node operators who use or expose Ethereum and/or events APIs. It is crucial to review the ChainIndexer documentation for operators to understand how to enable, configure, and use the new Indexer.

⭐ New Feature Highlights:

• New ChainIndexer subsystem to index Filecoin chain state such as tipsets, messages, events and ETH transactions for accurate and faster RPC responses. The ChainIndexer replaces the existing MsgIndex, EthTxHashLookup and EventIndex implementations in Lotus, which suffer from a multitude of known problems. If you are an RPC provider or a node operator who uses or exposes Ethereum and/or events APIs, please refer to the ChainIndexer documentation for operators for information on how to enable, configure and use the new Indexer. While there is no automated data migration and one can upgrade and downgrade without backups, there are manual steps that need to be taken to backfill data when upgrading to this Lotus version, or downgrading to the previous version without ChainIndexer. Please be aware that that this feature removes some options in the Lotus configuration file, if these have been set, Lotus will report an error when starting. See the documentation for more information
• lotus chain head now supports a --height flag to print just the epoch number of the current chain head (filecoin-project/lotus#12609)
• Implement EthGetTransactionByBlockNumberAndIndex (eth_getTransactionByBlockNumberAndIndex) and EthGetTransactionByBlockHashAndIndex (eth_getTransactionByBlockHashAndIndex) methods. (filecoin-project/lotus#12618)
• lotus-shed indexes inspect-indexes now performs a comprehensive comparison of the event index data for each message by comparing the AMT root CID from the message receipt with the root of a reconstructed AMT. Previously inspect-indexes simply compared event counts. Comparing AMT roots instead confirms all the event data is byte-perfect. (filecoin-project/lotus#12570)
• Reduce size of embedded genesis CAR files by removing WASM actor blocks and compressing with zstd. This reduces the lotus binary size by approximately 10 MiB. (filecoin-project/lotus#12439)

🐛 Bug Fix Highlights

• Add logic to check if the miner's owner address is delegated (f4 address). If it is delegated, the lotus-shed sectors termination-estimate command now sends the termination state call using the worker ID. This fix resolves the issue where termination-estimate did not function correctly for miners with delegated owner addresses. (filecoin-project/lotus#12569)
• The mining loop will now correctly "stick" to the same upstream lotus node for all operations pertaining to mining a single block (filecoin-project/lotus#12665).
• The Lotus Miner will now always mine on the latest chain head returned by lotus, even if that head has less "weight" than the previously seen head. This is necessary because F3 may end up finalizing a tipset with a lower weight, although this situation should be rare on the Filecoin mainnet. (filecoin-project/lotus#12659)
• Make the ordering of event output for eth_ APIs and GetActorEventsRaw consistent, sorting ascending on: epoch, message index, event index and original event entry order. (filecoin-project/lotus#12623)
• Event APIs (Eth events and actor events) should only return reverted events if client queries by specific block hash / tipset. Eth and actor event subscription APIs should always return reverted events to enable accurate observation of real-time changes. (filecoin-project/lotus#12585)
• Fix a bug in the lotus-shed indexes backfill-events command that may result in either duplicate events being backfilled where there are existing events (such an operation should be idempotent) or events erroneously having duplicate logIndex values when queried via ETH APIs. (filecoin-project/lotus#12567)

📝 Changelog

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

• Node: v1.30.0...v1.31.0-rc1
• Miner: v1.30.0...miner/v1.31.0-rc1

👨‍👩‍👧‍👦 Contributors

This is the final release of the MANDATORY Lotus v1.30.0 release, which delivers the Filecoin network version 24, codenamed Tuk Tuk 🛺. This release sets the Mainnet to upgrade at epoch 4461240, corresponding to 2024-11-20T23:00:00Z.

☢️ 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 release.
• 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*' | grep -v -E '-rc' | sort -V -r | head -n 1
  • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | grep -v -E '-rc' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

⚠️ The activation of F3 (Fast Finality) has been postponed for mainnet due to unresolved issues in the Client/SP code and the F3 protocol itself. These issues require further testing and resolution before we can safely deploy F3 on the mainnet. Read the full post here.

📦 v15 Builtin Actor Bundle

The v15.0.0 actor bundle is used for supporting this upgrade. Make sure that your Lotus actor bundle matches the v15 actors manifest by running the following cli after upgrading to this release:

lotus state actor-cids --network-version=24
Network Version: 24
Actor Version: 15
Manifest CID: bafy2bzaceakwje2hyinucrhgtsfo44p54iw4g6otbv5ghov65vajhxgntr53u

Actor             CID  
account           bafk2bzacecia5zacqt4gvd4z7275lnkhgraq75shy63cphakphhw6crf4joii
cron              bafk2bzacecbyx7utt3tkvhqnfk64kgtlt5jlvv56o2liwczikgzfowk2cvqvk
datacap           bafk2bzacecrypcpyzidphfl3sf3vhrjbiwzu7w3hoole45wsk2bqpverw4tni
eam               bafk2bzacebybq7keb45l6isqfaiwxy5oi5wlpknhggjheut7q6xwp7mbxxku4
ethaccount        bafk2bzaceajdy72edg3t2zcb6qwv2wgdsysfwdtczcklxcp4hlwh7pkxekja4
evm               bafk2bzaceandffodu45eyro7jr7bizxw7ibipaiskt36xbp4vpvsxtrpkyjfm
init              bafk2bzaceb5mjmy56ediswt2hvwqdfs2xzi4qw3cefkufoat57yyt3iwkg7kw
multisig          bafk2bzaced3csl3buj7chpunsubrhwhchtskx674fpukfen4u6pbpkcheueya
paymentchannel    bafk2bzacea3dpsfxw7cnj6zljmjnnaubp43a5kvuausigztmukektesg2flei
placeholder       bafk2bzacedfvut2myeleyq67fljcrw4kkmn5pb5dpyozovj7jpoez5irnc3ro
reward            bafk2bzaceapkgue3gcxmwx7bvypn33okppa2nwpelcfp7oyo5yln3brixpjpm
storagemarket     bafk2bzaceaqrnikbxymygwhwa2rsvhnqj5kfch75pn5xawnx243brqlfglsl6
storageminer      bafk2bzacecnl2hqe3nozwo7al7kdznqgdrv2hbbbmpcbcwzh3yl4trog433hc
storagepower      bafk2bzacecb3tvvppxmktll3xehjc7mqbfilt6bd4gragbdwxn77hm5frkuac
system            bafk2bzacecvcqje6kcfqeayj66hezlwzfznytwqkxgw7p64xac5f5lcwjpbwe
verifiedregistry  bafk2bzacecudaqwbz6dukmdbfok7xuxcpjqighnizhxun4spdqvnqgftkupp2

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

• Node: v1.29.2...v1.30.0
• Miner: v1.28.3...miner/v1.30.0

👨‍👩‍👧‍👦 Contributors

This is the final release of the MANDATORY Lotus v1.30.0 release, which delivers the Filecoin network version 24, codenamed Tuk Tuk 🛺. This release sets the Mainnet to upgrade at epoch 4461240, corresponding to 2024-11-20T23:00:00Z.

☢️ 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 release.
• 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*' | grep -v -E '-rc' | sort -V -r | head -n 1
  • To get the latest Lotus Miner tag: git tag -l 'miner/v*' | grep -v -E '-rc' | sort -V -r | head -n 1

🏛️ Filecoin network version 24 FIPs

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

⚠️ The activation of F3 (Fast Finality) has been postponed for mainnet due to unresolved issues in the Client/SP code and the F3 protocol itself. These issues require further testing and resolution before we can safely deploy F3 on the mainnet. Read the full post here.

📦 v15 Builtin Actor Bundle

The v15.0.0 actor bundle is used for supporting this upgrade. Make sure that your Lotus actor bundle matches the v15 actors manifest by running the following cli after upgrading to this release:

lotus state actor-cids --network-version=24
Network Version: 24
Actor Version: 15
Manifest CID: bafy2bzaceakwje2hyinucrhgtsfo44p54iw4g6otbv5ghov65vajhxgntr53u

Actor             CID  
account           bafk2bzacecia5zacqt4gvd4z7275lnkhgraq75shy63cphakphhw6crf4joii
cron              bafk2bzacecbyx7utt3tkvhqnfk64kgtlt5jlvv56o2liwczikgzfowk2cvqvk
datacap           bafk2bzacecrypcpyzidphfl3sf3vhrjbiwzu7w3hoole45wsk2bqpverw4tni
eam               bafk2bzacebybq7keb45l6isqfaiwxy5oi5wlpknhggjheut7q6xwp7mbxxku4
ethaccount        bafk2bzaceajdy72edg3t2zcb6qwv2wgdsysfwdtczcklxcp4hlwh7pkxekja4
evm               bafk2bzaceandffodu45eyro7jr7bizxw7ibipaiskt36xbp4vpvsxtrpkyjfm
init              bafk2bzaceb5mjmy56ediswt2hvwqdfs2xzi4qw3cefkufoat57yyt3iwkg7kw
multisig          bafk2bzaced3csl3buj7chpunsubrhwhchtskx674fpukfen4u6pbpkcheueya
paymentchannel    bafk2bzacea3dpsfxw7cnj6zljmjnnaubp43a5kvuausigztmukektesg2flei
placeholder       bafk2bzacedfvut2myeleyq67fljcrw4kkmn5pb5dpyozovj7jpoez5irnc3ro
reward            bafk2bzaceapkgue3gcxmwx7bvypn33okppa2nwpelcfp7oyo5yln3brixpjpm
storagemarket     bafk2bzaceaqrnikbxymygwhwa2rsvhnqj5kfch75pn5xawnx243brqlfglsl6
storageminer      bafk2bzacecnl2hqe3nozwo7al7kdznqgdrv2hbbbmpcbcwzh3yl4trog433hc
storagepower      bafk2bzacecb3tvvppxmktll3xehjc7mqbfilt6bd4gragbdwxn77hm5frkuac
system            bafk2bzacecvcqje6kcfqeayj66hezlwzfznytwqkxgw7p64xac5f5lcwjpbwe
verifiedregistry  bafk2bzacecudaqwbz6dukmdbfok7xuxcpjqighnizhxun4spdqvnqgftkupp2

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

• Node: v1.29.2...v1.30.0
• Miner: v1.28.3...miner/v1.30.0

👨‍👩‍👧‍👦 Contributors

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

• 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

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0086: Fast Finality in Filecoin (F3)
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

📦 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:

• Node: v1.29.2...v1.30.0-rc2
• Miner: v1.28.3...miner/v1.30.0-rc2

👨‍👩‍👧‍👦 Contributors

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

• 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

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0086: Fast Finality in Filecoin (F3)
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

📦 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:

• Node: v1.29.2...v1.30.0-rc2
• Miner: v1.28.3...miner/v1.30.0-rc2

👨‍👩‍👧‍👦 Contributors

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.

• 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

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0086: Fast Finality in Filecoin (F3)
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

📦 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:

• Node: v1.29.2...v1.30.0-rc2
• Miner: v1.28.3...miner/v1.30.0-rc2

👨‍👩‍👧‍👦 Contributors

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.

• 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

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0086: Fast Finality in Filecoin (F3)
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

📦 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:

• Node: v1.29.2...v1.30.0-rc2
• Miner: v1.28.3...miner/v1.30.0-rc2

👨‍👩‍👧‍👦 Contributors

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

• 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

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0086: Fast Finality in Filecoin (F3)
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

📦 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:

• Node: v1.29.2...v1.30.0-rc1
• Miner: v1.28.3...miner/v1.30.0-rc1

👨‍👩‍👧‍👦 Contributors

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

• 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

• FIP-0081: Introduce lower bound for sector initial pledge
• FIP-0086: Fast Finality in Filecoin (F3)
• FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM
• FIP-0095: Add FEVM precompile to fetch beacon digest from chain history

📦 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:

• Node: v1.29.2...v1.30.0-rc1
• Miner: v1.28.3...miner/v1.30.0-rc1

👨‍👩‍👧‍👦 Contributors