I think I've come across something similar to what you just said but I still don't fully understand how the whole SLIP-39 seed works. Plus back in the day I still remember that ELECTRUM seeds were considered better than the regular BIP- 39 seeds because of their word list and entropy too.
The electrum seed is considered more secure than BIP39 because it uses a version number that determines the type of wallet that will be generated, making it easier to restore and use. Whereas in bip39, the same seed can be used for all addres script type available, but as today practically all wallets follow the already established standards, it shouldn't be a problem to restore in the future and today there is a lot of docs on restoring bip39 wallets seeds.
I think the electrum seed system is interesting for beginners, as it involves less complexity in configuring the wallet.
I never knew BIP 39 seeds of electrum had better entropy. To my understanding
They are all 128 bits for a twelve word seedphrase and boast same entropy likewise SLIP 39(20 words here) .
The only difference is in application
SLIP strength is on distributed security making it harder to steal, electrum just boost flexibility and little less complex.
I'll add a few articles from Trezor explaining more about how the SLIP-39 shamir backup works, or rather, they don't call it by that name anymore, now it's multi-share backup or something like that.
Multi-share Backup on TrezorWhat is Multi-share Backup and Why You Need to Know About ItI'm not a fan of slip-39 because it's not backward-compatible with BIP-39 (you can't turn a SLIP-39 seed into a BIP-39 seed or vice versa). Therefore, BIP-39 is better suited for my use case.
Although Ledger claims that it's possible to convert a SLIP-39 seed to BIP-39 using their app, I wasn't able to do it. If anyone has managed to, please let me know.One key requirement was the ability to generate shares compatible with a BIP39 round trip. Another was using a standard solution instead of inventing my own.
An existing SLIP-39 solution used by another hardware wallet, unfortunately, cannot perform the required round trip.
Then I discovered the SSKR library, which was the perfect fit for several reasons. SSKR stands for Sharded Secret Key Reconstruction. It takes the SLIP-39 method and enhances it.
SSKR is an open-source, interoperable standard that builds upon SLIP-39 with various improvements, including BIP39 <-> SSKR round trip functionality. It perfectly meets all my requirements for the app.
Additionally, the creators of SSKR provide a security-audited, well-documented C library. One of its creators is a co-author of TLS, the bedrock of internet security, demonstrating SSKR’s impeccable security pedigree.
While SSKR forms the core of the app, its integration within a larger framework allows for potential future features like Envelope-SSKR. That can be added to the app.
The issue of multiple backups location is that it increases the likelihood of the seedphrase getting exposed.
One of the strategies to get around seed phrase exposure is to add
passphrases to your wallet that will be used to store funds, you can add as many passphrases as you like, in which case, if someone finds your mnemonic backup, they won't be able to access the funds because the funds are protected by your passphrase in a hidden wallet accessible by it.
So it's extremely important to store both the seedphrase and the passphrase in different locations, you can store your seed phrase offline while backing up your passphrase in an encrypted keepass database, then you can duplicate the backups on pend drives, sd cards and so on.
Another strategy is to encrypt the seed phrase with pgp, but you must do this on an air-gapped offline computer. You need minimal knowledge of how to encrypt/decrypt files with gpg using symmetric or asymmetric encryption.
There are N ways to make your backup as protected as possible, but there are also N ways to lose if you mismanage your backups.