Bitcoin gets a standard backup format for the wallet data a seed phrase cannot hold
Serguey Asael Shinder1 min readBIP139, a wallet metadata backup format, was merged into the Bitcoin Improvement Proposals repository. A seed phrase restores the keys but not the context a wallet needs to use them — which descriptors it tracks, address labels, when the wallet was created so a restore knows how far back to scan, the gap limit, and which signing devices are involved. BIP139 defines a single portable format for exactly that. Among its mandatory fields are the version, type, descriptor and key; it records a birth block rather than loose account timestamps, carries a change descriptor, signer modality and device records, BIP85 application and index, and an explicit encoding for BIP352 silent-payment labels. Field definitions live in a companion registry, and the design is documented against a survey of existing wallets including Bitcoin Core and Bitkey.
What it means
The seed phrase has always been an incomplete backup, and everyone who has restored a descriptor wallet into empty-looking balances knows it — the keys came back, the knowledge of what to look for did not. Standardising the rest is the unglamorous work that makes self-custody survivable across software changes and across wallets. The decisions visible in the commit history are the right ones: making core fields mandatory so a backup is either complete or rejected, pinning a birth block so a restore does not rescan the whole chain, and pushing field definitions into a registry so the format can grow without a new BIP each time. A format is only as useful as its adopters, so the survey of real wallets is the part that decides whether this becomes interchange or another spec nobody writes to.