M3 Curio PDP Burndown Overview

[rjan90]

This is a ticket to track the minimum items that need to land in Curio before we go out and campaign to the SPX group to update to the latest Curio PDP branch. Items in the original M3 scope that aren't essential for filecoin-pin stability have been moved to #688

List:

• Backport index and ipni pdp tasks to PDPv0 #670
•  feat(pdp): handle extraData in handleDeleteDataSetPiece #673

[BigLep]

Thanks for creating this @rjan90. I've read through the issues and https://filecoinproject.slack.com/archives/C07CGTXHHT4/p1759778230168949 . Lots here.

My biggest worry at the moment is that we're going to be delayed getting #670 out to SPs so we can test IPFS standard tooling retrieval for filecoin-pin. I know that PR needs to get merged first, but if it does and it seems like is #678 is still going to take another half day to land, what are our options? Could we:

1. proceed without PDPv0: uploadAndCreate #678 and followup with another Curio release later in the week?
2. or just have a single provider (e.g., James) use the Curio branch that has Backport index and ipni pdp tasks to PDPv0 #670 and filecoin-pin-website will harccode to that provided at the moment?

From a filecoin-pin perspective #670 is the most important thing. #678 is a very valuable follow (to go from 2 Tx to 1).

---

Slack conversation: https://filecoinproject.slack.com/archives/C07CGTXHHT4/p1759957791113559

[BigLep]

Summary from verbal conversation (which in line with slack thread):

1. rjan90 is finishing build: prep FWSS v0.3.0 release FilOzone/filecoin-services#268 2025-10-08 UTC and then update chore(pdp): M3 Calibnet contract addresses and ABIs #680. chore(pdp): M3 Calibnet contract addresses and ABIs #680 will be there for someone else to review and merge.
2. "filecoin-pin" will ask @TippyFlitsUK to deploy a provider from this branch when chore(pdp): M3 Calibnet contract addresses and ABIs #680 and Backport index and ipni pdp tasks to PDPv0 #670 land. We won't wait for PDPv0: uploadAndCreate #678. filecoin-pin-website will temporarily hardcode this provider.

[BigLep]

Update: @jennijuju and I have downscope this issue only be the essential items for October 15 filecoin-pin website demo. In practice this just means the #670 . By downscoping to this, we don't need to new contracts, don' t have breaking changes, and don't need SPs to re-register. They can just use the new commit.

The items that were bumped out (but were part of the original M3 scope and are still critical) have been moved to #688.

We'll mark this as done once PDP SPs have been given a clear commit to upgrade to.

[BigLep]

@jennijuju : please step in if I'm misdirecting, but @TippyFlitsUK I think it would be great to have you update your pdp SP to use bc716f4 (which has the IPNI indexing/advertising). I assume we'll test with you first and then have other SPs update...

[TippyFlitsUK]

Installed and running at calib.ezpdpz.net:

curio version 1.27.0+calibnet+git_bc716f4_2025-10-08T18:52:22-04:00