Public and private keys, explained properly

A public key and a private key are a matched pair of very large numbers. The private key is a secret only you hold. The public key is derived from it and can be shared with the world. In cryptocurrency, control of the private key is what lets you move funds, and the public key — or an address derived from it — is where others send funds to you. Get that split straight and most of crypto security stops feeling arbitrary.

What the two keys actually are

Public-key cryptography, also called asymmetric cryptography, uses two mathematically related keys instead of one shared password. The relationship runs one way. It’s easy to calculate the public key from the private key, but computationally infeasible to work backwards from the public key to the private one. That asymmetry is the entire point — it lets you publish one half of the pair to everyone while keeping the other half locked away.

Most cryptocurrencies, Bitcoin and Ethereum included, use elliptic-curve cryptography (a curve called secp256k1) to generate these pairs. You don’t need the maths to use it, but the takeaway is worth holding onto: a private key is effectively a random number pulled from a range so vast that guessing someone else’s key isn’t a realistic attack. The security rests on that sheer size — not on keeping the method secret.

How keys prove ownership without revealing themselves

When you send cryptocurrency, you’re not typing a password into a central server that checks it against a list. Your wallet builds a digital signature instead. Signing takes two inputs — the transaction details and your private key — and spits out a signature anyone can verify with your public key. That verification confirms two things at once: the signer held the matching private key, and the transaction hasn’t been altered since it was signed.

Here’s the elegant part. The signature never exposes the private key. Each one is specific to the exact transaction it authorises, so it can’t be lifted and pasted onto a different payment. This is how a fully public network lets you prove control of funds without ever transmitting the secret that grants that control. Want to see how those signed transactions then get accepted by the network? We cover it in how a crypto transaction gets confirmed.

Keys, addresses, and why they are not the same

People throw “public key” and “address” around as if they’re identical. They’re not. An address is usually derived from the public key by running it through extra hashing and encoding steps. The result comes out shorter, packs in an error-checking component so typos get caught, and hides the raw public key until you actually spend from it.

A rough way to keep the three layers straight:

This layering is exactly why sharing your address to receive a payment is completely safe. It reveals where funds can arrive — not how to move them.

Seed phrases: the human-friendly form of a private key

Juggling raw private keys by hand would be a disaster waiting to happen, so modern wallets use a seed phrase — also called a recovery phrase or mnemonic — typically 12 or 24 ordinary words. That phrase is a human-readable encoding of the master secret, from which your wallet mathematically derives all its private keys and addresses. The standard behind it is published openly as BIP-39.

And here’s the consequence that really matters: your seed phrase is your money. Anyone who reads it can regenerate every key in your wallet and walk off with the funds — on any device, without your phone or your password. Lose it with no backup and the keys can’t be recovered; the funds are gone, unreachable for good. There’s no support line to reset it, because nobody else holds a copy. That’s not a flaw. It’s the whole design working as intended.

Custodial versus self-custody: who holds the key

Whether you personally handle keys comes down to how you hold your crypto. In self-custody, your wallet stores the private keys and you alone can sign. In a custodial arrangement — most centralised exchanges — the company holds the keys, and you hold an account balance that’s really a claim against them, controlled by a normal login. The old line “not your keys, not your coins” captures the trade-off neatly: custody hands convenience and account recovery to a third party, in exchange for trusting them with the keys.

Neither model is universally right; they simply carry different risks. Self-custody kills counterparty risk but dumps the entire burden of key security on you. Custody lifts that burden but drags back in the very intermediary that public-key cryptography was built to make optional. Pick your poison knowingly.

Protecting a private key: the defensive basics

Because a private key or seed phrase grants total control, most real losses come from the secret being exposed or lost — not from anyone cracking the cryptography. So sensible defence zeroes in on where that secret lives:

• Keep the seed phrase offline. Write it on paper or stamp it into metal. That keeps it away from malware, cloud backups, and screenshots that quietly sync to a server.
• Never enter it into a website or share it. No legitimate wallet, exchange, or “support agent” ever needs your seed phrase. Any request for it is a theft attempt — full stop.
• Beware fake apps and lookalike sites. A common attack tricks you into typing your phrase into a convincing clone. Download wallets only from official sources, and check addresses carefully.
• Consider a hardware wallet for larger amounts. These devices keep the private key sealed inside dedicated hardware and sign transactions internally, so the secret never touches an internet-connected computer.

Notice the pattern — every one of these defends the secret itself. The cryptography isn’t the weak point. The handling of the key is, every time.

Why randomness is the quiet foundation

Everything above leans on one assumption that’s easy to overlook: that your private key was chosen at random from an unimaginably large range, so no one else could ever land on the same number. The security of the whole scheme depends less on the elegance of the maths than on the quality of that randomness. Generate keys from a weak or predictable source and an attacker who spots the flaw can regenerate them — without breaking the underlying cryptography at all.

This isn’t just theory. There have been real cases where funds were stolen because keys came from flawed software with poor randomness, or from human-chosen “brain wallet” passphrases that turned out to be guessable. The lesson for an ordinary user is reassuring rather than scary: reputable wallets handle key generation properly, drawing on strong sources of randomness. That’s precisely why you should let a trusted wallet create your keys and seed phrase instead of trying to invent them yourself. A phrase you dreamt up in your head is far easier to guess than one a good wallet generates — human brains are lousy random number generators.

What this means

Public and private keys turn a hard problem — proving you own something on a network with no central authority — into a routine operation. The public key and address let the world pay you and check your signatures; the private key, usually experienced as a seed phrase, is the one thing that authorises spending. Once that division clicks, the security rules stop feeling arbitrary. You can share an address without a second thought, and you must guard a seed phrase as though it were the funds themselves — because functionally, it is. If any of the underlying ideas here are new to you, it helps to start with what a blockchain actually is.