nv30 Network Upgrade Planning

[ThatGuyLLC]

Note: All information relating to NV29 has been updated in the #205

This discussion will cover the following for nv30:

1. Scope
2. Timing
3. Naming of the Upgrade

[ThatGuyLLC]

Scope

---

Scope

---

FIP/FRC	Link	Status & Progress	Timeline	T-shirt Size	Summary	Notes
🟡 FIP-0119: Increase maximum sector lifetime to 10 years	FIP-0119	Draft; number assigned 2026-10-19; requires FIP-0067 & FIP-0118	TBD; candidate for NV30	TBD	Raises max sector lifetime from 5 to 10 years for PoRep v1.1, Synthetic PoRep and NI-PoRep, applying to existing sectors; no state migration, no change to max extension (1278 days), pledge, PreCommit Deposit, fees or proofs. Also ratifies FIP-0067 margin-erosion trigger	Discussion #1291; needs agreement on the FIP-0067 policy points
🟡 FIP-0117: Repeated SnapDeals with Piece-Level Integrity	PR #1269	Draft (PR open); number assigned 2026-10-09; review comments outstanding	TBD; candidate for NV30	L (Jennifer's estimate)	Lets SPs snap already-snapped CC sectors repeatedly, with opt-in on-chain CommD storage to verify preserved pieces	Discussion #538; utility TBD
🟡 FIP-XXXX: Remove payment channel actor	Discussion #1290	In discussion; no PR in the FIPs repo yet, so no number assigned	TBD; candidate for NV30	TBD	Removes the built-in payment channel (paych) actor entirely	Author: @rvagg. Needs settlement path for any live channels
🟡 FIP-XXXX: Clear State Simply	Discussion #1266	In discussion; no PR or number yet	TBD; candidate for NV30	S (AJ +1)	Removes sector state trees from old miners (IDs created more than 6 months ago) with zero power
🟡 FIP-XXXX: Remove the Fil+ actors (f06, f07, f080)	Discussion #1300	In discussion; opened 2026-10-30; no PR or number yet	TBD	TBD	Removes the Fil+ built-in actors following FIP-0118	Author: @rvagg
⚪ FRC-0120: Filecoin Encryption Envelope	PR #1294	Draft (@Kubuxu, @BravoNatalie); approved for draft, awaiting code-owner reviews	Not tied to a network upgrade	TBD	COSE-based envelope separating encryption metadata from ciphertext; single-shot and seekable chunked AES-256-GCM schemes	Discussion #1253. Open: scheme 1 test vectors, shared 1 MiB prefix-read cap
🔴 FIP-0107: Implicit messages in block receipts	FIP-0107	Accepted; Lotus PR #13539 open, Forest/Venus TODO	Deferred NV29 → NV30; decision at Implementors Call	M	Adds implicit messages (cron, reward) to block receipts; deferred from NV29 for lack of Lotus & Forest bandwidth	Decide: commit to NV30 with named Forest/Venus owners, or defer again
🔴 Fork Signaling Repurposing	FIP-discussion-1221	In discussion; possible, needs bandwidth to implement	Deferred NV29 → NV30; can ship without a network upgrade	S	Uses the unused 64-bit BlockHeader.ForkSignaling field to signal miner software ID, upgrade readiness, actors bundle version and upgrade epoch offset	Not consensus-critical; likely an FRC
🔴 Sealer ID	PR #993	Draft PR open since Apr 2024; not in progress	Deferred NV28 → NV29 → NV30; high-risk, decision at Implementors Call	TBD	Assigns a unique ID to sealers; significant miner-actor change	Decide: re-scope, defer again, or withdraw
🔴 F3 Calibration Smart Contract Activation	F3-issues-1054	Not in progress (implementation issue, not a FIP); F3 restarted on Calibnet 2026-02-12	Deferred NV28 → NV29 → NV30; decision at Implementors Call	L	Lets the F3 activation date be set via smart contract on Calibnet for easier testing and resets	Decide: still needed for NV30 testing, or close

Legend:

• 🟢 Ready for NV30 (no timeline concerns)
• 🟡 Needs review / at risk but possible for NV30
• 🔴 Deferred to NV30 from NV29
• 🟤 Deferred to NV31 (next upgrade)
• ⚪ Not tied to a network upgrade (FRC / client-only)

T-shirt sizes: S < 2 eng-weeks · M 2–4 eng-weeks · L > 4 eng-weeks

[ThatGuyLLC]

Nv29 Timeline

Item	Latest Date	Requirements / Details
Actor code freeze	TBD	Requirements: • Actors PR gets domain expert review from @Kubuxu and @zenground0 • Rod/William audit with Irene • End-to-end integration tests with contracts
Lotus RC for Calibnet	TBD	Requirements: • Actor code freeze • Lotus miner changes • Establish calibration epoch This happens at least one day after the actor code freeze because the new actor bundle needs to be "packed" into Lotus.
Calibnet upgrade date	TBD	Requirements: • Lotus RC • Boost update Usually this is a minimum of +1 week after Lotus RC. We are shrinking the window for this upgrade because we are giving the four key calibration SPs advance notice that the upgrade is coming.
Final Lotus release	TBD	Can happen after a verified successful Calibnet upgrade. Verification will take longer this time because we want to observe behavior after various "quarters" per the test plan currently being drafted. There is concern that one week of testing in calibration may not be enough. We have some flexibility to add a couple of days, but the next step is finishing the testing plan so we can better assess the required window.
NV29 mainnet upgrade date	TBD	Usually there is a minimum of +2 weeks after the Final Lotus release. China Golden Week is October 1–7.

[ThatGuyLLC]

Name of the Upgrade:
Nominations will begin once a closer date has been set.