Why it exists
BIP 389 lets one descriptor express several related derivation branches. Receiving and change descriptors often differ by only one path component; a multipath expression can record those alternatives together without duplicating the rest of the wallet definition.
How it works
An expression such as XPUB/<0;1>/* expands into a receiving branch using /0/* and a change branch using /1/*. The angle brackets describe alternatives at one derivation step, while the wildcard still selects successive addresses within each branch.
When several keys contain alternatives, their tuples must have equal lengths and expand in lockstep. The first option from each key belongs to one descriptor, the second options to another. This is not a Cartesian product of every possible branch combination.
A practical example
A 2-of-3 multisig descriptor can give all three account keys the suffix /<0;1>/*. Its first expansion derives each cosigner through /0 and produces receiving scripts; its second uses /1 for all cosigners and produces change scripts. The same policy stays consistent across both.
What to keep in mind
An importer must understand multipath syntax or receive the separately expanded descriptors. A descriptor that preserves only receiving addresses can miss change during recovery. The tuple does not grant access to hardened derivation from public keys or replace the secret keys required to sign.
Status & implementation
The official BIP remains Draft. Core 31.0 documentation includes multipath expressions and an import example for a complete multisig account. That is implementation evidence despite the Draft label, not proof of support across all wallet software.
Specification status: Draft · Sources checked 13 November 2026
