Network v19 Scope and Upgrade Timeline

[jennijuju]

Creating this async discussion for core devs to start to propose ntwk v19 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 v19 to deliver for the above goal.
Project Timeline including, the month to have the upgrade, ideation cutoff timeline and governance timeline.

[jennijuju]

Scope

FIPs that are being considered

• FIP-0047: PoRep Security Policy
• FIP-0052: Sector extension duration -> 3.5 yr
• Revisiting a Sector Duration Multiplier (FIP-0056) FIPs#554 sector duration multiplier

[jennijuju]

@luckyparadise yes on grind ability fix for sure

[luckyparadise]

@jennijuju question- FIP0047 is still considered in scope from eng perspective no?

[jennijuju]

@jennijuju question- FIP0047 is still considered in scope from eng perspective no?

Nope - I’m not prioritizing it.

[jennijuju]

Due to filecoin-project/builtin-actors#1276 - Lotus and actor maintainers want to strongly propose to delay the finalization of filecoin-project/FIPs#673.
Main reason is to make the discrepancy created by the regression smaller. Also the benchmarking of batch balancer cross over and gas fees shall be updated with the new FIL+ operational gas cost with both FVM m1 and FIP0045 taken into consideration - ideally these should be captured in a new FIP. See the comments here.

[luckyparadise]

Hello!

Here is an updated list of FIPs considered in-scope for nv19- Lightning Upgrade;

• FIP0060: Set market deal maintenance interval to 30 days
• FIP0061: WindowPoSt Grindability Fix
• FIP0062: Fallback Method handler for Multisig and payment Channel Actors

You can find more information in the FIPs tracking here.

[jennijuju]

Timeline

Currently targeted at early Q2.

March 20th update- targeted timeline

• Apr 6th: all scoped FIPs are accepted & may enter code freeze
• Apr 12th: calibration upgrade
• May 3rd: mainnet upgrade

[jennijuju]

@luckyparadise would that work from a governance perspective ?

[luckyparadise]

@jennijuju this sounds perfect! We will have all in-scope FIPs scheduled for Last Call this Thursday! A Team!

[jennijuju]

@luckyparadise cool! updated #123 (comment) !

[kaitlin-beegle]

Updated timeline, according to revised governance update:

• Apr 18: calibnet
• May 9: mainnet v19
• May 11: mainnet v20

[kaitlin-beegle]

Updated (and final) timeline, due to yesterday's Core Devs governance deliberation.

Apr 18: calibnet
May 9: mainnet v19
May 16: mainnet v20

[jennijuju]

Network upgrade name

Proposing Lightning ⚡ - smaller cron -> faster validation!

[jennijuju]

proposing Thunder ⚡ for the nv20 ghost upgrade

[Derek-zd]

nv20 ? where is nv19?

[kaitlin-beegle]

Hey @Derek-zd! Great question- it's honestly a bit confusing.

nv19 (the Lightning Upgrade ⚡) will go live on May 9 and will include all accepted FIPs. One of these FIPs- FIP0061- introduces a change to the Filecoin proofs system. Because of this, the proofs system needs to be "reset", so to speak, which will technically require us moving onto a new network version. This will be nv20 (the Thunder Upgrade 🌧️).

However, these dual upgrades are really just a technicality. nv19 will introduce new actors versions, all FIPs, etc., and require SP hardware upgrades (as usual). nv20, which will arrive a week later, will effectively be a "ghost" upgrade that does not require any migrations, downtime, etc. However, technically speaking, between May 8 and May 17, the Filecoin community will move through two separate network changes.

Does that make sense?

[kaitlin-beegle]

Finalizing the nv19 will be the Lightning Upgrade ⚡ and nv20 will be the Thunder Upgrade 🌧️

[Derek-zd]

Hey @Derek-zd! Great question- it's honestly a bit confusing.
nv19 (the Lightning Upgrade ⚡) will go live on May 9 and will include all accepted FIPs. One of these FIPs- FIP0061- introduces a change to the Filecoin proofs system. Because of this, the proofs system needs to be "reset", so to speak, which will technically require us moving onto a new network version. This will be nv20 (the Thunder Upgrade 🌧️).
However, these dual upgrades are really just a technicality. nv19 will introduce new actors versions, all FIPs, etc., and require SP hardware upgrades (as usual). nv20, which will arrive a week later, will effectively be a "ghost" upgrade that does not require any migrations, downtime, etc. However, technically speaking, between May 8 and May 17, the Filecoin community will move through two separate network changes.
Does that make sense?

oh,I see. Thank you.

[ZenGround0]

Hey core devs

nv19 includes FIP 0060 which will greatly reduce block sync times. Due to the recent degraded chain quality, the lotus team is advising an expedited nv19 to land this change sooner.

Long block sync times continue to create problems that present in various ways throughout the network.  The latest seemingly related problem is a delay in block production that is causing a decrease in chain quality.  Concretely this means (1) SPs are missing blocks and losing out on revenue and (2) chain message bandwidth is significantly reduced.  Note that long block sync times are probably not the only contributing factor and it is still only a hypothesis that they are a significant factor.  However we have enough confidence in the hypothesis that reducing block sync time will significantly improve chain quality that it appears worth the cost to expedite the nv19 upgrade.

In order to expedite safely we need to reduce the scope of the upgrade to make up for the shorter testing and node update period.  To do this we are advising:

• removing the activation bug fix from nv19.  This removes the vast majority of migration work and therefore upgrade risk.  The network has until Feb 2024 to fix this issue.
• postponing FIP-0052 Extend sector/deal max duration to 3.5 yr to the next upgrade. FIP 0052 depends on this fix to maintain protocol security invariants, so it will have to be reverted too under this plan.
• increasing the time between nv19 and nv20 upgrades to 3 weeks from 1 week in order to give SPs more time to transition to FIP 0061 window PoSt proofs.

Code for this descoped upgrade is currently under test and found here: filecoin-project/lotus#10681

[jennijuju]

@Fatman13 This is a decentralized network and I think it is everyone's job to ensure network is healthy. While FF/core devs should be doing the heavy lifting to align network upgrade updates across the community, and implementation teams should actively bring their users up to speed - its also community's responsibility to outreach each other with the latest network upgrade information to ensure high uptime of the overall network service.

[Fatman13]

Sorry, I didn't mean community should not come together to push for a successful network upgrade, but rather as @q9f has pointed out that the proposal is about an out of norm upgrade timeline which may very well result in a great success and the core devs deserve all the flowers and praise for that, however there is also a slight chance that things may go south (in case of a big chunk of SP missing the upgrade time and network gets congested with recover messages which in turn pushes basefee even higher for a prolonged period of time). In that case, shouldn't the core devs be taking some of the responsibilities just like how SP takes responsibilities by getting slashed for missing windowPost?

[luckyparadise]

@jennijuju do we have a date for the Thunder upgrade?

[arajasek]

Exactly 3 weeks after the Lightning upgrade! 18th May, 13:00:00Z.

[jennijuju]

@jennijuju do we have a date for the Thunder upgrade?

nv19 - 2023-04-27T13:00:00Z at epoch 2809800
nv20 - 2023-05-18T13:00:00Z at epoch 2870280