nv22 Network Upgrade Planning #148
-
|
Updated 8 April 2024. I am already opening this thread to start gathering thoughts and ideas for nv22. This is in the realization of the discussed and agreed pre-scheduled upgrade discussion, you can refer to this. This thread will cover;
Updated 8 April 2024
Timeline: Name: |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 23 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Projects that were descoped from nv21 due to implementers's bandwidth and governance timeline constraints should be prioritized (not ranked in particular order):
In addition, FIP-0070 was descoped from nv21 last minute due to critical protocol implementation design bugs. FIP authors should iterate on the FIP itself (see some guidance here), implement and test it again, for consideration. Implementers should discuss the privatization here as well, i.e: whether the protocol should be simplified before even considering changing anything in this area of code and be confident it could be done safely. |
Beta Was this translation helpful? Give feedback.
-
|
The FIP for filecoin-project/FIPs#847 when it gets a number |
Beta Was this translation helpful? Give feedback.
-
|
We've been working towards getting the fast finality extensions (filecoin-project/FIPs#809) ready, as it would be great to get them into production rather than later. However, as it stands, it doesn't look like we'll be able to meet the code freeze deadline. We'll keep an eye out anyway, in case things move unexpectedly fast on our end or the nv22 deadline gets extended. |
Beta Was this translation helpful? Give feedback.
-
|
The FIP for filecoin-project/FIPs#903 when it gets a number |
Beta Was this translation helpful? Give feedback.
-
Timelines [UPDATED 8 April 2024]The timelines here are preliminary and subject to change depending on many factors including engineering constraints, resource allocation, and priorities. Code freeze - 1 Feb |
Beta Was this translation helpful? Give feedback.
-
|
Given Chinese New Year break, I am proposing the revised timeline below; All FIPS in-scope should enter Last Call by 15 Jan cc: @jennijuju @steven004 |
Beta Was this translation helpful? Give feedback.
-
|
Implementing teams have proposed a slight revision to the timeline for nv22 Watermelon Upgrade as a result of some technical delays in testing and other issues. Revised dates have been proposed above and more information can be found here - https://filecoinproject.slack.com/archives/C05P37R9KQD/p1706795430682699 |
Beta Was this translation helpful? Give feedback.
-
|
Implementers have encountered delays in migrating Direct Data Onboarding and therefore the various teams will need additional time for revisions to land correctly. Hence the teams have agreed on a revised timeline for nv22. Calibnet - March 6 2024 See more here - #166. |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: Based on the FIL-Implementers' discussion, the date for calibinet upgrade has been moved to 11 March 2024. |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: The implementer teams have agreed to postpone the nv22 mainnet date to 24 April 2024. For more information check this out - https://filecoinproject.slack.com/archives/C01AC6999KQ/p1712549942096779 |
Beta Was this translation helpful? Give feedback.
-
Network upgrade name |
Beta Was this translation helpful? Give feedback.
-
|
Let me kick-start this. I suggest Aurora because this upgrade will introduce significant changes and improvements. Another suggestion is Apollo as some of the FIPs being considered are exploratory, groundbreaking and pioneering a new journey for the ecosystem. |
Beta Was this translation helpful? Give feedback.
-
|
Dragon Upgrade! |
Beta Was this translation helpful? Give feedback.
-
|
We had an implementer sync today, and the following FIPs are the ones that implementers will prioritize support and targeting to ship in nv22 (assuming all FIPs accepted by the community)
The following FIPs will be supported in later upgrades. On FIP0081: Introduce lower bound for sector initial pledge, Forest team will have code implemented in builtin actor in a feature branch. However, we will let the governance process play along here before committing to any network upgrade finalization. The original author, members from Venus team, has suggested it might be the best to revert FIP0070: Allow SPs to move Partitions between deadlines back to Draft, and go through more community iterations cc @luckyparadise . Given this fip has proven that the existing protocol is too complicated to introduce enhanced feature, it might be beneficial if someone (maybe Venus team) to spend some cycle on looking into the post scheduling & expiration queues and see if the protocol can be simplified first. All three implementers has agreed that Faster Finality in Filecoin is one of the top priority project for the network as it unblock various ecosystem opportunities on Filecoin network. However, it is challenging to deliver and have the implementation well tested and audited within the proposed timeline and we believe we should NOT block other features to ship to the network b/c of F3. That being said, we believe F3 is likely out of scope for nv22. However, all implementers will (continuously to) allocate resources to prioritize implementing this in the upcoming January and aim to ship F3 as soon & secure as possible (the F3 project team has already been 👩💻 this for the past couple weeks). We would like to explore the idea to have a sooner f3-dedicated nv23 upgrade. If you would like to work with implementers and contribute to Fileocin protocol development, join us at Filecoin Slack #fil-implementers! It has been another packed year with 3 major upgrades including the launch of FVM! Both Lotus and Forest team will be on ❄️ holidays soon to take a well deserved break to recharge and be ready for 2024! To those who are also taking the holidays, hope you have some fun and relaxing time with the love ones! And we will talk to y'all next year! |
Beta Was this translation helpful? Give feedback.
-
|
F3 must be in nv22.Due to slow transaction confirmation, the user experience of Defi is very very bad.Even the upgrade can be delayed due to F3. |
Beta Was this translation helpful? Give feedback.
-
|
@jsoares I agree in principle with you for the FIP to be rejected and we put together a new FIP. The problem with that approach is versioning and open documentation. What I mean is that the community had already 'Accepted' the FIP as is and we have openly communicated its acceptance as well as updated all records. At the moment, we don't have a process whereby we retract the acceptance of a FIP even if such FIP is technically flawed. And it is not best practice for me to casually change its status from accepted to rejected without community intervention. |
Beta Was this translation helpful? Give feedback.
-
|
It needn't be you changing the status without community intervention. Per the wording in FIP-0001, Core Devs can move a technically broken FIP to |
Beta Was this translation helpful? Give feedback.
-
|
Sure @jsoares . I want to also clarify that the FIP being Accepted does not mean it has to be implemented. I think it is a matter of status-tagging. Could we leave it as is until a new FIP is written up and presented to the community for consideration? At which time we can make the necessary status changes? |
Beta Was this translation helpful? Give feedback.
-
|
I'm not going to die on this hill, and I defer to you on the way forward (provided it's consistent). Still, there is a fundamental difference between something not being implemented and something not being implementable. This FIP is broken, and, in my opinion, should be clearly marked as such. Keeping it accepted and tagging it as deprecated in the future suggests, for the eternal record, that it was, for some time, part of the protocol, and that's just not accurate. |
Beta Was this translation helpful? Give feedback.
-
+1 on this. The fip is known to be unsecured to be finalized in the network and should be rejected or reverted to be DRAFT snd go through the FIP review process again imo. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @jennijuju I shared more thoughts on this here - #148 (reply in thread). A FIP being Accepted does not mean it has to be finalized (two different stages in the current FIPs process). Let us get a new FIP to address the concerns with the old one and we can simply update the status of the old one to something like "Dependency" or anything else. |
Beta Was this translation helpful? Give feedback.
-
|
As requested by implementers, we have revised the date for mainnet upgrade for nv22 to 11 April 2024. All docs have been updated above. |
Beta Was this translation helpful? Give feedback.
Dragon Upgrade!