BIP85 for Mortals
How to stop managing ten recovery phrases with a single one

If you have ever had more than one bitcoin wallet, you already know the problem. Each one has its own recovery words, its own piece of paper stored somewhere safe, its own mental note about where it is and what it is called. With two wallets, it is manageable. With five, it starts to become chaos. With ten, it is a time bomb.

BIP85 is the answer the Bitcoin ecosystem took years to formalize. The idea is simple and powerful at the same time: instead of managing a collection of independent seeds, you generate them all from a single one. One master seed. The rest are derived from it in a mathematical, predictable way, without any of the derived ones compromising the original.

Why having multiple wallets makes sense — and why it is a problem

Separating funds is a reasonable practice. One wallet for everyday use with small amounts, another for long-term savings that you do not touch, one for family-related funds, another to test a new app without risking anything important. That separation is good self-custody hygiene.

The problem is the operational cost. Every new wallet means a new seed phrase: between 12 and 24 words that represent complete access to those funds. Losing them is the same as losing the wallet. If someone finds them, that someone has the wallet. So they need to be stored properly, in secure and separate physical locations, and you need to remember which set of words belongs to which wallet.

Most people end up simplifying in dangerous ways: reusing phrases, storing several in the same place, or simply giving up on separating funds because the maintenance is too tedious. The result is worse than not having tried.

BIP85 solves that conflict at the root.

What exactly is a seed, and why does it matter?

When you create a bitcoin wallet, the device or application generates a set of words — usually 12 or 24 — known as a seed phrase or recovery phrase. In practice, those words are the wallet. Whoever has them has access to the funds. Whoever loses them loses access forever.

A seed phrase is not a password you can change or reset. It is the mathematical root from which all the wallet’s keys are derived. Without it, there is no recovery.

BIP85 starts from that same principle and extends it: if one seed phrase can generate a whole tree of keys, why not also use it to generate other complete, independent seed phrases?

How it works, without the math

Imagine a secret recipe that only you know. A unique combination of ingredients that no one else has. That recipe is your master seed.

BIP85 lets you create other recipes from it. The master recipe combined with the number 0 always produces the same derived recipe A. Combined with the number 1, it always produces the same derived recipe B. And so on, for as many as you need. Always the same result for the same ingredients: no randomness, no surprises.

That number that distinguishes each derivation is called the index. Index 0 always produces the same child seed. Index 1 always produces another one. They are deterministic: given the same master seed and the same index, the result is always identical. There is no randomness involved.

What makes this useful and secure at the same time is that the process only works in one direction. Whoever has the child seed cannot reconstruct the master seed from it. The parent can generate children; the children reveal nothing about the parent.

Child seeds can be generated in whatever length you prefer: 12, 18, or 24 words, depending on what you request when deriving them. In every respect, they are standard BIP39 phrases.

What it is useful for in practice

The most direct application is managing multiple wallets with a single backup.

A daily spending wallet derived with index 0. A long-term savings wallet with index 1. One to give a family member access to part of your funds without revealing the main seed, with index 2. Under the conventional system, each of those wallets needs its own separate set of words stored independently. With BIP85, they all come from the same master seed, and it is enough to protect that one secret.

The child seed you derive is a completely normal, standard seed phrase, compatible with any wallet that follows BIP39. It carries no special marker. Whoever receives it does not know it is a derivation: it works exactly like any other seed phrase.

This has an important practical consequence for inheritance and delegation. Emergency instructions for a family member or executor become simpler: one master phrase, plus a list of which index corresponds to which wallet. Much more manageable than multiple sealed envelopes with independent phrases.

The advanced use almost no one mentions: derived passphrases

There is a BIP85 use case that rarely appears in educational content and that, for anyone already practicing self-custody with some seriousness, is probably the most interesting one: deriving BIP39 passphrases from the master seed.

A BIP39 passphrase — the “25th word” — is an optional extra layer added to a seed phrase to create a different hidden wallet. It is one of the strongest defenses against physical coercion and against accidental discovery of your backup phrase. The classic problem is that the passphrase itself also has to be remembered or stored, and if you lose it, you lose access to the hidden wallet even if you still have the seed phrase.

BIP85 solves that: instead of inventing a passphrase and memorizing it, you derive it mathematically from your master seed using an index. If you ever lose it, you regenerate it. And because each index produces a different passphrase, you can have multiple hidden wallets reproducible from a single root secret, without having to store anything extra.

The same logic applies to alphanumeric passwords for external services. Reproducible, strong, and independent of any third-party password manager.

What happens if you lose a child seed

This is the question that feels most reassuring once you hear the right answer.

Suppose you have a daily-use wallet derived with index 1, and the paper where you wrote down its words gets lost or destroyed. With your master seed, and knowing you used index 1, you can regenerate that exact same child seed at any time from any compatible device. The funds are not lost.

The process is straightforward: you enter the master seed into a BIP85-compatible device, specify the index, and the device regenerates the exact child phrase. You import it into the destination wallet and recover full access.

What is irreversible is losing the master seed. If that happens, you lose access to every wallet derived from it, without exception. The master seed is the single critical point of the whole system. All the complexity reduction BIP85 offers comes with that trade-off: the responsibility for custody is concentrated into one secret.

There is one good practice before moving real funds: generate a child seed with a specific index, write down which index you used, delete the child, and then regenerate it from the master to verify that it matches. Only once you have confirmed that the recovery cycle works correctly on your device should you move real funds into those wallets.

What BIP85 does not do

It is worth being precise about its limits.

BIP85 does not encrypt your funds or add any extra protection to real-time wallet access. Its function is to manage the generation and backup of seeds. It is not an extra lock on transactions.

It also does not eliminate custody risk: it concentrates it. If you used to have five seeds and now you have one, that master seed becomes the single point of failure for the whole system. More operational simplicity means more weight on that one secret. Anyone using BIP85 seriously should give that master seed the same level of care — or more — than they used to give five separate seeds. A steel plate, not paper. Two physical locations, not one. Never photographed, never stored digitally.

Finally, BIP85 requires explicit support from the device or application you use. Not every hardware or software wallet implements it, and support status changes with firmware updates. Coldcard by Coinkite is the reference implementation and the most mature one. Ian Coleman’s web tool can also calculate it manually, with the essential precaution of downloading the HTML and always using it with the device offline.

Why it is worth knowing about

Most bitcoin lost in self-custody was not lost to sophisticated hacks or protocol failures. It was lost to management mistakes: poorly stored phrases, forgotten backups, destroyed papers, heirs without clear instructions, abandoned wallets because maintaining so many separate phrases was simply too much work.

That is the real problem of self-custody, and it is one of the few areas where there have been very few structural improvements in the last decade. BIP85 is one of them. It does not remove risk — it reorganizes it, concentrates it, makes it manageable. One well-protected secret is, in practice, a safer system than five poorly protected ones, even if at first glance it seems like the opposite.

For someone already managing multiple wallets seriously, ignoring BIP85 comes with a real operational cost that grows with every new wallet, every hardware change, and every delayed inheritance conversation. It is one of those quiet pieces of infrastructure that does not solve anything in a spectacular way, but the day you need it, it saves you exactly the kind of mistake that can ruin years of savings.

To go deeper

— BIP85, official specification. The technical document, concise and readable if you want the detail.
— Ian Coleman’s BIP39/BIP85 tool. Useful for understanding how the output changes with the index. Always use it offline: download the HTML, disconnect from Wi-Fi before opening it, and ideally use it on a machine that is not part of your everyday setup.
— Device support documentation: Coldcard, BitBox02, Passport. Always verify BIP85 support against the current firmware before depending on it.