Done Criteria
We have a runbook that lists:
- which of our web-properties we want to ensure has a decentralized backup (i.e., Filecon Pinned, ENS contenthash set)
- what ENS domains they each map to
- who has credentials to update the corresponding ENS domain contenthash fields
In addition, our FOC web-properties are decentrally hosted by default.
Why Important
We want to ensure key functionality of our decentralized toolchain is still accessible, even if platforms like Cloudflare are down. It is a selling point of our tech, and it's otherwise a bad look if it doesn't work when AWS/Cloudflare are down.
Notes
- This should be automated.
Note that there are complications with automating this:
- Gas costs for ENS domain updates
- ENS domain ownership should be under a multisig, but that would get int he way of contenthash updates in CI
- Will we rely on ipns instead?
- Any site that we do want hosted decentrally needs to be pinned (presumably with the filecoin pin GitHub action so that we have IPFS CID to set the ENS domain contenthashh or ipns record to)
- Before doing the implementation work, lets have a review of the plan to (e.g., tools we're going to use, how we're going to automate) to make sure we're aligned.
Done Criteria
We have a runbook that lists:
In addition, our FOC web-properties are decentrally hosted by default.
Why Important
We want to ensure key functionality of our decentralized toolchain is still accessible, even if platforms like Cloudflare are down. It is a selling point of our tech, and it's otherwise a bad look if it doesn't work when AWS/Cloudflare are down.
Notes
Note that there are complications with automating this: