M3 Curio PDP Burndown Overview

Question

M3 Curio PDP Burndown Overview

Closed this issue a month ago · 7 comments

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:

Answer 1 · 2025-10-08T21:04:54.000Z

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:

proceed without #678 and followup with another Curio release later in the week?
or just have a single provider (e.g., James) use the Curio branch that has #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

Answer 2 · 2025-10-08T22:11:02.000Z

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

rjan90 is finishing FilOzone/filecoin-services#268 2025-10-08 UTC and then update #680. #680 will be there for someone else to review and merge.
"filecoin-pin" will ask @TippyFlitsUK to deploy a provider from this branch when #680 and #670 land. We won't wait for #678. filecoin-pin-website will temporarily hardcode this provider.

Answer 3 · 2025-10-09T05:40:15.000Z

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.

Answer 4 · 2025-10-09T05:42:02.000Z

@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...

Answer 5 · 2025-10-09T12:38:27.000Z

Installed and running at calib.ezpdpz.net:

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

Answer 6 · 2025-10-09T23:50:08.000Z

Note that we don't have end-to-end fully working this M3 for Curio isn't done yet. There are at least the changes in #693 that need to be included. There may be more. The issue description has been updated.

Answer 7 · 2025-10-10T03:50:46.000Z

We have end to end working (although maybe there will be performance or reliability improvements to come)?

Anyways, I'm going to close this issue since we have https://github.com/filecoin-project/curio/tree/pdpM3a for SPs. (**Note the "a". tag "pdpM3" without the "a" will not work. Feel free to use a different tag if that is goings to cause confusion...)