trezor_ks.json5

// These are all the supported fields for Trezor keystores in pyexch v0.0.1 and earlier.
//   Obviously these are example values and some will need to be changed to fit your needs.
//   Since Trezor CipherKeyValue is an encrypted keystore it is a good one to use without 
//   fear of getting compromised.  Obviously, you will need to think about whether or not
//   to use a passphrase, and how and where you want prompting.
//
// NOTE: If you copy this template to use as a keystore on a keystore_update call, ensure
//   ensure you remove the fields at the bottom that are updated and maintained by pyexch.

{
  // Possible formats are {json, trezor, gnupg}, but all internal stores are JSON in memory
  "format": "trezor",

  // Information needed by Trezor CipherKeyVale to encrypt / decrypt this keystore
  "trezor": {

    // The label presented when "ask" is enabled
    "key": "PyExch Keystore",
    
    // The SLIP-16 derivation used for CipherKeyValue
    "path": "m/10016'/0",
    
    // Enable passphrase protection?
    "passphrase_protection": true,
    
    // If passphrase is used, enter it on device or console / environ?
    "passphrase_on_device": false,
    
    // Should Trezor Prompt on decrypt?  Can't change once loaded
    "ask_on_decrypt": true,
    
    // Should Trezor Prompt on encrypt?  Can't change once loaded    
    "ask_on_encrypt": false,
    
    // =====================================================================================================
    // The fields below this line are updated and maintained by pyexch for state storage.  No need to update 
    // =====================================================================================================

    // Always zlib right now, really just documenting for recovery
    "compression": "zlib",
    
    // Last good session, useful when running commands back to back to avoid passphrase prompting
    "last_session": "456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123",
    
    // Pay attention to this.  You can use it to validate your passphrase and ensure nothing changes
    "fingerprint": "bcdef012",
    
    // The crc32 of the decrypted JSON object to ensure everything went OK.
    "crc32": "3456789a",
    
    // CipherKeyValue needs padding.  This is how many bytes to chop off the front after decryption for zlib.
    "hdr_padding": 12,
    
    // json.zlib.pad.cipherkv.base64 - Yes, those are the levels of encoding to unwind !
    "enc_data": "23456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz+/0123456789ABCDEFGHIJKLMNOP",    
  }
}