feat: replace Service Registry with PDP Verifier

[silent-cipher]

Note

This PR assumes that the intent of renaming “Service Registry” to “PDP Verifier” also includes updating the contract address to the actual PDP Verifier contract. This goes beyond the original issue description, which says address would remain unchanged. I’m opening this as a draft to clarify the intended behavior before proceeding further.

Happy to proceed with this pr based on the final decision.

📝 Description

This PR updates Service Registry contract details with PDP Verifier contract.

• Type: New feature

🛠️ Key Changes

• Replace service registry contract with pdp verifier contract
• Update contract type definitions

📌 To-Do Before Merging

• Clarify Change "Service Registry" to "PDP Verifier" in Warm Storage Details Contract Addresses #134 (comment)

📸 Screenshots

Closes #134

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
filecoin-cloud	Ready	Preview	Jan 15, 2026 0:56am

[BigLep]

@silent-cipher : when we deploy new contracts does this get updated automatically or is there a manual step?

Also, if you want someone to review it, please @mention them or request review.

[silent-cipher]

It's a manual step. When new contracts are deployed, the contract addresses needs to be updated explicitly.

[BigLep]

It's a manual step. When new contracts are deployed, the contract addresses needs to be updated explicitly.

Ack, ok. It would be good to have that automated, but that's a task for another time. For now we'll document this step as part of doing FilOzone/filecoin-services#346

[rjan90]

It's a manual step. When new contracts are deployed, the contract addresses needs to be updated explicitly.

Can we use the deployment.json file in filecoin-service: https://github.com/FilOzone/filecoin-services/blob/main/service_contracts/deployments.json ? Maybe have a GHA that checks them every day? And then open a PR if they have changed?