Trezor Multi-Share Backup (Enhanced 20 Word SLIP39 Backup, Trezor Safe 5, Safe 3, Model T)
Вставка
- Опубліковано 11 лип 2024
- Buy a Trezor Safe 3: trezor.io/trezor-safe-3?trans...
Buy a Trezor Safe 5: trezor.io/trezor-safe-5?trans...
SLIP39 Tool: 3rditeration.github.io/slip39...
A video which does a deep dive into the new backup approach that will be used in the Trezor Safe 5, making use of Trezor's SLIP39 standard, an implementation of Shamir's Secret Sharing.
00:00 - Introduction
01:34 - New Wallet Creation Workflow
02:57 - Creating a Mult-Share Backup from an existing extendable SLIP39 20 word seed
06:16 - Note on Converting Existing BIP39 Seeds to SLIP39 Shares
06:51 - Note on Creating to Multi-Share Backups from Older SLIP39 Sets (Prior to June 2024)
07:20 - Compatability Note regarding Older SLIP39 Implementations
08:40 - Advantages: Simplicity of SLIP39 Multi-Share Backups (Compared to a BIP39 Passphrase)
09:53 - Advantage: Re-Creating SLIP39 Backups Sets with Shares are Compromised, Lost or Damaged
10:20 - Advantage: Much Stronger Mnemonic Checksum & Distinct Wordlist
11:03 - Advantage: Wordlist optimised for T9 Entry (Faster and Easier with Touchscreen)
11:17 - Potenal Issue: Multiple Seed Backups Remaining Valid
12:01 - Note Regarding Recovery Shares being Unique to Recovery Sets
12:46 - Summary and Conclusion - Фільми й анімація
Great deep dive. Thanks for covering it!
Thanks, no worries :)
I prefer traditional bip39 + mutlisig. Might revisit later when more hw manufactures support these new standards. Good video btw.
Yea it depends on what you are trying to achieve as well as how much complexity you can manage. :)
@@jordanrox007 multisig is unfortunately on chain, more expensive on fee. Here you build the private key off chain
Yea the fees and privacy aspect of multisig are still an issue until signature aggregation is ready for prime time. (Never mind the privacy challenge that storing wallet descriptors everywhere creates)
@@jordanrox007 seems my comments are disappearing?
They get flagged as spam, so need manual approval. (No idea why, though looks like I can manually flag users as safe, so should be fine from now on)
Thanks a lot! Are you going to have a more in-depth review of the new Safe 3 and Safe 5 models, especially on the new security improvements?
I have already done one for the Safe 3, will do the Safe 5 when it arrives. (But it just looks like a Trezor T with a secure element, same as the Safe 3)
Crypto guide is very smart
Thanks ;)
@@CryptoGuide true
;)
@CryptoGuide thanks for the explanation of the difference in SLIP39 and bip39 didn't know the check sum was more them a 24 seed
Yea it's *significantly* stronger, (So like 1 in a billion chance of having a false positive checksum for all SLIP39 seed types, as opposed to 1/16 for 12 words and 1/256 for 24 words) having 30 bits for the checksum regardless of the length of the SLIP39 mnemonic. (See here: github.com/satoshilabs/slips/blob/master/slip-0039.md#format-of-the-share-mnemonic)
So if you can still recover from the original seed, even after you have set up multi-share, what’s the point? Should you destroy the original seed record and just use the multi-share from then on?
It depends on your setup but you might do something like have a full copy in a safe in your home and have a multi-share set distributed amongst different locations or people. (Or something like that)
That said, most people probably want to destroy the single backup after creating (and testing) the multi-share backup.
I heard there’s some sort of auto firmware update feature in one of the recent trezor updates that could be a potential security risk? Is that accurate or am I just hearing nonsense? I didn’t see it in their release notes.
Trezor Suite, the companion software provided by Trezor does have an option for an in-app auto update of itself, but this isn't really related to the hardware, as you will need to confirm firmware updates on-device and the device itself will also only accept official signed updates from Trezor. (Unless you have specifically selected to load unofficial firmware, which will throw all kinds of warnings)
@@CryptoGuide Ah, ok, good. I figured trezor wouldn’t do something stupid like auto update firmware. Good to hear.
Yea even Ledger haven't gone that far ;)
Hi, when I use passphrase for single share and after that upgrade for multi share, passpharse will work for multishare backup too?
And what advantage does slip39 have against bip39 backup+passphrase?
You can also add a passphrase for all slip39 wallets, the number of shares isn't relevant to this.
SLIP39 multi-share is much less error prone, as the share words are chosen for you have a checksum for each set.
so when I use slip39 multishare, I have two ways to restore the wallet (original single share and multishare) and passphrase will be compatible with both options?
That's right.
This is just for illustration. I have a Trezor Model T. I created a wallet backup with a bip39 high entropy passphrase and Super Shamir. One set is a 3x4. Another set is a 4x4. Another set is a 4x8.
I can verify and recover the wallet with 1 from 3x4 and 2 from 4x4 or 2 from 4x8. Can the new slip39 do this like my Mode T?
You do good work. Thanks..🧡😊
I didn't cover Super Shamir in this video, but the functionality from the Trezor T is unchanged in this regard and is all still there for all core devices (Trezor T, Safe 3 and Safe 5), though it still needs to be triggered via the command line. :)
@@CryptoGuide Thanks man. But I think I triggered Super Shamir from the touch screen. But it's been a while. So I could be mistaken. But I very much like the command line..👍
Yea you kick the workflow off from the command line (and Maybe Electrum) but once it is started, you select all the stuff on the touchscreen of the device itself.
Trezor T had snorr backup, they replaced it with slip39?
Trezor T had SLIP39 too, but didn't support the ability to re-create backup sets like is possible now with their update to the standard.