All articles

Upgrading to Multi-share Backup

If you’ve decided it’s time to boost your personal security standards, adopting Multi-share Backup is a giant leap in achieving just that!
 

Multi-share Backup is supported on Safe 5, Safe 3, and Model T


Depending on your current Trezor setup, there are different routes to getting set up with Multi-share Backup:


I have a brand new Safe 5, Safe 3 or Model T

If you're just unboxing a new Trezor that's compatible with Multi-share Backup, you can even bypass the upgrade process and dive straight in to a Multi-share setup. Select Multi-share Backup during the device initialization and follow the on-screen and on-device instructions:
 
 
You can get started straight away by following our detailed step-by-step guide to creating a wallet with Multi-share Backup.
 

I’m already using Single-share Backup on my Trezor

If you’re already setup your Trezor with a 20-word Single-share Backup, you can upgrade to Multi-share Backup directly via Trezor Suite settings:

  • Go to Settings > Device
  • Select Create Multi-share Backup:

 
  • Follow the on-screen and on-device instructions.
 
Note that when upgrading from Single-share to Multi-share Backup, you are effectively creating an additional backup for the same seed (same accounts, addresses etc). This means that your original Single-share Backup is still valid, and so should be kept safe and secure.
 

I have a 12 or 24-word Wallet Backup with my Safe 5/Safe 3/Model T

If you’re already using a 12 or 24-word Wallet Backup (recovery seed), the process is more complicated. As you will be migrating from one standard to another (i.e., BIP39 to SLIP39) your wallet will be set up using a different seed. This means you will have to migrate your funds carefully from one seed to another, which entails multiple steps.

 

Ensure you confirm you current Wallet Backup (formerly recovery seed) before doing anything else.
 

The step-by-step process required for ‘indirectly’ upgrading from BIP39 to Multi-share Backup is as follows:



Now that you’ve created a Multi-share Backup (for a new seed) you can transfer the funds from your original seed to the new one. The steps for doing so are outlined in our Move crypto to a wallet with a new seed article.
 

I am already using Shamir Backup

To create additional Multi-share backup(s) directly via Trezor Suite settings, you require either:

If you have already set up a Shamir wallet prior to the June 2024 release of Trezor Suite, it is not possible to create additional Multi-share Backups via the Trezor Suite settings menu (as outlined above).
 

Important: If you already have a Multi-share backup and create a new one, the old backup will still be valid. The shares from the old backup cannot be used with the new one.

Each Multi-share backup’s shares are unique and can’t be mixed with another Multi-share backup. In this case, you will have two separate, valid Multi-share backups, each usable only with their own set of shares respectively.


What happens to my Single-share backup when I upgrade to a Multi-share backup? 

When you create a new Multi-share backup from your 20-word Single-share backup, you will create a new Multi-share backup. You cannot add your Single-share backup as part of a new Multi-share backup.
 
Important: Upgrading to a Multi-share backup does not invalidate your original Single-share backup.  If your Single-share backup gets compromised your funds are at risk even if you have a Multi-share backup. 

If you want to reduce the risk of having a single point of failure, you have the option of destroying the original Single-share backup. You should only destroy your Single-share backup after verifying your new Multi-share backup works and that you can access your funds with it. 

Similarly, when creating a new Multi-share backup after you have already made a Multi-share backup, you can only create a new backup. It is not possible to use backup shares interchangably. To check if a backup share belongs to a certain backup, you can always look at first two words in the backup share, as these will be consistent across all shares within a Multi-share backup.