nv25 Network Upgrade Planning #183
-
|
I am already opening this thread to gather thoughts and ideas for nv24. In the realization of the discussed and agreed pre-scheduled upgrade discussion, you can refer to this. This thread will cover;
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 21 replies
-
Scope |
Beta Was this translation helpful? Give feedback.
-
|
Potentially in scope is implementing and finalizing FIP-0082, otherwise known as "SuperSnaps". This allows aggregation on SnapDeals proofs in order to allow a group of sector updates to land on chain and be activated all at once. |
Beta Was this translation helpful? Give feedback.
-
|
f3 (FIP-0086) mainnet launch |
Beta Was this translation helpful? Give feedback.
-
|
Given that F3 (FIP-0086) can't be activated in this network upgrade (see announcement here). The nv25 scope needs to be revisited along with the timeline. |
Beta Was this translation helpful? Give feedback.
-
|
I would like to propose that FIP-0097 Add Support for EIP-1153 (Transient Storage) in the FEVM be included in the nv25 upgrade. There is a technical implementation in place for this FIP is in place and currently has technical approvals |
Beta Was this translation helpful? Give feedback.
-
|
Following the cancellation of the upgrade trajectory and nv25 scope (where F3 was the main/only driver) in mid December 2024. Implementers currently believe that these FIPs can be ready for the nv25 timeline, which includes an actor code freeze by the end of February 2025:
I want to point out that there are some risks associated with the exact implementation timelines for the FIPs marked with |
Beta Was this translation helpful? Give feedback.
-
|
After an extended period of Last Call for FIP-0100, it reached consensus in a Core-Devs call to move forward to acceptance, endorsing key changes based on community feedback. See post here for more information: filecoin-project/FIPs#1105 (comment). This means that the scope for nv25 will be: |
Beta Was this translation helpful? Give feedback.
-
Updated February 27, 2025.TimelinesNV25 Upgrade (Q1 2025)
|
Beta Was this translation helpful? Give feedback.
-
|
Following discussions in yesterday's implementers call, implementation teams have estimated that the below proposed timelines are feasible for the outlined scope, provided the FIPs are accepted.
|
Beta Was this translation helpful? Give feedback.
-
|
Multiple groups agreed to postpone the Last Call period for FIP-0100 to Tuesday, March 11th, see message from Danny here. The proposed timelines for nv25 has therefore been pushed out by approximately 1 week:
|
Beta Was this translation helpful? Give feedback.
-
|
With the scope finally finalised for nv25, the proposed timelines for the network upgrade is:
|
Beta Was this translation helpful? Give feedback.
-
|
Implementers have decided to postpone the Calibration and Mainnet upgrade dates by one day. This adjustment allows additional time for finalizing releases, as well as conducting more reviews and checks of the code. The revised upgrade dates are as follows:
|
Beta Was this translation helpful? Give feedback.
-
|
Timelines are going to be updating. Given we are late in the cycle, we'll have one public/broady-visible source of truth for this: filecoin-project/community#74 (comment) |
Beta Was this translation helpful? Give feedback.
-
Network Upgrade NameTeep Upgrade |
Beta Was this translation helpful? Give feedback.
-
|
Raptor |
Beta Was this translation helpful? Give feedback.
-
|
Vroom |
Beta Was this translation helpful? Give feedback.
-
|
Teep, as it's our quick, precise strike to get F3 launched! |
Beta Was this translation helpful? Give feedback.
f3 (FIP-0086) mainnet launch
cc @rjan90