nv27 Network Upgrade Planning

[BigLep]

Note: All information relating to NV27 has been updated in the Network Updates Repo

This discussion will cover the following for nv27:

• Scope
• Timeline
• Name of upgrade

What about nv26?

Public planning is happening for nv27 instead of nv26 since nv26 is use to implement the 90 day grace period discussed in FIP-0100:

There will be a 90-day grace period after this FIP's activation during which old sectors that are extended will not incur the fee. After the grace period, extensions will cause old sectors to start paying the fee. The grace period uses the network version mechanism.

[BigLep]

Scope

---

Context:
This table summarizes the revised Network Upgrade (NV27) FIPs queue discussed during Core Devs Meeting 82.
It reflects the latest status, timeline considerations, and prioritization of proposals based on Core Devs 82 discussions.

Tentative Timeline:
The NV27 upgrade planning starts with a target code freeze date of August 31, 2025.

---

FIP/FRC	Link	Status & Progress	Timeline	Summary	Notes
🟢 FIP-0105: Add BLS12-381 precompiles to FEVM	FIP-0105	PR open; performance concern on 2MB WASM increase resolved here	No concerns for NV27	Adds ~2MB to EVM actor compiled WASM; improves cryptographic capabilities	Slack discussion
🟢 FIP-0103: Remove ExtendSectorExpiration method	FIP-0103	PR opened, reviewed, merged	No concerns for NV27	Removes deprecated method, replaced by ExtendSectorExpiration2 already in use	Straightforward removal
🟢 FIP-0106: Remove ProveReplicaUpdates method	FIP-0106	PR opened, reviewed, merged	No concerns for NV27	Second of three removal FIPs in NV27; straightforward	Already accepted
🟢 FIP-0077: Add deposit requirement for new miner creation	FIP-0077	All feedback resolved; ready to move from last call to accepted	No concerns; minor changes possible by month-end	Adds 5 FIL deposit for creating new miners; spam prevention	Deposit reduced from original proposal
🟢 FIP-0101: Remove ProveCommitAggregate method	FIP-0101	Third and final removal FIP in NV27; already accepted	No concerns for NV27	Removes deprecated parameters	Straightforward removal
🟢 FRC-0108: F3-compatible snapshots	FRC-0108	Ready for NV27; Forest team ready by end of August; testnet phase planned	No concerns	Standardizes format for F3 data loading; backward compatible; not a protocol change but requires network upgrade	Ensures all nodes support new snapshot format
🟢 FIP-0109: Smart contract notifications for Direct Data Onboarding (DDO)	PR #1180	Potential for NV27 if reviewed in time; flagged to FIP editors	Low risk; minimal integration	Enables DDO-related smart contract notifications; unlocks marketplaces, DAOs, data apps	Waiting for 2 FIP editor reviews
🔴 FIP-0107: Implicit messages in block receipts	FIP-0107	Deferred to next upgrade	Misses August deadline	Would allow implicit messages in receipts; deferred due to lack of bandwidth in Lotus & Forest	Update to be posted in GitHub discussions
🔴 Sealer ID	PR #993	Deferred; implementation specs still WIP	High-risk; deferred	Assigns unique ID to sealers; significant miner-actor change	Needs extensive testing; timeline too short

Legend:

• 🟢 Ready for NV27 (no timeline concerns)
• 🟡 Needs review / at risk but possible for NV27
• 🔴 Deferred to next upgrade

[Tanisha-fil]

