FVM M0.5, Network v16 Skyr (FVM M1) Updates and Lotus Releases Timeline

[jennijuju]

More details on the Skyr network upgrade can be found here!

Subscribe to notifications on https://status.filecoin.io/ for any additional network updates!
If you have any concerns or questions, leave a comment here.

Lotus releases

**Note: This projected timeline is subject to change based on testing, auditing, new discoveries, and development.

You may follow the development progress in #fil-lotus-dev, #fvm, #fil-actors channels in Filecoin Slack where daily development and weekly updates are shared.**

You will need to be on Lotus v1.16.0 or ^ for the Network v16 Skyr (FVM M1) upgrade.

To fully support the different milestones of FVM, lotus is currently planning to publish the following releases:

• lotus v1.15.1-rcX - v1.15.1 is the Lotus March release, which includes the experimental non-programmable FVM on mainnet. By enabling LOTUS_USE_FVM_EXPERIMENTAL=1 ennvar, the lotus daemon will be running the WASM-compiled built-in actors v8 alpha that is compatible with the existing chain(Network v15 OhSnap). If you are trying it out and have any questions or feedback, please leave a comment FVM (Experimental) Mainnet v15 Testing & Feedback #8334!
  • Note: To re-iterate - this version includes experimental FVM and built-in actor v8 alpha. The lotus x FVM team has been running such node syncing network v15 since February (FVM Phase 0.5).
  • SP operation testings started on March 18, 2022 with the lotus internal testing & SPX, and you may follow the progress here.
• lotus v1.16.0 will be based on the last stable release (version depends on when v1.16.0 is ready to be code frozen for the first release candidate). This release includes consensus-breaking changes and necessary improvements for the Network v16 Skyr upgrade. We recommend all lotus users to join the testnets' testings as soon as the first release candidate is published, and upgrade your nodes to the final v1.16.0 as soon as it's published. This upgrade will switch Lotus to use FVM with built-in actors v8 (rust) with the new gas models.
• (Tentative) v1.17.0 is a potential feature release that will include everything in v1.16.0 plus the latest functionalities and improvements. More details will be shared later.~

Tentative Releases and Network Upgrade Timelines

Note: This projected timeline is subject to change based on testing, auditing, new discoveries, and development.

Time below is in UTC.

