Skip to content

pdpv0: integrate with main 💪  #822

@BigLep

Description

@BigLep

This is the tracking issue for the steps/work involved with integrating the pdpv0 branch back into main. This is about getting pdpv0 co-existing with eveything else in main. It is not about migrating pdpv0 with marketsV2/pdpv1. That can be a separate workstream.

Notes

Tasks

  • No regression vs pdpv0 baseline (primary signal: Dealbot)
    • Dealbot performance shows no material degradation compared to the current pdpv0 branch
    • No functional regressions observed in:
      • proving
      • onboarding
      • retrieval
  • Core functionality verified (manual checks) - These confirm that the system is behaving correctly beyond automated signals.
    • Proofs are successfully generated and submitted
    • Submitted proofs are accepted without errors
    • No unexpected failures in the proving → verification flow
    • Can onboard data
    • Can serve retrievals
  • Use all approved Calibration SPs to gather confidence
    • All approved Calibration SPs should move to main for this validation period
    • This provides a broader confidence signal than testing against only one or two nodes
  • Sustained stable behaviour
  • Test on mainnet
    • Create release (if needed from new fixes)
    • Have non-endorsed SPs update to RC
    • Confirm no issues for 24 hours.
    • Have endorsed SPs update to RC
    • Confirm no issues for 24 hours
  • Bring over docs changes
  • Bring over any new commits from pdpv0 that hadn't landed in main
    • Log the git commands that were run to confirm not missing anything
  • Make pdpv0 read only
  • (bonus) Address task scheduling between PoRep and PDP: Task Starvation #1137

Metadata

Metadata

Labels

team/fs-wgItems being worked on or tracked by the "FS Working Group". See FilOzone/github-mgmt #10

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions