NETWORK · operating reference

BIP-32 receive-only address derivation

A guide to deriving public receive addresses from an extended public key without exposing a corresponding private key.

Reference center

What this page establishes

An extended public key can derive non-hardened child public keys.

Sharing an xpub reveals address relationships and can reduce privacy.

A derived address must be independently verified before it appears on an invoice.

Bitcoin BIP-32 specification

Practical review sequence

1

Submit an xpub only; reject every extended private key.

2

Confirm the intended network, script type, branch, and index.

3

Compare the derived address with trusted wallet software before receiving funds.

Open receive-only manager

Recheck primary sources before acting

Contracts, names, issuers, governance, bridges, providers, networks, fees, and access rules can change. CoinPork provides an operating checklist, not financial, legal, tax, accounting, or cybersecurity advice.