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.

[rjan90]

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

Hey everyone! 👋

Introducing Fast Finality FIP0086: Fast Finality in Filecoin (F3) is one of the major changes to Filecoin, and is set to bring huge improvements and benefits for the ecosystem by reducing the finality time from 900 epochs to just around 2, and ensuring that “finality” truly means finality. While this change is very important for the ecosystem, it is important that is being delivered safely to the network.

While the Calibration network has been syncing correctly since the F3 activation, and F3 hasn’t caused major outages, and correctly fallen back to EC in the event where the system could not reach a decision. However, we’ve encountered two issues during testing; one happening in the Client/SP code, and the other issue in the F3 protocol:

• GetBestMiningCandidate & F3: This first issue encountered relates to how the system selects the base on which to mine on in some edge cases with F3 (issue #730). For this issue we have a fix ready (PR: 12659) - but given that these changes involve complex and critical code - rushing these changes out just before the final release is unwise, and it is prudent to give this fix more time for testing, before shipping the fix.

• PowerTable Disagreement: F3 protocol encountered a disagreement of the PowerTable of a finalized instance on instance 11912 yesterday (2024-11-05) which caused F3 to stop and fall back to EC. We are currently investigating this and have limited it down to a certain portion of the f3 code, but more time is needed to figure out the fix.

The implementation teams therefore think it is most prudent to suggest that the F3 activation on Mainnet to be delayed until nv25, when implementation teams are certain the testing coverages fully support F3 Mainnet readiness. We will propose to core-devs to schedule nv25 in early Jan, 2025.

To summarize:

• We suggest the nv24 upgrade to happen on the 2024-11-20 and include FIP-0081, FIP-0094 and FIP-0095.
• Once the implementation teams can be certain that F3 is ready for Mainnet, another mandatory release with the final F3 protocol, setting the activation epoch will be published. Current estimates is early January 2025.
• SPs running custom block production code is recommended to check out issue #730 and the fix that is written up in #12659.
  • We need SPs with different geo-locations and significant custom code (apart from the sealing pipeline) to help us testing the final F3 protocol and client code. If you would like to contribute, please DM @Phi-rjan if you want to be a part of that testing.

[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