You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As already mentioned by me in #113 I perceive a distributed backup as the last dealbreaker for me switching to the BitBox02.
Also (already mentioned in #113) with the introduced feature of BIP-85 (child keys) my percieved importance for such a features has risen significantly as a lost seed can now not only jeopardize ones own wallet but the wallet of everyone trusting the seed's owner with their wallet's backup (e.g. children, parents, friends (as advertised by the BIP and your blog). Of course this could be migitated by storing multiple copies of the seed but this also increases the chances of one single copy of the seed being compromised and therefor also the derived seeds.
As I myself do not prefer any specific standart for this I do not inded to put such in the title of this FR. But as suggested by @jonathancross a more compatible standard to SLIP-39 could be SSKR which already provides libraries in C or Rust. But which it would be could be discussed by more involved person here.
For more arguments wheter multisig is an alternative or an anhancement to distributed backup please see the discussion in #113.
As SSKR is a standard which could be setup seperatly from the BitBox I want now to mention that sharding the BIP-39 seed outside the BitBox could be done, but would need a secure and trusted device (while the BitBox should already be one of the most if not the most trusted device owned) and would not let the user take advantage of the possibility that the BitBox could store the shards on multiple SD-cards for ease of recovery.
Lastly I want to ask for some additional quality of life features if this would be included in the BitBox:
Continue Recovery in case of powerloss (not a partial typed in shard just from the last complete shard)
Continue a begun recovery without a PC (e.g. just power from a powerbank) to not need to bring all shards together (just go from shard to shard and type them in / read in the SD-card)
Continue a "completed" Dry-Run Recovery for the remainding shards to check the whole setup at once
The text was updated successfully, but these errors were encountered:
As already mentioned by me in #113 I perceive a distributed backup as the last dealbreaker for me switching to the BitBox02.
Also (already mentioned in #113) with the introduced feature of BIP-85 (child keys) my percieved importance for such a features has risen significantly as a lost seed can now not only jeopardize ones own wallet but the wallet of everyone trusting the seed's owner with their wallet's backup (e.g. children, parents, friends (as advertised by the BIP and your blog). Of course this could be migitated by storing multiple copies of the seed but this also increases the chances of one single copy of the seed being compromised and therefor also the derived seeds.
As I myself do not prefer any specific standart for this I do not inded to put such in the title of this FR. But as suggested by @jonathancross a more compatible standard to SLIP-39 could be SSKR which already provides libraries in C or Rust. But which it would be could be discussed by more involved person here.
For more arguments wheter multisig is an alternative or an anhancement to distributed backup please see the discussion in #113.
As SSKR is a standard which could be setup seperatly from the BitBox I want now to mention that sharding the BIP-39 seed outside the BitBox could be done, but would need a secure and trusted device (while the BitBox should already be one of the most if not the most trusted device owned) and would not let the user take advantage of the possibility that the BitBox could store the shards on multiple SD-cards for ease of recovery.
Lastly I want to ask for some additional quality of life features if this would be included in the BitBox:
The text was updated successfully, but these errors were encountered: