changed 3 years ago  
Linked with GitHub

Backup and Restore Strategies

Standard Schema & Parallel

  • Standard schemas for compatibility
  • Arbitrary custom data for stuff outside the standard schemas

Sketch






Contacts [...]
Credentials [...]
DIDsandKeys [...]
LibIndyDump [...]
AppData [...]

Pros

  • Easy to get started with
  • Establishes base standards fast
  • Doesn't require lots of work for custom stuff.
  • Backup / Restore as primary goal, with portability second.

Cons

  • Custom stuff not easily adoptable by others

Extendable Standard Schema

  • Standard schemas
  • Extended with custom stuff

Sketch






Contacts [{
    standardfield1: "",
    customfield1: "",
}]
Credentials [...]

Pros

  • Custom stuff can be easily adopted by others. (Organic standardization)

Cons

  • Harder initial adoption
  • Starts to feel like a good application of json-ld

Meta Backup/Restore Container

  • streaming compression/encryption
  • abstracts the internal details from UX
  • Allows protocols and other supporting materials to be created.
  • Allows later flexibility to innovate on agents without having to abandon the basics.

Local Backup Storage

  • Uses built in backup capabilities of device
    • Mobile app data backup
    • PC based backup
    • Enterprise server backup

Backup and Restore Protocols

  • Allows backup vendor to be different than wallet vendor
    • Wallet Vendor may still offer integrated service
  • Provides regular, automated backup
  • How do you identify yourself to a service to receive a restore?
    • Code or sequence
    • Print and store safely
    • Necessarily different ID than wallet related
Select a repo