Browse Source
In the db, the 'seed_type' field could be present both at the top-level and inside keystores. Note: - both fields had usages - the top-level field was added in 2.8 re "initial segwit support" (master3a64ec0f2e) - there was no db upgrade for it, so older files are missing it - if present, valid values can be electrum types but also other types supported by the wizard, e.g. "bip39" - the keystore-level field was added in 4.1 (7b7bba2299) - there was a db upgrade when it was introduced, so old files also have it - if present, valid values can only be electrum types - there is not much value in the top-level one having a non-electrum value, and those values were never used by other parts of the code - note that when creating a standard wallet from a bip39 seed, the seed is discarded. Only the derived xprv and the derivation path are kept. If we changed this and also kept the seed, e.g. to display it to the user, then it would make sense to save the seed type (e.g. "bip39"). However storing that seed_type would make more sense at the keystore level (not top-level). We delete the top-level 'seed_type' field. ``` { "keystore": { "seed_type": "segwit", ... }, "seed_type": "segwit", ... } ```
5 changed files with 22 additions and 8 deletions
Loading…
Reference in new issue