Shamir backup

A Shamir backup splits the secret that restores a crypto wallet into several separate word lists, called shares, and sets how many of them, the threshold, are needed to rebuild the wallet. Anyone holding fewer shares than the threshold learns nothing about the secret, so one lost or stolen share doesn't put the coins at risk.

Three shares, any two

What happens when one share of a backup goes missing? Wallet maker Trezor prints a sample backup in its Shamir backup guide, three shares of 20 words that each open with “gesture necklace academic.” On November 19, 2026 we decoded them with the field layout and checksum code published in SLIP-39, the standard behind the feature. Our decoder first reproduced all 45 test vectors that the standard points to.

Shares combined Result
1 and 2 128-bit master secret starting e685dc27
1 and 3 The same secret
2 and 3 The same secret
Any one share alone Refused, threshold not met

Each share’s header describes one group with a member threshold of 2, and every three-word checksum was valid. So the sample is a 2-of-3 scheme, and it also carries the older value of the standard’s extendable-backup flag, which SLIP-39 says newly created shares should no longer use.

What the standard says

SLIP-39 is dated December 18, 2017 and marked final. Five of its six listed authors give SatoshiLabs email addresses, and SatoshiLabs is the group Trezor belongs to. The standard splits a master secret so that a set minimum of parts rebuilds it, and “knowledge of fewer than the required number of parts does not leak information about the master secret.”

The standard allows up to 16 groups of up to 16 shares each, with a threshold inside every group and another across groups. A 128-bit secret gives 20-word shares and a 256-bit one gives 33, drawn from a list of 1,024 words. The last three words are a checksum that is guaranteed to catch errors in up to three words.

NIST describes the general idea in its July 2020 threshold report: shares are “unintelligible” alone but recover the secret “once combined into a set with a threshold number of shares.” The same report sets this apart from threshold schemes that sign “without ever reconstructing the key in any place,” the approach an MPC wallet takes. A Shamir backup does rebuild the secret, on the device doing the restore.

Where you see it

Trezor’s Multi-share Backup guide lists the Safe 7, Safe 5, Safe 3 and Model T as supported, with 1 to 16 shares per backup. The company says Shamir backup has been the default on its Safe devices since June 2024.

Trezor Suite sets up 20-word shares, while 33-word shares need the trezorctl command-line tool or Electrum. Every share in one backup starts with the same two words, which tells you the pieces belong together.

Trezor names Electrum, Sparrow and BlueWallet among the software wallets that support it. The word list differs from the BIP-39 list behind a seed phrase, and SLIP-39 says the two schemes are for the most part not compatible.

The old backup still opens the wallet

Since June 2024 Trezor has let owners start with a single-share backup and upgrade it to several shares later. Its guide warns that the original stays valid, and “if your Single-share Backup gets compromised, your funds will also be at risk regardless of the Multi-share Backup.” The standard explains why, since the extendable flag lets several sets of shares lead to the same master secret.

The opposite failure is final too. In Trezor’s 3-of-4 example, losing two shares leaves the wallet “unrecoverable.” Before you destroy an old backup, check the new shares on the device, as Trezor advises, and keep each share in a separate place, never as a photo or a cloud file.