A new SLIP39 backup can leave an earlier recovery route open.
In my public-data experiment, a prior single-share backup, a prior 2-of-3 backup, and a new 2-of-3 backup all recovered the same underlying value. They used the same identifier and extendable format. This was not a device upgrade test.
That makes earlier backup sets part of the inventory, even after a new set exists. More shares do not, by themselves, revoke leaked recovery material.
The write-up includes all 77 expected outcomes, a reproducible test package, and a blank checklist. The 77 include deliberate refusals and wrong-passphrase results, not just successful recovery.
No hardware wallet, signing, or inheritance procedure was tested. Use the package only with its public dummy data, never real recovery words or funds. This is not an instruction to discard old backups.


CypherpunkGuide
SLIP39 Backup Recovery: What Enough Shares Cannot Prove
Test what SLIP39 shares can restore, why a wrong passphrase can return a different result, and why creating another backup does not revoke the earl...
