Trezor Guide
Shamir Backup Integrity Checks: How to Verify Your Seed Shares Are Correct
Published on 2026-08-29Updated on 2026-08-29By Jonah Pratt · Editorially reviewed
A Shamir backup splits your recovery seed into multiple shares, but the system only works if every share is recorded accurately. An integrity check is the process of verifying that each share’s checksum is valid and that the shares still reconstruct the original master seed. For Trezor users, this means using the built-in Shamir backup tool to test your shares before you need them in an emergency.
Why Integrity Checks Matter More Than You Think
When you create a Shamir backup, you are distributing trust across multiple physical pieces of paper or metal. A single typo in a share—a wrong word, a missing letter, or a swapped digit—can make that share useless. Unlike a standard 12-word seed, where a checksum catches most errors, Shamir shares use a different encoding. The checksum in each share is your first line of defense, but it only tells you that *that specific share* is internally consistent. It does not tell you whether the share belongs to the same set as your other shares.
The Difference Between Share Checksum and Set Validity
A share checksum verifies the integrity of a single share in isolation. If you type a share incorrectly, the checksum will fail immediately. However, a valid checksum does not guarantee that the share is from the correct backup set. You could have two valid shares from different backups, and they would never reconstruct your original seed. This is why you need a full integrity check that tests the entire set together.
What Happens When a Share Is Corrupted
If you discover a corrupted share during a routine check, you still have time to recreate your backup. If you discover it during a recovery attempt after a hardware failure, you may be locked out of your funds. The cost of checking is minutes; the cost of failing is permanent loss.
How to Run an Integrity Check on a Trezor Device
Trezor’s Shamir backup (based on SLIP-39) includes a verification step during the initial setup. The device will ask you to confirm each share as you write it down. But you should not stop there. A proper integrity check happens after you have stored the shares, because physical storage can introduce errors—smudged ink, torn paper, or a bent metal plate.
Step-by-Step Verification on the Device
1. Connect your Trezor and open the Trezor Suite application.
2. Navigate to the device settings and select “Check recovery seed” or the equivalent option for Shamir backups.
3. The device will display a prompt asking you to enter one share at a time.
4. Enter the full share exactly as written, including the share index and checksum words.
5. Repeat for each share until the device confirms that the set is valid.
The device will not show you the reconstructed seed. It only confirms that the shares are mathematically compatible and produce a valid master secret.
What the Check Does Not Cover
The device check validates the *cryptographic* integrity of your shares. It does not verify that your physical copies are legible, dry, or fireproof. You still need to inspect the physical medium for wear and tear.
Common Integrity Failure Modes and How to Spot Them
Most failures fall into three categories. Understanding them helps you know what to look for during a manual review.
- Transcription errors: You wrote the wrong word or number when copying the share from the device screen. The checksum will usually fail, but not always—rarely, an error can produce a valid checksum.
- Partial shares: You missed a word or dropped the last line of a share. The share will be too short, and the device will reject it immediately.
- Mixed sets: You accidentally combined shares from two different backups. Each share is valid on its own, but the set is invalid. This is the most dangerous failure because it passes the single-share check.
Building a Regular Integrity Check Routine
You should not wait for a hardware failure to test your shares. A simple schedule protects you from slow degradation of your backup media.
Quarterly Checks for Active Users
If you use your Trezor regularly, run a full share verification every three months. This catches transcription errors from the initial setup and any damage that occurred during handling.
Annual Checks for Long-Term Storage
For a backup that sits in a safe deposit box, an annual check is sufficient. When you retrieve the shares for the check, also inspect the storage container for water damage, rust, or fading.
A Simple Comparison: Device Check vs. Manual Review
| Method | What It Verifies | Time Required | Limitation |
|---|
| Device check (Trezor Suite) | Checksum and set compatibility | 5–10 minutes per share | Requires the device to be powered and connected |
| Manual review of written shares | Legibility and completeness | 2–3 minutes | Cannot detect hidden typos that still pass checksum |
| Full dry-run recovery | End-to-end reconstruction | 20–30 minutes | Requires a second device or a wiped device to test safely |
A full dry-run recovery is the gold standard. You enter all shares into a fresh wallet (or a wallet on a separate device) and confirm that the derived addresses match your known receiving addresses. This is the only test that proves the shares can actually restore your funds. Run this at least once after creating the backup, and again after any major change to your setup.
The bottom line: a Shamir backup is only as strong as your ability to verify it. Perform a device check immediately, schedule periodic reviews, and do one full dry-run recovery. That three-layer approach ensures your shares are not just stored, but proven.