• 2022-03-17, lotus v1.15.1-rc1. (Note: This release candidate include experimental FVM that sync mainnet v15, with built-in actor v8.alpha.1 & w/o execution trace supported.
• 2022-03-23, lotus v1.15.1-rc2. (Note: This release candidate include experimental FVM that sync mainnet v15, with built-in actor v8.alpha.1 & w/o execution trace supported.
• [ ]- [x] 2022-03-27, lotus v1.15.1-rc3. (Note: This release candidate include experimental FVM that sync mainnet v15, with built-in actor v8.alpha.1 & w/o execution trace supported.
• 2022-03-29, lotus v1.15.1-rc4. (Note: This release candidate include experimental FVM that sync mainnet v15, with built-in actor v8.alpha.1 & w/o execution trace supported.
• 2022-04-07, lotus v1.15.1-rc4. (Note: This release include experimental FVM that sync mainnet v15, with built-in actor v8.alpha.1 & w/o execution trace supported. )
• 2022-05-13, lotus v1.15.3-rc1. (Note: This release include experimental FVM that sync mainnet v15, with built-in actor v8.alpha.1 & with execution trace supported. )
• 2022-05-30, lotus v1.16.0-pre-rc (Note: This tag only sets upgrade epcoh for Butterfly-SkyrNet, does not set the upgrade epochs for calibration and mainnet.)
• 2022-05-31T14:32:00Z @ epoch 333258, Butterfly-SkyrNet v16 Skyr Upgrade,
• 2022-06-14, lotus v1.16.0-rc1 Note: This release candidates only sets upgrade epcoh for calibrationnet, does not set the upgrade epoch for mainnet.)
• 2022-06-16T17:30:00Z, epoch 1044660, Calibrationnet v16 Skyr Upgrade
• 2022-06-24, lotus v1.16.0
• 2022-07-06T14:00:00Z, @ epoch 1960320, Mainnet v16 Skyr (FVM M1) Upgrade

[jennijuju]

lotus v1.15.1-rc4

A panic was reported, a panic was resolved, back on mainnet again!

[jennijuju]

🦋 Lotus v1.16.0-pre-rc & Butterfly-SkyrNet nv16 Skyr Upgrade

Butterfly v16 Skyr Upgrade epoch is set @epoch 333258, 2022-05-31T14:32:00Z. This will upgrade the butterfly-skyrnet to use FVM with built-in actor (rust) with the new gas accounting. To join the network or be ready for the upgrade, update your lotus node on butterfly net to v1.16.0-pre-rc and make butterflynet.

This is the very first upgrade in the Butterfly-Skyernet (devnet), the goal is to have the community join the implementation teams to test the new codes and catch potential consensus critical bugs or necessary enhancements in builtin actor, fvm, and client implementation, so that we can have a smooth and safe upgrade on calibration net (testnet).

⚠️ Notes

• The lotus team is highly interested in any bugs or ux improvements you may find!
  • Issues are highly appreciated if you think you've found a bug, tag @jennijuju when seeing fits!
  • You may also leave questions or feedback here and @filecoin-project/lotus-tse .
  • Alternatively, you can also join #lotus-butterfly in FC slack for more sync conversation.
• Butterfly-Skyrnet participants should expect the network to be reset and upgraded as needed if a consensus critical bug/enhancement is found.

🆕 Things you may wanna know

Built-in actor bundles

As the network introduces FVM, it's also switching from spec-actor (written in GoLang) to built-in actor (written in rust), in which the latter comes with importable bundles. This means, like filecoin proof parameters, node operators now also need to fetch the actor bundles according to the network versions for the nodes to remain operational.

In lotus v1.16.0-pre-rc, the bundle for the specific network is fetched upon the node (daemon, miner..) starts and stored in the lotus node/miner repo under builtin-actors. For this butterfly network upgrade v16, we will be using v8 dev actor . Thus, you will find two files, builtin-actors-butterflynet.car and builtin-actors-butterflynet.sha256 in builtin-actors/v8/dev/20220527, where the sha256 of the car is d6a36c397beadba9e096f41a376c424c6c2378b9a48605c2f3a191594ec8b0d1.

While lotus checks that the bundle you have is the right one upon node starts, you may also check the bundle manifest CID matches the one in the param file by running lotus state actor-cids --network-version 16, and the output should be

Network Version: 16
Actor Version: 8
Manifest CID: bafy2bzacedy4qgxbr6pbyfgcp7s7bdkc2whi5errnw67al5e2tk75j46iucv6

Actor             CID  
account           bafk2bzacebokyrxttmnta57zqv4wmuhitxvois4ms3supyxvebmwnmohcgtxi
cron              bafk2bzacebx4e75g26a74dks5cvoxp26d3ds7ecxhukgrzva6kbfn62fg3whk
init              bafk2bzacecqyh33jcmo6cgfy5ggbg4f4er62cgbowazlicfvxpcw5pisq75pc
storagemarket     bafk2bzacecpjcy5eezq32dcsje5dbiwbbmcxv2cmjhifmkukgzufl62yxkghs
storageminer      bafk2bzaceciht74rpjtr3mdalubcfjzo5n6733i4mmxj2hs5e7caowjdnijiw
multisig          bafk2bzacecg6w7xycxvisxyolz3pcbdhvwp7nxqmvtldncs3vi5fvmgsv2s5u
paymentchannel    bafk2bzacedbg6s7eii6lqqn67za5if6dtebncxanv2ammjd7fb2prf4bbeuxi
storagepower      bafk2bzaceccsmebstaf5mye6ybyssp3svdmvwupk6prjaj2hat2goimmtonnm
reward            bafk2bzacecqrqytydwusmricocq7ix574ujkeqzay5wf2aawmybcufodmyhai
system            bafk2bzacec35iwbebnacuaqszqgdbkkhmniatonaeezkl3kekm57usr7ywbme
verifiedregistry  bafk2bzacecxde6ynf6jslzgfy4q4yvypmzy3bu7vvxgcesqejxmktr5766bza

(We will get into the CIDs more in the next section).

As you may have noticed, all bundles are also available at https://github.com/filecoin-project/builtin-actors/releases, thus you can also manually download the bundles and place them in the right path. The team is also working on #8701 so that the actors will be in the lotus binary instead of being loaded on runtime!

Actor Code CIDs

If you have followed the conversation in FIP discussion Does the switch of CodeCIDs to real content-addressing impact you and FIP-0031- structure of the code cid, you should already know that from nv16, system actor code CIDs will be real content-addressing instead of being a static string like (fil/7/account)/ (fil/8/storageminer).

For lotus users, this means the CODE output when you run lotus state get-actor will now be the CID that represents the executable code for the actor, followed by the key name of the actor.

Moreover, this also means that in the future, whenever the actor code changes, the CID will change accordingly, in which will result in a need for a network upgrade for the network participants to have consensus over what executable code we should use for each system actor.

Execution Trace

For developers that are dependent on lotus execution trace, you may expect to see some structure change with the execution trace lotus provides - don't worry we are working on #8757 and is aiming to have it ready in the upcoming rc1! Tho one thing you should note is that, currently, if you don't enable LOTUS_VM_ENABLE_GAS_TRACING_VERY_SLOW envvar, you might not get Duration and GasCharges fields from the new FVM trace.

[jennijuju]

🌟 Lotus v1.16.0-rc1 & Calibrationnet nv16 Skyr Upgrade

v1.16.0-rc1 is now out.

Calibration-net upgrade is set at epoch 1044660, 2022-06-16T17:30:00Z. The bundle the network will be using is v8.0.0-rc.1(located at build/actors/v8.tar.zst ) upon/post migration, manifest CID bafy2bzacedrdn6z3z7xz7lx4wll3tlgktirhllzqxb766dxpaqp3ukxsjfsba. Your lotus node will switch from legacy VM to FVM atomically upon the upgrade. Easily enable envvar LOTUS_USE_FVM_TO_SYNC_MAINNET_V15 to sync calibration using FVM on network v15.

This upgrade introduces non-programmable FVM M1 to the network and switches the network from using go spec-actor to rust built-in actor with new gas model.

❗ Given the number of changes being introduced to protocol + impl code base, we wanna encourage ALL network participants to join the implementation teams to test the new codes and catch potential consensus critical bugs or necessary enhancements in builtin actor, fvm, and client implementation. The more joint testing effort on calibration we get over the next 2-3 weeks as a community - the more confidence & guarantee we will get for having a smooth and safe upgrade later in mainnet as a network!

PLEASE READ THE RELEASE NOTE FOR FULL DETAILS

[jennijuju]

v1.16.0 is released!

v1.16.0 is now released! for upgrade details please see the release note!

[jennijuju]

https://filecoinproject.slack.com/archives/C027TQMUVJN/p1657094066189799