In one sentence
The discipline that protects information using mathematics: it turns readable data into codes that are unreadable to anyone without the key.
Cryptography is the discipline that protects information using mathematics: it turns readable data into codes that are unreadable to anyone without the key. It’s the technology that makes cryptocurrencies possible, and it gives them the first half of their name.
You use it every day without seeing it. When you send a WhatsApp message, when you log into your bank, when the browser shows the lock icon next to the address bar: in every case, cryptography is encrypting the communication so only the legitimate recipient can read it. Cryptocurrencies took that same toolbox one step further: instead of protecting messages, they protect money.
Cryptography, a craft with centuries of history
Encrypting messages is as old as war itself. Julius Caesar shifted the letters of the alphabet to write to his generals; the Spartans wrapped strips of leather around rods of a secret thickness. The modern version was born in World War II, when cracking the Nazis’ Enigma machine (the work of Alan Turing and the Bletchley Park team) shortened the war and, along the way, founded computing.
The leap that made digital money possible arrived in the 1970s with public-key cryptography: a system with two mathematically linked keys, where what one encrypts only the other can decrypt. For the first time, two strangers could communicate secretly without ever having met to agree on a password. Bitcoin is, at its core, an application of that invention.
The two cryptographic pieces that cryptocurrencies use
The first is the hash: a function that turns any data (a word, an entire book) into a fixed-length digital fingerprint. The same data always produces the same fingerprint, but changing a single comma produces a completely different one, and it’s impossible to reconstruct the original data from it. The blockchain chains its blocks together with hashes: that’s why altering an old transaction would visibly break the entire chain.
The second is the digital signature. Your private key signs every transaction, and anyone can verify with your public key that the signature is yours, without the private key ever being revealed. It replaces the handwritten signature, the bank, and the notary all at once: mathematical proof that the owner of the funds authorized the transfer.
How hard is it to break cryptography?
The numbers quickly stop making sense. A Bitcoin private key is a number between 1 and 2 to the power of 256, a quantity comparable to the number of atoms in the observable universe. Trying random keys with every computer on the planet working together wouldn’t make a dent in millions of years. Crypto funds that get stolen aren’t stolen by breaking cryptography, but by tricking people into handing over their keys, which is infinitely easier.
What happens, cryptographically, when you send Bitcoin
Your wallet takes the transaction data (how much, to which address), signs it with your private key, and broadcasts the signed transaction to the network. Thousands of nodes verify the signature against your public key: if it’s valid, the transaction enters the mempool and then a block, whose hash gets chained to the previous block. At no point does your private key leave your device. The entire system rests on that asymmetry.
The cryptography you don’t see: one seed, all your keys
Behind every modern wallet there’s an extra layer of mathematical elegance: hierarchical deterministic (HD) wallets. Your seed phrase encodes a master number, and from that number the wallet derives, through cryptographic functions, an entire tree of private keys and addresses: one for each asset, a new one for each transaction if needed. That’s why a single 12- or 24-word backup recovers all your accounts: it doesn’t store the keys, it stores the seed from which they’re all recalculated, identically, on any device in the world.
The same derivation principle explains why addresses can be shared without fear: every link in the chain (seed → private key → public key → address) works in only one direction. Moving forward is trivial; going backward is computationally impossible.