filecoin-project/lotus v1.28.0-rc4

on GitHub

This is the fourth release candidate of the upcoming MANDATORY Lotus v1.28.0 release, which will deliver the Filecoin network version 23, codenamed Waffle 🧇.

This release candidate sets the calibration network to upgrade at epoch 1779094, corresponding to 2024-07-11T12:00:00Z. This release does NOT set the mainnet upgrade epoch yet, in which will be updated in the final release.

Compared to Lotus v1.28.0-rc3, the Lotus v1.28.0-rc4 release addresses an issue that allows us to publish Docker builds.

☢️ Upgrade Warnings ☢️

• If you are running the v1.26.0 or an earlier version of Lotus, please go through the Upgrade Warnings section for the v1.27.* releases, before upgrading to this RC.
• This version includes an additional migration to the events database. Node operators running Lotus with events turned on (off by default) may experience some delay in initial start-up of Lotus as a minor database migration takes place. See filecoin-project/lotus#12080 for full details.

The Filecoin network version 23 delivers the following FIPs:

• FIP-0065: Ignore built-in market locked balance in circulating supply calculation
• FIP-0079: Add BLS Aggregate Signatures to FVM
• FIP-0084: Remove Storage Miner Actor Method ProveCommitSectors
• FIP-0085: Convert f090 Mining Reserve Actor to Keyless Account Actor
• FIP-0091: Add support for legacy Ethereum transactions
• FIP-0092: NI-PoRep
• FIP-0086: Fast Finality Soft Launch

Note that we are only doing a "soft launch"/"passive testing" for F3 (Fast Finality) i.e. FIP-0086 in NV23. Please see this doc for more details.

v14 Builtin Actor Bundle

The actor bundles for the calibration network can be checked as follows:

lotus state actor-cids --network-version=23
Network Version: 23
Actor Version: 14
Manifest CID: bafy2bzacebq3hncszqpojglh2dkwekybq4zn6qpc4gceqbx36wndps5qehtau

Actor             CID  
account           bafk2bzaced5ecfm56dvtw26q56j4d32yoccyd7ggxn3qdki2enxpqqav45ths
cron              bafk2bzacedpbtttpyvtjncqoyobr63mhqqtlrygbnudhxyp2vha56f626dkfs
datacap           bafk2bzacecded3lcvo7ndsk66samyecw2trnhrgzi7jxsary3sqgopxlk6rku
eam               bafk2bzacecsda4uw7dcu76a27gnrrdcm73tgms7wrte6jbou63vloktkqc5ne
ethaccount        bafk2bzacebu2lcxfmohomjj3umslnylwugf5gssywdq3575tjarta7o227dls
evm               bafk2bzacea4xnekruhfmdnzvzeo6cbf7jsfgco6x5wje2ckwc2ui2ojzcrlgu
init              bafk2bzacedfmsdlewihdcrkdepnfata26nj7akbvexzs3chicujhjf2uxsazc
multisig          bafk2bzacedwx4svscsp6wqqu2vlcunjihvvm4u2jnsqjkwutjhir7dwtl7z6m
paymentchannel    bafk2bzacedbit7oo6lryhbo64uikvtjtfcth6oxwy3eebxerenu2h7rj44n24
placeholder       bafk2bzacedfvut2myeleyq67fljcrw4kkmn5pb5dpyozovj7jpoez5irnc3ro
reward            bafk2bzaced5rlycj7fzpscfc7p3wwxarngwqylqshj7te3uffey5tevunz4we
storagemarket     bafk2bzaceatwbyrec2nnwggxc2alpqve7rl52fmbhqflebuxmmnvg3qckjb7c
storageminer      bafk2bzacecr7ozkdz7l2pq3ig5qxae2ysivbnojhsn4gw3o57ov4mhksma7me
storagepower      bafk2bzacedgeolvjtnw7fkji5kqmx322abv6uls2v34fuml6nw36dvfcw4mtu
system            bafk2bzacederl6tlpieldsn6mkndqwd4wj5orfoqgab6p2klswfn3cjagxwla
verifiedregistry  bafk2bzaceczw2kp6gjjdcjbso7mewp7guik7gr525pal6dotdja2lrct6ok3c

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 NV23 upgrade is expected to be light with no heavy pre-migrations, here are some expected timings and resource consumption numbers:

• Pre-Migration is expected to take less then 1 minute
• The migration is expected to take less then 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.

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.

Dependencies

• github.com/filecoin-project/go-state-types (v0.14.0-dev -> v0.14.0-rc5)
• github.com/filecoin-project/filecoin-ffi (v1.27.0-rc2 -> v1.28.0-rc2)
• ref-fvm4 (as part of filecoin-ffi) (4.2.0 -> 4.3.1)
• A new github.com/filecoin-project/go-f3 dependency for F3 soft launch (v0.0.2)

Others

• Soft launch of F3 (#12119)
• NI-PoRep changes (#12130)
• Fixes for the ETH events API (#12080)
• Support for legacy Ethereum transactions (#11969)
• Ignore market balance after nv23 (#11976)
• Add finality-related params for eth_getBlockByNumber (#12110)
• rename Actor.Address to Actor.DelegatedAddress and only use it for f4 addresses (#12155)
• feat:ec: integrate F3 dynamic manifest #12185
• fix: f3: Fix F3 build parameters for testground target (#12189) (filecoin-project/lotus#12189)