How to Back Up a Seed Phrase Without a Single Point of Failure

The two ways a seed phrase backup fails

A backup can fail in two opposite directions, and most setups only defend against one of them:

• Loss: the only copy is destroyed, misplaced or forgotten, and the coins are gone for good. Nobody can reset a seed phrase.
• Exposure: someone else reads the phrase, whether a burglar, a cloud breach, a curious relative or a phishing page, and the coins can be moved in minutes.

Adding more copies protects against loss but multiplies exposure. Locking a single copy away protects against exposure but makes loss more likely. A good backup needs to handle both at once.

Common options and their trade-offs

• Paper or metal plate in one place: offline and simple, but a single point of failure for fire, flood, theft or simply forgetting where it is.
• Several full copies in different places: survives the loss of one, but anyone who finds any copy has everything.
• Photo, notes app, email or cloud drive: convenient, but it puts the full phrase on internet-connected services. Avoid this.
• Splitting the words (for example, 12 words to one person and 12 to another): a half phrase still leaks a lot of information, and losing either half loses the wallet. This is not real secret sharing.
• Multisig wallets: strong protection that needs several keys to sign, at the cost of more setup and wallet support.
• Hardware wallet Shamir backups (SLIP-39): some hardware wallets can create threshold backups natively when you set up the wallet.
• Threshold backup with Shamir's Secret Sharing: the phrase is protected so that any chosen number of pieces (for example 3 of 5) recovers it, and fewer reveal nothing.

How a threshold backup works

Shamir's Secret Sharing splits a secret into N shares with a threshold T. Any T shares rebuild it; any smaller number reveals mathematically nothing. With 3 of 5, you can lose two shares and still recover, and two people colluding still learn nothing.

In ShareMySecret, the seed phrase is encrypted on your iPhone with AES-256, and the encryption key is split with Shamir's Secret Sharing. Each person you choose receives one key share together with the encrypted secret. No server stores anything, and there is no account. The security whitepaper covers the exact design.

A practical setup

1. Pick the people or places. Five is a common number: for example, two family members, a close friend, a second device you control, and someone in another city.
2. Pick the threshold. 3 of 5 tolerates two losses and needs at least three people to act together.
3. Create the secret and share the keys. Recipients need ShareMySecret on their own iPhone to receive and store their share.
4. Write down the plan, not the secret. Note who holds a share and how many are needed, and keep that note apart from the shares.
5. Review it yearly. People move, change phones or drift apart. If a holder is no longer right, create a new secret with new recipients and move your funds if you have any doubt.

Be honest about the limits

• The phone you type it on matters. Entering a seed phrase into any phone exposes it to that device while you do it. If that device is compromised, no cryptography helps. Use an up-to-date iPhone you trust.
• Threshold collusion. If T of your holders decide to work together, they can recover the phrase. Choose people who don't all know each other well, or raise the threshold.
• Too many lost shares. If more than N − T shares are lost, the secret is gone. There is no backdoor, by design.
• Everyone needs an iPhone. ShareMySecret is iOS only today, for you and for the people holding shares.

If you hold large amounts, a threshold backup works well alongside a hardware wallet or a multisig setup rather than replacing them.