[Tracking Issue] 202608 FOC Release

[BigLep]

Purpose

This issue tracks the work across the FOC stack for the "202608 Release", at least as it pertains to fully delivering contract changes. This includes the the work needed to unblock contract deployments and the resulting changes to take advantage of contract deployments (e.g., Synapse changes).

Timeline

2026-08-24: @BigLep and @martapiekarska are still figuring out the timeline

• ✅ 2026-08-20: Contract code freeze
• ✅ 2026-08-21: Announce PDP and FWSS calibration upgrade
• ✅ 2026-08-25: completing Curio changes
• ✅ 2026-08-25: foc-devnet verification
• ✅ 2026-08-26: Curio release
• ✅ 2026-08-26: Curio rollout to calibration PDP SPs
• 2026-08-24 2026-08-27: Execute PDP calibration upgrade
• 2026-08-27: Synapse RC release (happens automatically with each PR)
• 2026-08-27: filecoin-pin RC release
• 2026-08-27: Execute FWSS calibration upgrade
• 2026-08-28: Announce PDP and FWSS mainnet upgrade
• 2026-08-31: Curio rollout to mainnet PDP SPs
• 2026-09-01: Execute PDP mainnet upgrade
• 2026-09-01: Execute FWSS calibration upgrade
• 2026-09-02: Synapse release
• 2026-09-02: filecoin-pin release

Steps

PDP Calibration Deployment

• Synapse piece-metadata deprecation and release fix: deprecate piece metadata getters synapse-sdk#938
• feat: handle PiecesAddedV2 event dealbot#683
• feat: handle PiecesAddedV2 event filecoin-project/curio#1440
• PDP: integrate new processRemovals function into pdp tasks filecoin-project/curio#1422
• Curio release: https://github.com/filecoin-project/curio/releases/tag/v1.28.5
• Curio rollout to calibration PDP SPs: https://filecoinproject.slack.com/archives/C0AL3C8K11S/p1787766154926809
• PDP Calibration upgrade as tracked in PDPVerifier upgrade from v3.4.0 to v3.5.0 pdp#304

FWSS Calibration Deployment

(Assumes the completed PDP calibration deployment above)

• Anything listed in https://github.com/FilOzone/filecoin-services/milestone/12
  • Improve contract size policy checks #593
• Complete the "essential-to-verify-in-calibration" items from https://github.com/FilOzone/synapse-sdk/milestone/13
  • Update to pricing changes in 1.4.0 synapse-sdk#928
  • Piece metadata stops being accessible on-chain synapse-sdk#917
