Document Contract Relationship and Migration Strategy

[BigLep]

Done Criteria

1. Document the current relationship/coupling between various contracts.
   1. A visual here would help.
   2. It would be good to include details about which contracts are upgradeable due to proxies.
2. For each of the main components (PDP Verifier, Filecoin Pay, and Filecoin Warm Storage Service) answer, "If there were a flaw in *this* piece, what then?"
3. From those “what then?” analyses, propose concrete migration mechanisms (even if they’re manual at first):

Why Important

We want to identify where the story is so bad that we actually need contract design changes now because we wouldn't want to be operationally exposed later..

Notes

Examples to think through and document:

• If PDP Verifier’s proof system has a security bug and we need a new PDP Verifier:
  • What happens to existing deals/verifications?
  • How do we link new verifier(s) to existing or new warm storage?
• If Warm Storage needs a v2:
  • How do users move data / authorizations / balances?

[rvagg]

Related work: #115

[rvagg]

And https://filoznotebook.notion.site/Filecoin-Services-Model-for-Change-241dc41950c180af85f1cac1687766a5