Skip to content

SIP - Catastrophic blockchain failures and recovery #10

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

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

SIP - Catastrophic blockchain failures and recovery #10

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
70c4b48
sip 011 first draft
jcnelson Feb 11, 2021
3f62578
Merge branch 'main' into feat/sip011-catastrophic-failure-recovery
jcnelson Feb 15, 2021
3a9ec98
address typos and feedback
jcnelson Feb 15, 2021
7fe629c
list core developers to contact for catastrophic error recovery
jcnelson Feb 17, 2021
3832ae2
Address some feedback
jcnelson Feb 17, 2021
1427c78
reword text in core developer list to make it less editorialized
jcnelson Feb 17, 2021
05f8c6f
fill in related work section and address feedback on soft-fork signaling
jcnelson Mar 12, 2021
893dd5a
Add case studies for all kinds of catastrophic failure recoveries
jcnelson Mar 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions sips/sip-011/SIP-011-001.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Stacks Core Developers

The following is a list of people who may be called upon to carry out the catastrophic bug recovery procedures described in SIP 011.

Inclusion in this list is subject to review by the SIP Steering Committee, its superiors, or its successor organizations. Names are alphabetical by last name. Anyone on this list can remove themselves by contacting the Steering Committee.

* Aaron Blankstein ([email protected]), @kantai
* Ludo Galabru ([email protected]), @lgalabru
* Jude Nelson ([email protected]), @jcnelson

This SIP must be cryptographically signed by each Stacks Core Developer on the initial list and the Stacks Foundation in order to be ratified. These signatures are included below:
Loading