Network v16 Scope and Upgrade Timeline

[jennijuju]

The purpose of this conversation thread is to provide an asynchronous space for core devs to review current FIPs, share ongoing dev priorities and dependencies, flag risks, and otherwise help determine an appropriate timeline for Filecoin Network v16 upgrade.

Note: We will take more feedback on timeline from the community later on.

This was discussed in Core Devs call 36 (links to meeting notes and recording will be added later).

Creating two threads for discussion :

• scope
• timeline

[jennijuju]

Scope

According to the discussion in the Core Dev call 36(Feb 10, 2022), the tentative scope of ntwk v16 is to (only) introduce Filecoin Virtual Machine v0.

As of Feb 16, 2022, FIPs for FVM v0 are:

• FIP-0030 Introducing the Filecoin Virtual Machine (FVM)
• [FIP-0031(Atomic switch to non-programmable FVM)] - currently the FIP Draft is in pr draft

There are more FIPs that are subject to come, and we will be updating this list as they are created.

[q9f]

Since FIP-0031 is not yet ready, we only have two options

1. Execute NV16 with FIP-0030 only on the given timeline, and prepare everything that is not ready yet for a subsequent upgrade.
2. Push back NV16 to an unknown timeline until FIP-0031 is ready for review by the teams.

[raulk]

I'm going to move FIP-0031 out of draft mode, because it's giving the impression that the scope is not locked down, when it actually is. The only reason the FIP is in draft is because I need to fill in some of the non-specification sections and incorporate feedback on the testing plan.

[anorth]

The PR proposing FIP-0031 can certainly be moved out of draft mode. I think the fact that it's in draft is probably a significant turn-off to people reviewing it seriously. I indeed am waiting for a PR that you're ready to merge before giving more thorough review. You can do that without having all the sections complete, if you'll follow up with new PRs to complete the FIP

Note that this is different to the status of the FIP. I don't think it's appropriate to move to Last Call until it's complete. But that can be over multiple PRs.

[jennijuju]

Timeline

[raulk]

@q9f Each testnet has a different characteristics and stability expectations behind it.

• Butterflynet is used for protocol development, it has small sector sizes, and is often reset instead of upgraded.
• Calibnet is a stable testnet and runs closest to mainnet conditions. It is always upgraded, never reset (unless a catastrophic event happens). This is the one that matters the most, and that's why it has a duration of 3 weeks.
• Caterpillarnet is a private, rapid blocktime testnet Lotus is using for internal testing. We encourage other implementations to adopt a similar approach.

The idea is for the Calibnet upgrade to be performed with an RC, ideally with the last one, but we don't know. The RC will be produced as a result of the intensive testing performed on more previous testnets.

[jennijuju]

Adding on what @raulk is saying - technically calibration is the only testnet thats being maintained: https://docs.filecoin.io/networks/#calibration. Agree that - FIPs should be at least in last call, ideally Accepted before deployed to this network.

[jennijuju]

in case its missed from the last core dev call - FIP-0032 won't require work from client implementation.

[kaitlin-beegle]

@jennijuju @raulk Jennifer is right, we don't want calibnet running FIP chanmges that could potentially not be accepted...the calibnet is dress rehearsal for the real upgrade.

My work queue tomorrow is all FIPs -related, so I'l be following up with specifics for FVM FIP last call statuses. There's still plenty of flexibility, however; I don't expect that the FIPs acceptance timeline for FIPs 30/31/32 will be a concern for implementers.

[kaitlin-beegle]

Per last week's Core Devs call, I'm confirming the upgrade timeline as the following:

• Canary Tag v0: March 14
• Butterflynet Upgrade: March 31
• Calibnet Upgrade: April 19
• Mainnet Upgrade: May 10

For additional information, see the FVM test plan.

[kaitlin-beegle]

Name

[raulk]

I'd like to propose one of two themes that have high relevance to the history of this project.

• Portuguese theme: to commemorate where the official FVM kickoff took place, as well as many discussions.
  • LX (abbreviation for Lisbon)
  • Sintra (the place where kickoff happened)
  • Cascais (a beautiful town nearby)
  • Caparica (a stunning coastal area near Lisbon)
  • Funchal (where a Lab Week took place, along with many discussions)
  • Prego (a delicious Portuguese meat sandwich)
• Icelandic theme:
  • Skyr (Icelandic yoghurt)
  • Lagoon
  • Geysir
  • Harpa (the name of the concert hall in Reykjavík)
  • Aurora (Borealis)

My personal choices, in order of preference:

1. Skyr
2. Sintra
3. LX
4. Lagoon

[jennijuju]

my vote on Skyr

[kaitlin-beegle]

I'm not sure of the Iceland reference, but I also vote Skyr....keeps with the standing food theme, and wasn't someone eating a Skyr yogurt on the last Core Devs call???

[jennijuju]

Oh hahahah @kaitlin-beegle for some reason i thought i told you 😂😂 we had a fvm hack week in Iceland that’s why lolol

[kaitlin-beegle]

Per last week's Core Devs call, Skyr it is!

[kaitlin-beegle]

Confirming: 'Skyr' Network v16

Scope

The below FIPs represent those prioritized by Core Devs and FIP Editors. Final implementation is dependent on the successful completion of community Last Call.

FIP0027 - Change type of DealProposal label field from string to byte array (FIP Draft)(Discussion)
FIP0030 - Introducing the Filecoin Virtual Machine (FIP Draft)(Discussion)
FIP0031 - Atomic switch to non-programmable FVM (FIP Draft)(Discussion)
FIP0032 - Gas model adjustment for non-programmable FVM (FIP Draft)(Discussion)

TENTATIVE Timeline*

Canary Tag v0: April 26
Butterflynet Upgrade: May 6
Calibnet Upgrade: May 26
Mainnet Upgrade: June

*Typically, Core Devs confirm a single upgrade timeline. This upgrade timeline is determined at least several weeks prior to the canary tag, and buffer time is incorporated in order to accommodate testing setbacks. However, given the scope and importance of the FVM introduction during the v16 upgrade, we are unable to confirm a single timeline. This upgrade's deadlines are heavily dependent upon complex testing requirements and security audits, and Core Devs will not prioritize planning consistency over network security and functionality.

[jennijuju]

As of May 11th, the butterfly upgrade is targeted in the next two weeks.