PROJECT: Collaborative Seed Recovery (CSR)

Comienza con los documentos enlazados CSR Overview y CSR & CKM Use Cases, y después lee los documentos SSKR, UR y crypto-request referenciados. Este issue contiene varios frentes de trabajo de diseño, especificación, implementación y documentación que aún no se han marcado como completados, en lugar de un único punto de entrada; el trabajo solo está terminado cuando se delimita un frente de trabajo específico y se completa su diseño, sus requisitos, sus pruebas o su aplicación de referencia.

Collaborative Seed Recovery, or CSR, is a new system intended to automate the recovery of seeds and other sensitive digital data in a way that is safe, secure, and simple to use. It is not a methodology to prevent compromise, but simply to add resilience to recovery in the case of failure or loss.

CSR allows for the recovery of seeds and other secrets by dividing responsibility for recovery up between multiple devices, some (but not all) of which will be necessary for recovery. Its baseline recovery mechanism uses self-sovereign recovery, while more advanced scenarios allow for social recovery. Backup is meant to be largely automated, especially in the baseline scenario, while recovery may require some user intervention.

CSR is built using SSKR to lock crypto-envelopes of data and to allow recovery using a variety of authentication methods.

Please see the CSR Overview for more information.

TODO: Documentation & Prep

• Decide Who Will Be Involved at Each Principal Company
  • Share Individual Goals
• Decide Shamir or VSS
• Write Use Cases
• Write Cryptographic Design
• Write System Requirements
• Spec Out Automated crypto-envelope with multiple types of SSKR Permits (2 of 3 + 4 of 9) + metadata
• Spec out related crypto-requests
  • Update any necessary papers, test vectors, etc
• Create Reference App for Sending SSKRs
• Write White Paper
  • https://github.com/BlockchainCommons/Gordian/blob/master/Docs/CSR.md
  • Clearly define: CSR does not defend the use of your keys, it simply makes recovery easy and minimizes SPOFs in recovery.
  • Lay out how it works
  • Describe why Proxy, Bitmark, and other parties would support it.
  • Build a roadmap for a fall release.
  • Preview how this will lead to CKM in 2023.

TODO: Specification Work

• Design Hash Inclusion Proof for Envelope

TODO: Level 0

• Design Level 0 of CSR
  • User makes no decisions
  • One Share is stored in iCloud
  • Information on location of other shares is stored in iCloud
  • Other shares are stored on remote sites in an automated way
  • User must do no auth to recover, other than verify their iCloud login
• Develop Level 0 of CSR

TODO: Level 1

• Design Level 1 of CSR
  • User makes one choice for a share to be given to someone
  • Option: offline
  • Option: given to a friend running an app
  • Option: given to an online service
  • At least two shares for automated recovery are deleted
  • Auth is required for new share management
• Develop Level 1 of CSR

TODO: Post-Release

• Write test cases
• Choose a branding name
• Decide if there is a seal for this

This is expected to be a joint project of Blockchain Commons, Bitmark, and Proxy with a planned start date around July 5th.

Essential Links: CSR

• CSR Overview
• CSR & CKM Use Cases
• CSR Intro for RWOT
• CSR Intro Poster for RWOT

Essential Links: SSKR

• SSKR for Developers
• SSKR Test Vector
• Developing SSKR Share Scenarios
• The Dangers of Secret-Sharing Schemes

Essential Links: URs

• Uniform Resources (UR)
• UR Type Definition for Sharded Secret Key Reconstruction (SSKR)
• URs: An Overview
• A Guide to Using URs for SSKR
• A Guide to Using UR Request & Response
• Crypto-Request Test Vectors