Shamir over BIP39
Applying Shamir's Secret Sharing (SSS) to a BIP39 recovery phrase means cutting your master backup into multiple mathematical "shares" instead of keeping it as a single vulnerable list of words.
Here is how it works in short:
The Problem: A standard BIP39 seed phrase (12 or 24 words) is a single point of failure. If someone finds it, they take your funds. If you lose it, your funds are gone.
The SSS Solution: You split your seed into N different shares (e.g. 5 ) and set a threshold k (e.g. 3).
The Security Benefit:
You can hide the 5 shares in different locations.
An attacker finding just 1 or 2 shares gets zero information about your seed.
If you lose 1 or 2 shares due to a fire or theft, you can still fully recover your wallet using the remaining 3.
⚠️ Important Nuance: BIP39 does not natively support Shamir splitting. To do this securely, the crypto industry created a standard called SLIP39 (Shamir-based Linear Integer Partitioning). Instead of a standard 12/24-word BIP39 list, SLIP39 generates distinct sets of 20/33-word shares specifically engineered to mathematically reconstruct the master private key without compromising security.
Using the Seedmate BIP39 Shamir method allows you to split and backup your existing recovery phrase, so you don’t have to migrate your funds or stick to SLIP39 hardware. The disadvantage is that other manufacturers don’t implement this Shamir BIP39 scheme, so you will need the SEEDMATE hardware to recover the master mnemonic, or alternatively use the free backup HTML tool in a strictly offline environment.
Another advantage is that even if someone gathers enough shares it is unlikely that he would be able to combine them without the appropriate instructions. Make sure your loved ones have access to proper instructions in case something happens!
Important: you need to write down k value (threshold) and the id of each share in order to recover/merge correctly. So each share would look like this:
k=3
Id: 1
actor
reveal
benefit
donkey
twin
adjust
seed
ankle
oil
scan
chase
water
Or store k and shares id in a different location (or even on a cloud server). This way if someone finds a share they do not have a clue that it is part of a Shamir scheme. But you cannot lose this map to reconstruct. In a simple 2/3 scheme you could still manually test all combinations.
k=3
Id 1 starts with word ‘actor’
Id 2 starts with word ‘buyer’
Id 3 starts with word ‘abandon’
Id 4 starts with word ‘zoo’
Id 5 starts with word ‘plane’
Test properly before moving funds!
Entering a wrong id of a share does not produce an error, it would produce a different invalid result mnemonic. But entering repeated share ids does generate an error.
Each share is a valid BIP39 mnemonic with the same size as the master mnemonic, and can be used as decoy with small funds. If those funds move you know that share has been compromised.
