A Bitcoin address is not the same thing as a public key, and neither is a wallet. The terms are often compressed into “where you receive bitcoin,” but the distinctions matter when backing up funds, checking a payment or evaluating privacy.
Four objects, four jobs
- Private key: secret data used to produce a valid signature authorising a spend.
- Public key: derived from the private key and used by the network to verify a signature.
- Address: a user-facing encoding of a payment condition or script information. It includes error-detection features and is designed to be shared.
- Wallet: software or hardware that manages keys, creates addresses, tracks transactions and constructs signatures. A wallet can control many keys and addresses.
The Bitcoin developer guide describes how a secp256k1 private key is used to derive a public key and how public-key data can be hashed and encoded for payment. Modern Bitcoin addresses can represent several script types, so “an address is a public key” is not a safe general definition.
What can safely be shared?
A receiving address is intended to be given to a payer. Sharing it does not give that person the ability to spend the funds. A private key or seed phrase must never be shared. Anyone who obtains the secret can normally authorise transactions, and there is no password-reset desk at the protocol layer.
Extended public keys require more care. An xpub or similar account-level public key can allow a wallet or service to derive a large set of addresses and observe their activity. It generally cannot spend funds, but disclosing it may reveal a much broader financial history than sharing one receiving address.
Why address formats differ
Bitcoin has introduced new script and address formats as its transaction capabilities evolved. Prefixes and lengths can differ, while other blockchains use entirely different encodings. A valid-looking string on one network may be unusable on another. Wallet interfaces should identify both the asset and network before presenting an address.
Do not manually edit an address. Copy it through a trusted interface, compare the beginning and end on a separate screen where possible, and make a small test transaction when the amount or destination is material. Clipboard malware can replace an address after it is copied.
Public does not mean anonymous
Bitcoin transactions are recorded on a public ledger. Our transaction privacy guide examines the operational consequences. Addresses are pseudonyms, but activity can be linked through address reuse, transaction patterns, exchange records and information disclosed to a counterparty. Bitcoin.org’s privacy guidance recommends using a new address for each payment and warns that balances and transaction histories are visible once an address is known.
Generating a fresh address does not erase every link. A later transaction that spends several inputs together may reveal common control, while change outputs can create additional clues. Privacy is a system property involving wallet behaviour, network connections and the services used to acquire or spend coins.
How signatures prove control
When a wallet spends bitcoin, it constructs transaction data and signs it with the relevant private key. Nodes can check the signature against the public key or spending condition without learning the secret. That is the core benefit of public-key cryptography: public verification without disclosing the signing key.
A signature proves control of a key for the signed message; it does not prove the signer’s legal identity unless some separate evidence connects that key to a person or organisation.
A safer mental model
Think of the wallet as a key manager, the private key as signing authority, the public key as the verification counterpart and the address as payment-routing information. Back up the wallet’s recovery material offline, verify every destination and treat account-level public data as sensitive even when it cannot directly spend funds.
