Network v18 Scope and Upgrade Timeline

[jennijuju]

Creating this async discussion for core devs to start to propose ntwk v18 upgrades scope.

• High-level theme/priority of the network upgrade, what protocol change we wanna bring to the network, and what use case do we wanna focus on enabling?
• FIPs that should be considered to be accepted & finalized in network v18 to deliver for the above goal.
• Project Timeline including, the month to have the upgrade, ideation cutoff timeline and governance timeline.

[jennijuju]

Scope

Given the soft consensus so far, we expect most FIPs to be finalized in nv18 will be FEVM related.

Latest update: https://github.com/filecoin-project/tpm/discussions/115#discussioncomment-4337719

--------------------------------- DEPRECATED ---------------------------------
Current, the following FIPs/FRC are being considered

Core Dev 👍 :

• evm spec, including runtime, syscall, gas model changes, readonly mode and so on
• account abstraction (discussion, FIP draft)
• FIP-0048: f4 && eam actor (discussion, FIP draft)
• FIP-0049: actor event (discussion, FIP draft
• FIP-0050: public api for built in actor (discussion)
• fevm architecture spec frc
• FIP-0037: Gas model for user-programmable FVM.
• FIP-0047: PoRep policy

Pending

• NEW* FIP-0052: First draft of FIP proposing increased max sector commitment duration FIPs#558: Sector extension duration -> 3.5 yr
• NEW* Revisiting a Sector Duration Multiplier (FIP-0056) FIPs#554 sector duration multiplier
• NEW* New FIP: MarketNotifyDeal called by market actor on proposal clients FIPs#549 MarketNotifyDeal called by market actor on proposal clients

[jennijuju]

we want to propose filecoin-project/FIPs#549. for better foundation of enabling data use cases on Filecoin storage market

[jennijuju]

Dec 7th, 17:07 EST

As communicated here, core devs are now no longer accepting new FIP proposals to be considered for nv18 finalization. (emergency FIPs, i.e: security fixes, are excluded)

Next, core dev will discuss which FIPs/FRCs should/can be finalized in nv18:

Known Scope ✅

• FEVM
  • evm spec, including runtime, syscall, gas model changes, readonly mode, eam and so on
  • account abstraction (discussion, FIP draft)
  • FIP-0048: f4 (discussion, FIP draft)
  • FIP-0049: actor event (discussion, FIP draft
  • FIP-0050: public api for built in actor (discussion)
  • fevm architecture spec frc
  • FIP-0037*: Gas model for user-programmable FVM.
  • FIP-0047: PoRep policy

Pending

• NEW* FIP-0052: First draft of FIP proposing increased max sector commitment duration FIPs#558: Sector extension duration -> 3.5 yr
• NEW* Revisiting a Sector Duration Multiplier (FIP-0056) FIPs#554 sector duration multiplier
• NEW* New FIP: MarketNotifyDeal called by market actor on proposal clients FIPs#549 MarketNotifyDeal called by market actor on proposal clients

[jennijuju]

FIP-0037 covers a lot of gas changes for wasm native measurement, and many of them are not FEVM related. Thus we will descope some of the gas FIP content.

[jennijuju]

Final list of FEVM FIPs

FIP-0048: f4 address class
FIP-0049 : Actor events
FIP-0053: FEVM spec draft
FIP-0037*: Gas model for user-programmable FVM.

[jennijuju]

Final nv18 scope - FEVM
FIP-xxx: Gas Model Adjustment for User Programmability
FIP-0048: f4 Address Class
FIP-0049: Actor Events
FIP-0050: Public API for builtin-actor
filecoin-project/FIPs#569: Filecoin EVM runtime (FEVM)
FIP-0055: Ethereum Accounts, Addresses, and Signatures

[jennijuju]

TImeline

Updated on Dec 1st:

Notes:

1. Currently, the projection is mainly based on the fvm, lotus and actors’ engineering resources & deliverables. Feedbacks from other implementers are welcome!
2. The timeline is planed with the consideration of up coming longer holidays (for both core devs and community).
3. As always, the following dates are subject to change base on engineering developments, testing and readiness.

• Dec 8th: Hyperspace Developer Testnet
• Dec 9th: Scope lock down
• Jan 6th: builtin actor code freeze
• Jan 16th: FEVM audits complete
• Jan 26th: Calibration upgrade
• Mid Feb: Mainnet upgrade

[Fatman13]

Do we have a fixed date on the upgrade yet?

[jennijuju]

We will update the community by EOW, after Thursdays core dev call.

[Fatman13]

Heard that it is decided that mainnet upgrade will be on March 1st? Not sure if the date is solid.

[jennijuju]

Dec 5th - nv18 scope lock down

For engineering and governance planning, core devs are planning to lock down the scope of nv18 before heading into EOY holidays (many core devs will have reduced capacity from Dec 19th to Jan 2rd, 2023). That being said, FIP authors MUST propose any FIP finalization in nv18 to core devs by Dec 7th, 5pm EST for it to be considered. FIP authors may send a scope proposal via:

• this TPM discussion.
• #fil-fips channel (tag @jennijuju).

Notes:

• Above deadlines does not apply to emergency FIPs, i.e: security fix FIPs and so on.
• All proposed FIPs must pass the governance process in order to be finalized in a network upgrade. You can find the the nv18 governance tracker and timeline here.
• Core devs will have the final call on the set of ACCEPTED FIPs that will be finalized in nv18.

[jennijuju]

Upgrade Codename

FVM team has been proposing Hygge, which in danish culture means "finding comfort, pleasure, and warmth in simple, soothing things such as a cozy atmosphere or the feeling of friendship."

&& we did a FVM colo/sprint in Denmark earlier this year so seems fitting 😉

[jennijuju]

Jan 10th, 2023 nv18 scope and timeline update

The final scope of nv18 and its targeted timeline is now available at the community announcement forum filecoin-project/community#74.

tl'dr & notes:

• Current nv18 Hygge scope is to include FEVM-related FIPs solely and targeted to deliver on Mar 1st - Mar 8th.
• Other proposed FIPs, i.e: SDM, FIP-0047 porep security, and so on are considered for nv19, and we aim to ship nv19 in early Q2.
• Core implementers aim to deliver at least one upgrade in Q1 for the filecoin network and community. If FEVM development hits unexpected challenges later on and may slip the Q1 timeline, we will consider switching the focus of nv18 to other Accepted FIPs, and delay FEVM to nv19 (and aim to ship soon after). Further analysis will be conducted to see how this may work.