-
Notifications
You must be signed in to change notification settings - Fork 339
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.
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
CIP-0135? | Disaster Recovery Plan for Cardano Networks #893
Conversation
update rationale
update mithril
update motivation
update abstract
update scenario_1
update scenario_2
Small text change
Expand on what the lightweight checkpoints introduced with Genesis are, and how they can assist with recovery from a disaster.
Add section on Genesis checkpoints
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor formatting things. Please check for extra spaces between words that I may have missed.
As mentioned in the last CIP editor meeting, these comments do not detract from the content. So, after the formatting, I am happy to approve this CIP 👍
Co-authored-by: Ryan <44342099+Ryun1@users.noreply.github.com>
Co-authored-by: Thomas Vellekoop <107037423+perturbing@users.noreply.github.com>
Co-authored-by: Thomas Vellekoop <107037423+perturbing@users.noreply.github.com>
Co-authored-by: Thomas Vellekoop <107037423+perturbing@users.noreply.github.com>
Co-authored-by: Thomas Vellekoop <107037423+perturbing@users.noreply.github.com>
I've applied the editing suggestions. |
@kevinhammond promoting to |
Thank you. |
FYI for reviewers, interested community members & editors: I would recommend anyone planning to participate in the |
@perturbing @Crypto2099 since yesterday's CIP meeting was cancelled, would you have any objection if we merged this proposal as it stands now? Re #893 (comment) I think there was some good dialogue & suggestion externally there, but also that @kevinhammond and co-authors will be keeping an eye on all those issues going forward and can update this proposal in accordance if & when necessary. |
@rphair, perfect! Since all acceptance criteria have been met, I suggest marking it active as well. |
@kevinhammond re: @perturbing's #893 (comment): are there implications of marking this |
@rphair, as I understood it, the plan is ready to go. I think that marking this document as But let's wait for @kevinhammond to confirm the above sentiment. |
CIP-0135/README.md
Outdated
CIP: 135 | ||
Title: Disaster Recovery Plan for Cardano networks | ||
Category: Tools | ||
Status: Proposed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Status: Proposed | |
Status: Active |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kevinhammond we're waiting for you to change the |
thanks @kevinhammond for bringing it home - @perturbing @Crypto2099 I'm merging since we were all unanimous about the change in 8c43db3 being the last item to go. 🎉 |
This CIP describes a number of scenarios that could lead to a major failure of Cardano, and
discusses how the chain could be recovered in such an eventuality.
While such an event is highly unlikely, it is necessary to be prepared.
The recovery process involves both technical and social aspects, and explains how new mechanisms and tools
such as DB Truncator, DB Synthesiser, Mithril and Ouroboros Genesis can be used to assist with the recovery.
📃 Rendered proposal