Subject to the implementation being completed in time, FIP: Introducing Sealer ID (filecoin-project/FIPs#993) is also queued for the network upgrade.

[BigLep]

I updated the table with my 2025-07-22 understanding:

Item	URL	Implemented as of 2025-07-22	Ability to trigger a network upgrade train.	Other Notes
FIP-XXX: anything needed for PoRep in FS	Unlock sector content notifications to arbitrary actors (draft text), Exposure of Sector Status Method to Smart contracts from Builtin Miner Actor (discussion)	No	Yes if writing and implementing the FIPs was something the FS Working Group was shooting for before FDS-7.	Due to priorities and resource constraints, the FS Working Group doesn't think it can do this work in time. It is currently planning to just get the FIPs written and accepted, but not push to implement them for nv27.
FRC-0108: F3-aware snapshot format	https://github.com/filecoin-project/FIPs/blob/master/FRCs/frc-0108.md	Implementation is well underwary, but not finished yet. See tracked items from ChainSafe/forest#5627	No, but should go out in the next network upgrade so node implementations can switch over to a snapshot format that is F3-aware.
FIP-0105: Add Support for EIP-2537 (BLS12-381 Precompiles) in the FEVM	https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0105.md	filecoin-project/builtin-actors#1669	At the minimum it should go out in the next network upgrade. It could help drive if for some reason this gap from the EVM becomes an ecosystem inhibitor.
FIP-0107: Implicit Messages in Block Receipts	https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0107.md	No	Likely not since it isn't needed to enable PoRep in "FS".	It would still be very useful to have!F. ilOz isn't planning to pick it up before FDS-7 and is not aware of another team wants/can (although it would be great if some other group did).
FIP-0101: Removal of the ProveCommitAggregate method from the miner actor	https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0101.md	Awaiting review in filecoin-project/builtin-actors#1691	None. It'll just go out with whatever is the next train.
FIP-0103: Removal of the ExtendSectorExpiration method from the miner actor	https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0103.md	Awaiting review in filecoin-project/builtin-actors#1690	None. It'll just go out with whatever is the next train.
FIP-0106:Removal of the ProveReplicaUpdates method from the miner actor	https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0106.md	Awaiting review in filecoin-project/builtin-actors#1688	None. It'll just go out with whatever is the next train.
FIP-0077: Add Cost Opportunity For New Miner Creation	https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0077.md	filecoin-project/builtin-actors#1535	Most likely not unless we get more miner creation spam. It would go out with the next train (after being implemented).
FIPXXXX: Introducing sealerID	filecoin-project/FIPs#993	Started in filecoin-project/builtin-actors#1683	Maybe, if critical for unlocking new ecosystem business?	None

[BigLep]

For visibility, @Tanisha-fil updated the top of the "Scope thread" with the current proposal.

[Tanisha-fil]

For visibility, I have updated the top of the discussion with a link to the Network Updates repo where all information relating to NV27 sits.

[BigLep]

For visibility in case there anyone watching here who isn't watching #fil-implementers, it's possible we'll need drop FIP-0077 because the end-to-end implementation is ready to go currently and might not be in time for the Lotus RC cutoff date. See https://filecoinproject.slack.com/archives/C05P37R9KQD/p1756832700663399

[BigLep]

Timelines (Tentative and requesting for review)

---

Item	Date	Note
Actor code freeze	2025-08-29 2025-09-02	Usually there is a minimum of +2 weeks after FIP Last Call.
Lotus RC for Calibnet	2025-09-03	+1 week? (If needed and tentative)
Calibnet upgrade date	2025-09-10	Usually this is a minimum +1 week after Lotus RC.
Final Lotus release	2025-09-11	Can happen after a verified successful Calibnet upgrade.
nv27 mainnet upgrade date	2025-09-24	Usually there is a minimum of +2 weeks after Final Lotus release.
Chinese golden week	2025-10-01 - 2025-10-08

[BigLep]

Thanks for the feedback @beck-8 .

This upgrade is not light.

I'm curious what you're seeing in the scope that is leading to this. I have been thinking that:

1. there isn't any significant migration here and
2. limited new functionality is being added

[beck-8]

I can't interfere with your ideas. Hopefully no problems will occur.

[beck-8]

I just want him to land more smoothly. If you have your KPI requirements, just follow your time.

[Tanisha-fil]

@beck-8 — Noted that there won't be any squeezing upgrades into holiday windows. If there are any complications, we automatically postpone to avoid holiday stress.

It's a simple cliff rule:

1. If we can meet the September 24th timeline = proceed
2. If there are any slippages = defer to post-Golden Week (mid-October+)

My KPI is momentum for the network when safe, respect for holidays when it's not safe. :) Thanks for bringing this up!

[BigLep]

Per #fil-implementers thread, the actors code freeze will need to bump back to Tuesday, 2025-09-02. We currently still believe we can hit the as-proposed 2025-09-03 Lotus RC date, but it does increase the chance that we find an issue in the week window before the 2025-09-10 Calibration upgrade, which would cause pushing back that date (potentially bumping us out past Chinese Golden Week). I believe we are fine with the risk because the ramification for being "wrong" is acceptable (i.e., dates move but don't interfere with Chinese Golden Week). I updated the top of the thread.

[BigLep]

Network Upgrade Name - Golden Week Upgrade

[Tanisha-fil]

I'm inviting people to vote between @jennijuju's and my proposal for naming convention. Simply mark 👍🏻 to whichever options you prefer.

Note 1: If you mark 👍🏻 to @jennijuju's comment, please also specify which of the 3 sub-names you like most.

Note 2: Due to time constraints, at 00:00 UTC on 29th August, we will pick the most 👍🏻 option. Thanks

Note 3: I moved my original post from the initial thread post to the comment above so that it's easier to vote between the 2 comments.

Thanks!

[BBQFIL]

NV27 Naming Proposal: “Golden Week” 💰

Proposal Rationale:

1. Timing Alignment: The NV27 upgrade is scheduled to start one week before China’s Golden Week (target code freeze date: August 31, 2025), making the name relevant and easy to remember.

2. Symbolic Meaning: “Golden Week” represents prosperity and a highlight period, reflecting NV27’s multiple improvements and its contribution to the Filecoin network’s robustness and ecosystem growth.

3. Memorable: The name is concise, distinctive, and easy to reference in discussions and documentation.

---

NV27 命名提议：“黄金周”💰

提议理由：

1. 时间契合： NV27 升级计划在中国黄金周前一周启动（目标代码冻结日期：2025年8月31日），名称贴切且易于记忆。

2. 象征意义： “黄金周”象征繁荣与亮点，体现了 NV27 的多项改进及其对 Filecoin 网络稳健性和生态系统发展的贡献。

3. 易于记忆： 名称简洁、独特，便于在讨论和文档中引用。

[Tanisha-fil]

For everyone's visibility, the timing to vote has been corrected to 00:00 UTC on 29th August, not 28th August. Thanks!

[BigLep]

I like the "golden week", particularly given its temporal alignment to Chinese Golden Week as compared to Argentina activities in November.

One way to potentially bridge the two is "Golden Semana" (where Semana is Spanish for week). This has the properties of:

1. Nods to "Chinese Golden Week" and "Argentina"
2. Avoids any confusion with the actual "Chinese Golden Week"

[Tanisha-fil]

Hello everyone,

We have finalized the name with the maximum 👍🏻

The winner is Golden Week, proposed by @BBQFIL. We are locking that in for the network upgrade 27! Thank you to everyone who participated. 🤍

[BigLep]

Other

---

[BigLep]

FYI that I created this discussion because:

1. It's a post network upgrade cleanup step for nv25
2. I wanted a place to start marking items that should be in scope for nv27.

Even though I was the "discussion creator" here, I shouldn't be viewed as the network upgrade coordinator/driver. I assume the Filecoin Foundation (e.g., @Tanisha-fil) to play more of that role (related slack thread).

[Tanisha-fil]

From my side,

FIP 0101 and FIP 0082 are the two FIPs that are "Accepted" but not "Final". If there are no objections, I would prioritize adding them to the NV'27 upgrade. I'll add more FIPs in the pipeline as I clean up statuses and drafts this week, but just wanted to scope this pipeline in the open.

Links:
FIP 0082: https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0082.md
FIP 0101: https://github.com/filecoin-project/FIPs/blob/master/FIPS/fip-0101.md

[Tanisha-fil]

Context:
This table summarizes the revised Network Upgrade (NV27) FIPs queue discussed during Core Devs Meeting 82.
It reflects the latest status, timeline considerations, and prioritization of proposals based on Core Devs 82 discussions.

Tentative Timeline:
The NV27 upgrade planning starts with a target code freeze date of August 31, 2025.

---

FIP/FRC	Link	Status & Progress	Timeline	Summary	Notes
🟢 FIP-0105: Add BLS12-381 precompiles to FEVM	FIP-0105	PR open; performance concern on 2MB WASM increase resolved here	No concerns for NV27	Adds ~2MB to EVM actor compiled WASM; improves cryptographic capabilities	Slack discussion
🟢 FIP-0103: Remove ExtendSectorExpiration method	FIP-0103	PR opened, reviewed, merged	No concerns for NV27	Removes deprecated method, replaced by ExtendSectorExpiration2 already in use	Straightforward removal
🟢 FIP-0106: Remove ProveReplicaUpdates method	FIP-0106	PR opened, reviewed, merged	No concerns for NV27	Second of three removal FIPs in NV27; straightforward	Already accepted
🟢 FIP-0077: Add deposit requirement for new miner creation	FIP-0077	All feedback resolved; ready to move from last call to accepted	No concerns; minor changes possible by month-end	Adds 5 FIL deposit for creating new miners; spam prevention	Deposit reduced from original proposal
🟢 FIP-0101: Remove ProveCommitAggregate method	FIP-0101	Third and final removal FIP in NV27; already accepted	No concerns for NV27	Removes deprecated parameters	Straightforward removal
🟢 FRC-0108: F3-compatible snapshots	FRC-0108	Ready for NV27; Forest team ready by end of August; testnet phase planned	No concerns	Standardizes format for F3 data loading; backward compatible; not a protocol change but requires network upgrade	Ensures all nodes support new snapshot format
🟡 FIP-0109: Smart contract notifications for Direct Data Onboarding (DDO)	PR #1180	Potential for NV27 if reviewed in time; flagged to FIP editors	Low risk; minimal integration	Enables DDO-related smart contract notifications; unlocks marketplaces, DAOs, data apps	Waiting for 2 FIP editor reviews
🔴 FIP-0107: Implicit messages in block receipts	FIP-0107	Deferred to next upgrade	Misses August deadline	Would allow implicit messages in receipts; deferred due to lack of bandwidth in Lotus & Forest	Update to be posted in GitHub discussions
🔴 Sealer ID	PR #993	Deferred; implementation specs still WIP	High-risk; deferred	Assigns unique ID to sealers; significant miner-actor change	Needs extensive testing; timeline too short

Legend:

• 🟢 Ready for NV27 (no timeline concerns)
• 🟡 Needs review / at risk but possible for NV27
• 🔴 Deferred to next upgrade

[Tanisha-fil]

No, we discussed end of August code-freeze.

[jennijuju]

right - but you also suggested “the upgrade in tentatively planned for end of August” - we can’t code freeze and upgrade at the same time. What’s the timeline for calibration testnet upgrade and mainnet upgrade after code freeze?

[Tanisha-fil]

Right - but I've clarified that when we discuss in the context of "Network Upgrade 27", we are starting with a target code freeze date of August 31, 2025.

@rjan90 - Correct me if I'm wrong, but we discussed that the mainnet upgrade is approximately 2 months after the code freeze, assuming all tests go smoothly?

[BigLep]

Per slack discussion, lets:

1. Move the proposed scope table to the scope thread
2. Move the proposed timeline discussion to the timeline thrad
3. Expand the timeline to callout the key events after actor-code freeze (e.g., Lotus RC, calibration upgrade, Lotus final release, mainnet upgrade date)

[Tanisha-fil]

Hi @BigLep

This is done. Requesting a review on the timeline thread if I am missing anything (given this is the 1st time I am doing this, apologies for any errors)

[Derek-zd]

建议将主网升级时间设置在 11 月 1 日之后