nv 24 Tuk Tuk Network Upgrade Planning

[luckyparadise]

I am already opening this thread to start gathering thoughts and ideas for nv24. This is in the realization of the discussed and agreed pre-scheduled upgrade discussion, you can refer to this.

This thread will cover;

• Scope
• Timeline
• Name of upgrade

[luckyparadise]

Scope

---

• FIP0081: Introduce lower bound for sector initial pledge
• FIP0086: Fast Finality in Filecoin (F3)
• FIP0094: Add Support for EIP-5656 (MCOPY)
• FIP0095: Add EVM precompile to fetch beacon digest

[anorth]

FIP-0081 probably.

[ZenGround0]

I propose including the randomness precompile FIP in scope for nv24: filecoin-project/FIPs#1048

[luckyparadise]

Timelines [Updated 12 September 2024]

---

The timeline here is preliminary and subject to change depending on many factors including engineering constraints, resource allocation, and priorities.

Code freeze: TBC
Calib upgrade: 23 October 2024
Mainnet upgrade: 20 November 2024

[rjan90]

Repost/Summary of the thread in the #fil-implementers channel in Slack:

It was flagged in the implementers’ call that the current nv24 timelines are too short to get fast finality (F3) ready for the calibration and mainnet upgrade dates.

The F3-team did a prioritization and time estimation of the remaining F3 tasks that must be completed before a release can be cut for the rollout to the calibration network upgrade. The estimation shows a time deficit of ~3 weeks (~9 dev-weeks with the 3 engineers working on F3), given the current proposed timelines.

Therefore I would like to propose that the nv24 timelines are adjusted to:

• October 23rd: Calibration network upgrade
• November 20th: Mainnet network upgrade
  • December 4th: F3-activation

Some holidays and major events that I have taken into consideration that has been flagged when setting these upgrade dates:

• National Day Golden Week: Oct 1st -> October 7th
• DevCon / Flagged colo´s by implementer teams: Nov 11th -> Nov 15th
• Thanksgiving - November 28th

Separate F3-activation date

The F3 team is considering scheduling the F3 activation two weeks after the Mainnet upgrade epoch, specifically on December 4th. This delay serves several purposes:

1. Mitigating Holiday/Event Constraints: By setting the F3 activation two weeks after the Mainnet upgrade, we avoid potential disruptions caused by holidays and travelling back from DevCon. This ensures that developers are available and responsive during the activation period.
2. Risk Reduction: The two-week delay allows for passive sanity testing once the entire network has upgraded to the latest F3 release.

[luckyparadise]

Network Upgrade Name

---

[rjan90]

Velocity

[LesnyRumcajs]

Given the number of events in Bangkok in November plus the Velocity above - I propose Tuk Tuk!

[f8-ptrk]

finality

[jennijuju]

Speedy

[jennijuju]

Given the nv22 & nv23 timeline changes, nv24 will be the last upgrade of the year implementers will support. I think it should be our goal to ship f3 (fast finality) this year to unblock cross-chain, interop & l2 integrations for Filecoin storage use cases over bridges, and it would make sense to make nv24 be oriented for f3. "Oriented for f3"

• means all relevant implementers must prioritize developing and testing f3 in q2 if they haven't already.
• if unexpected discovery exists during development, nv24 upgrade dates should be re-evaluated.
• does not mean nv24 should only finalize f3, implementers should evaluate the opportunities and risks of the FIPs set to finalize to determine the scope (as they always do).

If we do not make any changes towards how we do upgrade, for example, still follow pre-scheduled network upgrade, then I'd propose the following schedule for nv24:

• calibration upgrade: Sep 26th, 2024
• mainnet upgrade: Oct 30th, 2024

Implementers ought to consider these dates in their engineering planning and coordinate the support needed for the FIPs that are in the FIP pipeline.

[jennijuju]

updated calibration upgrade date from Oct 1st to Sep 26th per Venus' request, to avoid Chinese golden week holiday (Oct 1st - Oct 7th)

[snissn]

I think it would be possible and highly beneficial to include FIP-0094: Add Support for EIP-5656 (MCOPY Opcode) in the FEVM #1047 pending final approval and merging. Implementation of the FIP is happening here: filecoin-project/builtin-actors#1572

cc and thanks to @rjan90 for helpfully leading me here