Glossary / Addresses & keys
Parent key
Also known as Parent public key, Parent private key.
- Definition
- The parent key sits one level directly above another key in an HD wallet's tree, and every extended key carries four bytes that fingerprint its own parent.
Specified in BIP-32.
Parenthood in BIP-32 is a relation, not a rank. The master key is the only key with no parent, and it records that fact with a parent fingerprint of four zero bytes and a depth of 0. Everything else names its parent in the opening bytes of its own serialization, which is how software works out where a stray key belongs.
How it works
A parent key is identified by a fingerprint rather than by the key itself. Take the parent's compressed public key, hash it with SHA-256 and then RIPEMD-160, and keep the first four bytes of the result. Those four bytes sit in the child's 78-byte extended key at a fixed position, immediately after the depth byte and before the child index.
Four bytes is 4,294,967,296 possible values, which makes a fingerprint a label rather than a proof. BIP-32 is explicit that fingerprints can collide and that implementations must not depend on them for security. They exist so a wallet can sort keys into the right tree quickly, and any real check involves deriving the key and comparing the result.
The parent also supplies both ingredients a derivation needs: its chain code and its key material. That is why extended keys travel as a pair. Hand somebody a parent public key without the chain code and no child can be computed from it at all.
Where you see it
The fingerprint of the master key is the identifier you meet most often, because descriptors and signing devices both quote it.
An output script descriptor writes it in brackets ahead of the extended key, as in wpkh([1a2b3c4d/84h/0h/0h]xpub.../0/*). The bracketed part states which wallet the key came from and by what route, so a signer reading the descriptor can tell whether it is being asked to sign with a key it actually holds. Partially signed bitcoin transactions under BIP-174 carry the same pairing for every input and output, which is what lets a hardware wallet decide offline that an output is its own change rather than a stranger's address.
Multisig is where this stops being trivia. A two-of-three setup in Sparrow displays a master fingerprint for each cosigner, and rebuilding that wallet later needs all three extended public keys as well as the seed phrases. Writing each device's fingerprint on its backup card is the cheapest way to tell three otherwise identical seed cards apart years afterward, and people who skipped it have spent weekends deriving keys to work out which card belongs to which device.
One last practical note. A restored wallet showing an unfamiliar fingerprint is usually not a corrupted backup, it is a mistyped passphrase. A BIP-39 passphrase produces a different master key and therefore a different fingerprint, so comparing that short value is a fast and safe way to confirm you entered the passphrase correctly before you go looking at a balance.