List all FWSS related contract addresses

[BigLep]

Done Criteria

The other addresses relevant for FWSS (pdpVerifier, filecoinPay) should be listed at https://filecoin.cloud/warm-storage-service as well.

Why Important

If we're trying to be transparent, then lets be consistent and include everything.

Notes

1. With adding more contracts, I don't expect the current card layout makes sense. Maybe instead a table with 3 columns:
   • Contract Name
   • Mainnet Contract Address
   • Source Code Link
2. Contract addresses are listed in https://docs.filecoin.cloud/resources/contracts/ . Another option is to link to that page?

[BigLep]

Or if it was intentional to not include all those contracts, let me know...

[BigLep]

"product input" is required here. Also, contract addresses are listed in https://docs.filecoin.cloud/resources/contracts/ . Another option is to link to that page?

[BigLep]

@nijoe1 in a private channel (thread) suggested:

I'd suggest having one source of truth in the docs (https://docs.filecoin.cloud/resources/contracts/) and linking to it from https://filecoin.cloud/warm-storage-service rather than duplicating the info in both places. The contracts section on filecoin.cloud could link to each contract's source code and point users to the docs for contract addresses.

---

@nijoe1 : we need to come to decision here as there is #134 which we need to decide whether to proceed with. For simplicity, I agree with just using https://docs.filecoin.cloud/resources/contracts/, but then make sure that:

1. https://docs.filecoin.cloud/resources/contracts/ has all info (contract name, address on calibration, address on mainnet, link to source code)
2. it gets updated as part of our contract upgrade process

There part I don't have intuition on is if we think it's important for branding to list more "contract" stuff directly on https://filecoin.cloud/warm-storage-service . But tha

[nijoe1]

Can we assume that this file will always be up to date once new deployments occur ?

If so I can create a CI job to check the addresses match before each docs.filecoin.cloud deployment.

At the same time as filecoin.cloud is a next app a solution for keeping addresses updated is to make the contracts section an SSR component that fetches the deployments.json with hourly caching to not get rate limited.

cc: @BigLep @rjan90

[rjan90]

Can we assume that this file will always be up to date once new deployments occur ?

Yes, that can be assumed. As part of the deployment of new implementation contracts for a upgrade, the deployment.json will automatically be updated.