chore(deps): update dependency filozone/pdp to v3.5.0

[renovate]

This PR contains the following updates:

Package	Update	Change
FilOzone/pdp	minor	v3.4.0 → v3.5.0

---

Release Notes

FilOzone/pdp (FilOzone/pdp)

v3.5.0

Compare Source

This release upgrades the deployed PDPVerifier contract with compact piece storage, resumable piece deletion processing, compact PiecesAddedV2 events, scheduled-removal events, and delay-based upgrade announcements.

Storage-provider integrations must process pending piece deletions before advancing a proving period. Event consumers must support PiecesAddedV2; the legacy PiecesAdded event remains in the ABI but is no longer emitted.

Deployed

The implementation contracts were deployed from commit cc3f5eaffee7df80471b671a4e35a42b000685b8. The v3.5.0 release tag points to the later documentation-only commit that finalizes these release notes.

Mainnet:

• PDPVerifier Implementation: 0x04D4CdB99E34D7e9a366E7eba7A835e034bc41b1
• PDPVerifier Proxy: 0xBADd0B92C1c71d02E7d520f64c0876538fa2557F
• Implementation Deployment Transaction: 0xf39ea3a831d2b60035fbe894157f0ce78e0b13fff1ffed2e6cf77d462f0292cc
• Proxy Upgrade Transaction: 0x2a9f9d3807b4d904a36f02021022e5cbbed5a5ff17e465422b71abdf201cbcbc

Calibnet:

• PDPVerifier Implementation: 0x04D4CdB99E34D7e9a366E7eba7A835e034bc41b1
• PDPVerifier Proxy: 0x85e366Cf9DD2c0aE37E963d9556F5f4718d6417C
• Implementation Deployment Transaction: 0x824aec5fd5694c7894985cea1b05545a01d8e09cf114300cf882c3ca79a3a27d
• Proxy Upgrade Transaction: 0x1168d152d58f861ced999d01f70987306eb666965f4d2e26c414510403e700d8

Deployment constructor values are initializerVersion = 4 on both networks, with challengeFinality = 10 on Calibration and challengeFinality = 150 on Mainnet.

Breaking Changes

• Scheduled piece removals are no longer applied automatically by nextProvingPeriod(). Storage providers must drain the pending queue with the new resumable processPieceDeletions(setId, removalCount) method before advancing the proving period; nextProvingPeriod() now reverts with PendingPieceDeletions(count) while removals remain. Processing removals invalidates the active challenge, and PiecesRemoved events are emitted in batches of at most 100 piece IDs. Storage-provider integrations must add this explicit processing step (#​297).
• The legacy PiecesAdded event remains declared in the ABI but is no longer emitted. Event consumers must support PiecesAddedV2 before this contract version is deployed (#​300).

Added

• Added legacyPieceStorageIdLimit() to expose the permanent data-set ID boundary between legacy and compact piece storage. Upgrade deployments must call migrate() to initialize this boundary; until then, newly created data sets continue using legacy storage (#​292).
• Added ABI-decodable PiecesAddedV2 events containing the first contiguous piece ID and two-word packed CIDs. Additions larger than 100 pieces emit multiple events so each remains within Filecoin's 8 KiB event-value limit (#​300).
• Added PiecesScheduledForRemoval events so indexers can observe scheduled removals immediately. Piece IDs are emitted in batches of at most 100 to preserve the 2,000-piece scheduling limit without exceeding Filecoin's 8 KiB event-data limit; empty removal schedules are rejected (#​287, #​299).
• Added announceUpgradePlan(nextImplementation, delayEpochs) for announcing upgrades using a relative delay (#​285).

Changed

• New data sets created after the migration cutover store each piece in a compact two-slot PieceV2 representation instead of the five-slot legacy representation. Existing data sets remain fully supported on the legacy layout, including new piece additions, proofs, removals, deletion, and cleanup (#​292).
• PieceCIDv2 validation now rejects non-minimal, unterminated, overflowing, length-mismatched, and otherwise malformed multihash encodings (#​292).
• Deprecated announcePlannedUpgrade() in favor of announceUpgradePlan(). Calls that specify the current or a past epoch now schedule the upgrade for the next epoch instead of reverting (#​285).

Fixed

• cleanupPieces() now uses the same permission gate as deleteDataSet(), anchored to last proving activity instead of cleanup-mode entry. The abandonment path previously required two full INACTIVITY_WINDOW periods (~60 days); a permissionless deleter can now clean up and collect the deposit immediately. An SP deleting after exceeding the inactivity window no longer gets an exclusive cleanup period (the data set was already permissionlessly deletable). The unused cleanupModeEpoch storage is deprecated in place (#​279).

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 4am on monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.