• Synapse "RC" (happens automatically)
• Stop exposing piece metadata filecoin-project/filecoin-pin#668 | feat!: stop exposing piece metadata filecoin-project/filecoin-pin#683
• filecoin-pin "RC" (happens automatically with chore: add pkg-pr-new workflow for package preview publishing filecoin-project/filecoin-pin#678)
• FWSS Calibration upgrade as tracked in [Release] FWSS v1.4.0 Mainnet Upgrade (includes Calibnet) #588
• Update view contract for price list in synapse [FWSS 1.4.0] After FWSS contract upgrades bump StateView addresses synapse-sdk#945

PDP and FWSS Mainnet Deployment

• chore: validate, notify and if able migrate users of PiecesAdded to PiecesAddedV2 pdp#302
  • feat: handle PiecesAddedV2 event filecoin-project/curio#1440
  • feat: handle PiecesAddedV2 event pdp-explorer#165
• Update to pricing changes in FWSS 1.3.0 synapse-sdk#944 (addressing existing pricing gap)
• Curio mainnet PDP SP rollout
• Dealbot production deployment (for deploying feat: handle PiecesAddedV2 event dealbot#683)
• PDP Mainnet upgrade as tracked in PDPVerifier upgrade from v3.4.0 to v3.5.0 pdp#304
• FWSS Mainnet upgrade as tracked in [Release] FWSS v1.4.0 Mainnet Upgrade (includes Calibnet) #588
• Update view contract for price list in synapse [FWSS 1.4.0] After FWSS contract upgrades bump StateView addresses synapse-sdk#945
• Synapse release: chore(master): release synapse-core 0.9.0 synapse-sdk#941 | chore(master): release synapse-sdk 2.0.0 synapse-sdk#942 | chore(master): release synapse-react 0.4.0 synapse-sdk#943
• filecoin-pin release:
  • Update to latest Synapse release (synapse-sdk@1.2.1) filecoin-project/filecoin-pin#684
  • Migrate to Synapse 2.0 (post 202608 FWSS mainnet upgrade) filecoin-project/filecoin-pin#685

Can happen anytime

• @BigLep add @Kubuxu to multisig signers
• Remaining Synapse items from https://github.com/FilOzone/synapse-sdk/milestone/13
  • For AddPieces where all metadata is empty in a batch, use compact metadata synapse-sdk#927
  • Select compact datasets with priority synapse-sdk#925
  • Stateful batching synapse-sdk#922
  • Call out benefits of the new dataset storage synapse-sdk#931
  • Update batcher limiter for old datasets synapse-sdk#932
• Synapse release with the items above

[Kubuxu]

FilOzone/synapse-sdk#917 and FilOzone/synapse-sdk#926 are dupes, that is on me.
Ideally, that should happen before FWSS Mainnet is upgraded, but it could happen afterwards.

[Kubuxu]

foc-devnet run over here: FilOzone/foc-devnet#180
It generally succeeds, but one scenario fails at the second copy step due to insufficient locked funds.
This should be addressed by FilOzone/synapse-sdk#928

FWSS PRs that cause it: #583 #592

Increasing the amount of USDFC in the foc-devent user setup resolved the issue.

[BigLep]

The issue description has been updated to call out steps I was missing previously:

• Curio releases
• Curio PDP SP rollouts
• Synapse releases
• filecoin-pin releases

I am still working to understand the timeline better.

[BigLep]

Digging in on the Synapse side, here is my current understanding based on slack conversation:

Functionality	Impact if released before contract upgrade	Impact if not present in a release after contract upgrade	Plan concerning Calibration upgrade
Piece Metadata removal	None. Client is not using functionality that is still supported until contract upgrade. Basically the client will handle the breaking change, which they would have had to do at some point anyway.	Clients attempting piece metadata will have failed calls.	In will land before calibration upgrade for foc-devent testing.
Pricing changes	Users will see wrong pricing. Things should continue working, unless users are riding right on the edge of their budget.	Higher-level applications (like filecoin-pin) might fail to ask the user to top up or top up automatically.	In will land before calibration upgrade for foc-devent testing.
Batching	Need to make a code change to reduce static caps. The caps could be increased after contract upgrade.	Clients not taking advantage of batching optimizations. Things are no worse than before.	It will likely land after calibration upgrade. It will be in an feature/RC branch but not in a published normal release.

I think we ideally want a RC branch/release that these features are accumulating into for calibration testing and for mainnet apps to build against in preparation for the mainnet upgrade. After the mainnet upgrade we do a full/normal Synapse release, which should be a no-op for anyone who has already been tracking the RC.

[BigLep]

We had an extended breakout about this today and walked through all the steps and updated the dates in the issue subscription. It's possible we may be able to pull in a day or two, but it's also possible we hit snags with foc-devnet verification or PDP SP rollout, so I have left the current best guess dates.

---

This is other chicken scratch notes from the meeting that I need to cleanup. I'll do so 2026-08-26 with fresh eyes, when I can also review my Granola notes to make sure I didn't miss anything from the conversation.

• We'll do metadata note about deprecated Synapse methods for piece metadata
• Batching: Need a batching item for the dataset ids to switch over (synapse#932)
• TODO: create Issue in filecoin-pin for updating to latest synapse that was release today 2026-08-25.