Why it exists
BIP 85 derives reproducible entropy for other applications from a BIP 32 root. One use is generating separate child wallet recovery phrases, so the parent backup can recreate them without putting the same recovery words into every wallet.
How it works
The application selects a defined hardened derivation path under purpose 83696968'. The derived private-key material is processed with the specified HMAC construction to obtain entropy. Each application defines how much entropy it needs and how to encode it.
For BIP 39 child phrases, the path records the mnemonic application, language, word count and child index. These settings are part of the recovery instructions. Deriving another index produces another child backup, rather than another account under the child wallet.
A practical example
A compatible device can derive an English twelve-word wallet at index zero and a second one at index one. Either child phrase can initialize a compatible BIP 39 wallet. Repeating the same parent, application and index reproduces the same child phrase.
What to keep in mind
The parent can recreate all children, so compromising it has a broad impact. Losing a child does not reveal the parent under the scheme’s assumptions, but a child wallet remains exposed wherever its phrase is entered. BIP 85 is not secret sharing and does not remove the need for child-wallet metadata.
Status & implementation
The BIP is Deployed. COLDCARD documents a deterministic-entropy export workflow, including selection of output type and index. A receiving wallet only needs to understand the resulting backup format; reproducing it from the parent requires BIP 85 support.
Specification status: Deployed · Sources checked 13 November 2026
