For educational purposes only; not security or investment advice. Blockchain transactions can be irreversible. Never disclose a private key or recovery phrase, and verify every transaction before signing.
Direct answer
A public-private key pair is an asymmetric cryptographic relationship used to authorize and verify blockchain actions. The private key is secret data used to create digital signatures. The corresponding public key can be shared and lets others verify those signatures without learning the private key.
A blockchain address is usually derived from a public key or from a script or account rule; it is not universally identical to the public key. The derivation and address format depend on the network. An address identifies a destination or account, while control normally depends on satisfying that network’s spending or authorization rules.
Holding a private key does not place coins inside the wallet. The ledger records assets or spendable outputs, and the key lets its holder authorize valid state changes. Anyone who obtains the key may be able to sign as the holder, while losing the only usable key can make self-custodied assets permanently inaccessible.
How it works
The basic signing flow is:
- Wallet software generates a private key from cryptographically secure randomness, or derives it from a wallet seed according to a defined scheme.
- A one-way mathematical operation derives the matching public key. Deriving the private key from the public key should be computationally infeasible when the algorithm and implementation are secure.
- The network’s rules derive or associate an address, script, or account with the public key. Different networks can use different curves, hash functions, encodings, and account models.
- The wallet signs a specific transaction or message with the private key. A signature applies to the exact encoded data; changing that data invalidates the signature.
- Network participants use the public key and protocol rules to verify the signature before accepting the authorized action. Verification reveals no private key.
A recovery phrase is not the same object as a private key. In many hierarchical deterministic wallets, the phrase represents entropy used to recreate a seed, from which many keys and addresses are derived. Whoever learns that phrase may therefore gain control over every derived account. A wallet password usually encrypts or unlocks a local wallet file; it does not replace the underlying keys and cannot restore them by itself.
Public-private key control also does not describe every blockchain account. For example, an Ethereum externally owned account is controlled by a key pair, whereas a contract account is controlled by its deployed code and may enforce multisignature, time-delay, or recovery rules.
Example
Alice gives Bob a receiving address. Bob’s wallet checks the network and address format, constructs a payment, and asks Bob to confirm the recipient, amount, and fee. The wallet signs the exact transaction locally with Bob’s private key and broadcasts the signed transaction; the private key itself is never sent to Alice or the network.
Nodes verify the signature and the relevant spending rules. A valid signature shows that the transaction was authorized by the required key, but it does not prove Bob’s legal identity, that Alice is trustworthy, or that the transaction is economically sensible. If Bob signs data for the wrong network, recipient, or contract action, correct cryptography can still authorize the wrong outcome.
Risks
- Disclosure: Phishing, malware, cloud backups, screenshots, browser extensions, or fake support agents can expose a private key or recovery phrase. Treat either as full-control material.
- Loss: A destroyed device, forgotten passphrase, incomplete backup, or incompatible derivation settings can prevent recovery. Test the documented recovery process without exposing the secret.
- Bad randomness or software: Predictable key generation, flawed signature code, supply-chain compromise, or a malicious wallet can defeat otherwise sound cryptography. Use maintained software and reputable signing devices.
- Signing ambiguity: A signature may authorize a transfer, token approval, order, login, or other message. Read the human-readable intent and independently verify the encoded details, network, address, and amount.
- Operational concentration: One key controlling all assets creates a single point of failure. Separate balances and duties where appropriate, minimize online exposure, and consider hardware signing, multisignature, or policy-controlled accounts for higher-value use.
If a private key or recovery phrase may have been exposed, assume it is compromised. From a clean device, create a new independently generated wallet, verify its backup, and move remaining assets and required permissions when it is safe to do so. Do not type the old secret into a website that claims it can check or repair the wallet.
Common misconceptions
Myth 1: A private key is just a wallet password
A password may protect a local app or encrypted keystore. The private key authorizes signatures, and resetting the app password does not recreate a lost key or recovery phrase.
Myth 2: An address and a public key are always the same
Address construction is protocol-specific. Many addresses encode a hash, script, or account rule rather than the raw public key, and some contract addresses do not have a private key at all.
Myth 3: Sharing a public key lets someone compute the private key
Secure public-key systems are designed so that public keys and signatures can be shared. The practical threats are weak randomness, flawed implementations, exposed secrets, and future breaks in the cryptography, not ordinary verification.
Myth 4: A valid signature proves who the signer is
It proves that the required key authorized the signed data under the protocol’s rules. Linking that key to a real person or organization requires separate identity evidence.
Related topics
Sources
- Blockchain Technology Overview - NIST (accessed: 2026-08-21)
- Public Key - NIST Computer Security Resource Center (accessed: 2026-08-21)
- Wallets - Bitcoin Developer Documentation (accessed: 2026-08-21)
- Ethereum Accounts - Ethereum.org (accessed: 2026-08-21)