New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Recovery strategy for total network meltdown #4

Open

m0ar opened this issue Sep 14, 2023 · 0 comments

Assignees

Collaborator

m0ar commented Sep 14, 2023

There is a small chance we outlive the Ceramic network.

DOD: we have a rough contingency plan for this situation.

Notes:

All the data which models our protocol will still be available on IPFS as long as someone pins it. This includes both files but also the stream data itself.
All software (IPFS, composeDB, ceramic client, graphql) is open source, so nothing prevents us forking and running our own network.
The anchor and consensus network is a bit more unclear, but not at all impossible for us to move I'd assume.

m0ar self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment