Extended Public Key (xpub)
Abbreviation: xpub
Pronunciation: ik-STEN-did PUB-lik KEE (EKS-PUB)
Also known as: BIP32 Extended Public Key, xpub
Definition
An extended public key, commonly displayed as an xpub or a related network-specific prefix, combines a public key with derivation information.
Overview
What it means
An extended public key, commonly displayed as an xpub or a related network-specific prefix, combines a public key with derivation information. It can generate many child public keys or receiving addresses without exposing the corresponding private keys.
How it works
Hierarchical deterministic wallets derive branches of keys from a master seed. An account-level extended public key permits watch-only software to derive public receiving addresses along non-hardened paths. Derivation scheme and account path matter, so two wallets using the same seed can show different address groups.
Understanding the technical details
Choose derivation scope deliberately. A service may need only one account branch rather than the wallet’s broader master-level extended public key. Store the derivation path and address type, and monitor the wallet gap limit when addresses may be generated but not used immediately. Exporting xpubs to third-party analytics systems exposes relationships among deposits; privacy review belongs in the architecture, even when spending keys never leave secure hardware.
Additional protocol context
An xpub cannot normally sign transactions, but it is not harmless public information. Anyone with it may derive addresses and observe activity across the exposed branch, weakening financial privacy. In certain derivation conditions, combining a parent xpub with a leaked non-hardened child private key can endanger parent private material.
Organizations should expose only the narrowest required branch, separate environments and customers, control API access, and avoid publishing xpubs. Monitoring systems must store derivation paths and script types accurately. Rotation or migration may be needed after leakage even when funds cannot be spent directly.
Common failures and limitations
An xpub is highly sensitive for privacy: disclosure can expose many linked addresses and transaction histories. Combining an extended public key with a compromised non-hardened child private key can also endanger a broader wallet branch in affected designs.
Related concepts
Crypto Wallet, Private Key, Seed Phrase.
Further reading
Example
A donation website uses an extended public key to generate a fresh Bitcoin address for every donation. The web server can monitor those addresses while the private signing keys remain offline on a separate device.
Comparison
An xpub is not a seed phrase or private key: it normally permits observation and public derivation, not spending. A single public address reveals much less of the wallet’s full address tree.
Key Takeaway
An xpub is highly sensitive for privacy: disclosure can expose many linked addresses and transaction histories.
Sources
- Recommendation for Key Management: Part 1 – General — NIST (2026-08-02)
- Recommendation for Key Management: Part 2 – Best Practices for Key Management Organizations — NIST (2026-08-02)
- BIP 32: Hierarchical Deterministic Wallets — Bitcoin Improvement Proposals (2026-08-02)