Imagine opening your Bitcoin recovery kit and discovering that you did almost everything right.

You built a 2-of-3 multisig wallet.

You separated the signing devices.

You backed up the seeds.

You accepted the extra complexity because you wanted to survive losing one key without trusting a company to return your money.

Years later, one signer is gone. Two seeds survive. That is exactly the failure your setup was supposed to handle.

Then you discover that the laptop containing the wallet configuration is gone, too. So is the only other copy of that file.

You can recreate your two signing keys. You cannot recreate the missing cosigner’s public-key information. You no longer have everything needed to reconstruct the original wallet scripts.

The Bitcoin is still on the blockchain. The network is still running. Your surviving seeds are correct.

Your recovery plan may nevertheless have failed.

This is the uncomfortable gap between owning enough keys to satisfy a spending rule and preserving enough information to reconstruct that rule.

Bitcoin culture has spent years teaching people to protect their seeds. It has been much less successful at explaining everything else that might need to survive alongside them.

That is what makes BIP138 interesting.

Meet BIP138 : A Backup Without Another Password

Bitcoin Optech’s September 25, 2026 newsletter highlighted its addition to the BIPs repository. The proposal describes a way to encrypt wallet recovery information using public-key material already associated with the wallet, allowing an eligible cosigner to recover that information without remembering another password.

The convenience is obvious. The privacy implications take a little longer to sink in.

The information that opens your backup may be information you already gave away.

Before going further, the status matters. BIP138 is a draft application-layer specification. It does not change Bitcoin’s consensus rules, and its publication does not mean every wallet now supports it. Its listed author is Pyth ; it builds on an earlier backup design discussed by Salvatore Ingala and other developers.

Think of it as a proposed common language for a neglected part of self-custody : keeping the wallet’s instructions recoverable without exposing them unnecessarily.

The proposal deserves attention because the problem will outlive whichever hardware wallet is fashionable this year.