A Simple Guide
Bitcoin is a digital currency system that lets people send money to each other without banks or governments. It runs on a network of computers worldwide that work together to keep everything honest and secure.
Rather than physical coins, Bitcoin is really just a record of who owns what. When you send Bitcoin to someone, the network records that transfer permanently. Think of it like a giant shared notebook that everyone can see but no one can erase. These records (called transactions) get grouped into blocks, which are then chained together — forming the blockchain. Once a transaction is recorded and a few more blocks are added on top, it becomes permanent and irreversible.
Usually one person, but the system is flexible. You can send to individuals, groups, or even automated programs using different methods — with names like P2PKH, multisig, and P2SH.
Under the hood, each transaction uses a simple scripting language to lock funds. The recipient unlocks them by proving they're the rightful owner. Most people never see this — wallets handle it automatically.
Bitcoin uses strong math-based locks called cryptography. Only the intended recipient has the "key" to unlock and spend the funds. As an extra layer of security, your public key isn't even stored openly on the blockchain until you spend — just a scrambled version of it called a hash.
Bitcoin is essentially a chain of secure, verified transfers — each one locked with a puzzle, solved by the right person, and written permanently into a global ledger that no single person controls.
It also inspired many other technologies — including the broader concept of blockchains and the Lightning Network for faster everyday payments. The sections that follow explore each of these building blocks one by one.
Bitcoin is a global shared ledger — secured by math, controlled by nobody, and open to everyone.
- Bitcoin has no central authority — no bank, no government. Who do you trust more: a bank, or math? Why?
- If Bitcoin is just a record of who owns what, what stops someone from simply editing that record?
- Bitcoin transactions are permanent and irreversible. Is that a feature or a flaw?
Cryptography
Before Bitcoin existed, there was a beautiful idea: what if you could lock a message for someone without ever meeting them — using math alone?
Most of us have used a padlock. You lock it, snap it shut, and only your key can open it. Now imagine a magic padlock — one you can make thousands of copies of and hand out freely to strangers. Anyone can lock a message inside. But only you hold the key to open it.
That is precisely how public-key cryptography works. You have two keys. Your public key is mathematically derived from your private key — but crucially, this only works in one direction. Knowing the public key gives you absolutely no practical way to work backwards to the private key. One you share freely. One you guard with your life.
Think of your public key as your home address — anyone can send you a letter there. Your private key is the only key to your letterbox. You never hand that out.
The system also works in reverse for digital signatures. You can "sign" a message with your private key. Anyone who has your public key can verify the signature is genuinely yours — without ever seeing your private key. It's like a wax seal that only you can make, but anyone can check.
Bitcoin uses one additional tool: the hash function. Instead of storing your public key directly on the blockchain, Bitcoin stores a scrambled fingerprint of it — a hash. This adds an extra layer of privacy and, importantly, guards against future threats from quantum computers.
Public-key cryptography lets anyone lock data for you — but only you can unlock it, and you can prove that at any time.
- If your public key is truly public, why doesn't that make the system unsafe?
- What's the difference between encrypting a message and signing one? Why might you need both?
- Why does Bitcoin store a hash of your public key rather than the public key itself?
Cryptography (ECC)
Imagine you and a friend want to pass secret messages — but anyone could be listening. You need a lock that everyone can see, but only you have the key to open. That's exactly what ECC does — but with math. 🔢
ECC stands for Elliptic-Curve Cryptography. It is the specific branch of public-key cryptography that Bitcoin uses — and it's more powerful than the classic methods that came before it.
Draw a squiggly line on paper following the rule y² = x³ + 7 — that's Bitcoin's version, called secp256k1. That shape is an elliptic curve. The cool thing about it: if you draw a straight line through it, it almost always hits the curve at exactly 3 points. That geometric property is the foundation of everything that follows.
A finite field is also part of the picture. It is simply a finite set of numbers where all arithmetic — addition, subtraction, multiplication, division — always produces a result that stays within the same set. Think of it like clock arithmetic: on a 12-hour clock, 11 + 3 = 2, not 14. The math wraps around and stays contained. Without this boundary, numbers would grow infinitely large. The finite field keeps everything manageable — and ensures your public key stays the same compact 256-bit size as your private key.
Think of it like a hopping game on the curve. Everyone agrees on a fixed starting dot on the curve (called Point G). You secretly pick a number — say, 5 (in real life, it's a number with 77 digits!). You "hop" from the starting dot exactly 5 times, following the curve's rules. Where you land is your public key. The number 5 is your private key. You share where you landed. You never share how many hops you took.
A fixed base point called Point G is built into the Bitcoin protocol. Everyone uses the same starting dot.
A secret 256-bit number — astronomically large — chosen at random. This is your private key. You never share it.
Using the curve's mathematical rules, you add Point G to itself that many times. Each hop lands on a new point on the curve.
The final landing spot is your public key. You can share this freely with the world.
🔐 The trapdoor: It's easy to hop forward. But if someone only sees where you landed, they cannot figure out how many hops it took — not even with the most powerful computers on Earth.
Without a boundary, your numbers would grow infinitely large after all those hops — like a ball bouncing forever. The finite field puts walls in the room. When numbers hit the wall, they wrap around to the other side — just like in a video game. This keeps all calculations contained, and ensures every public key is exactly 256 bits long.
Old systems like RSA needed a key the length of 3,000 characters to be secure. ECC gives you the same security with only 256 characters. Same lock strength. Much smaller key. Much faster. That's why Bitcoin uses it.
| RSA (Old Method) | ECC (Bitcoin) | |
|---|---|---|
| Key length needed | 3,072 bits | 256 bits |
| Like a password of… | 3,000 characters 😱 | 256 characters 🎉 |
| Speed | Slow | Fast |
| Used in Bitcoin? | No ❌ | Yes ✅ |
🟡 ECC is like a hopping game on a special curve. Your private key is how many hops you took. Your public key is where you landed. Anyone can see where you landed — but nobody can figure out how many hops it took to get there. That's what keeps your Bitcoin safe.
- What makes a mathematical problem "hard enough" to be used in cryptography?
- If ECC uses a curve defined by a simple formula, why can't a hacker just plot the curve and reverse-engineer your private key?
Blockchain
Bitcoin needed a way for strangers — who don't trust each other — to agree on one version of the truth. The blockchain is how it solved that problem.
Picture a public notebook. Anyone can read it. Nobody can erase it. Every new page must reference the page before it, all the way back to the very first page. If you tried to alter an old page, every reference after it would instantly break — and everyone would know something was tampered with.
Each "page" is a block. Each reference is a hash — a unique fingerprint of the previous block's contents. Change even one digit in an old block, and its fingerprint changes entirely, snapping the chain. This is what makes the blockchain essentially tamper-proof.
The blockchain is most useful not when people trust each other — but precisely when they don't.
Occasionally two valid blocks are created at the same moment by different participants. The chain briefly forks — like two roads branching from one point. Very quickly, the network picks one path and abandons the other (the discarded block is called an orphan). This is why you shouldn't consider a Bitcoin transaction fully settled until several more blocks have been built on top of it — each additional block makes the transaction exponentially harder to reverse.
→ [Block B] ✗ orphaned
Blockchain shines when participants don't trust each other, span different countries, want transparent and permanent records, and have no shared authority to appeal to. It is not a magic solution — if you already trust the people you're transacting with, a simple shared database works better.
A blockchain is a shared notebook nobody owns, everyone can read, and nobody can erase — where each page is permanently locked to the one before it.
- Why does the blockchain need to be public? Couldn't a private blockchain work just as well?
- What happens if two miners create valid blocks at exactly the same time — who decides which one "wins"?
- Can you think of a use for blockchain beyond money — and would it genuinely need one, or would a regular database do the same job?
Network
Bitcoin is secure and unstoppable — but it was never designed for buying coffee. The Lightning Network was built to change that, without compromising Bitcoin's fundamental guarantees.
Every Bitcoin transaction is written permanently to the blockchain, confirmed roughly every 10 minutes, and costs a small fee. That's perfectly acceptable for large, high-value transfers. But for everyday spending, it's overkill — like sending a signed legal document every time you tip a street musician.
Think of a bar tab. You open a tab at the start of the evening. You and the barman keep an informal running tally throughout the night. You only settle the bill — and write it permanently into the records — when you leave. Lightning works exactly like this. The blockchain only sees the opening and closing of your tab. Everything in between is instant, free, and private.
A Lightning channel is opened between two parties by locking some Bitcoin into a shared arrangement on the blockchain. From that point, payments can flow between them instantly — back and forth, many thousands of times — without touching the blockchain at all. When they're done, the final balance is settled on-chain.
The real magic is the Lightning Network itself — the web of interconnected channels. You don't need a direct channel with everyone you want to pay. Lightning finds a path through the network and routes your payment through connected channels automatically, arriving at its destination in seconds.
| Bitcoin (On-Chain) | Lightning | |
|---|---|---|
| Speed | ~10 minutes | Instant |
| Fees | Higher | Near zero |
| Best For | Large payments | Small, frequent payments |
| Privacy | Publicly recorded | More private |
| Maturity | Very well tested | Still maturing |
When you download a Lightning wallet (like Phoenix or Breez), you don't need to manually lock up Bitcoin or manage channels yourself. The wallet handles all of that invisibly in the background — connecting you to existing nodes that already have channels open. You simply send and receive. Think of it like using an ATM: you don't build the banking infrastructure — you just use it.
Lightning is Bitcoin turbocharged — instant, cheap payments that run off-chain, with only the opening and closing of accounts ever touching the blockchain.
- If Lightning payments happen off the blockchain, are they actually as secure as regular Bitcoin? What could go wrong?
- Lightning routes payments through other people's channels. Does that mean those people can see what you're paying for?
- Lightning wallet apps manage channels for you invisibly. Does that make them similar to a bank? What's different?
- Could Lightning ever fully replace on-chain Bitcoin transactions — or will both always be necessary?
Picture Questions
Use these to spark a wider conversation — there are no right answers. Just honest thinking.
- Bitcoin was designed so that no single person or government controls it. Is that actually a good thing — or does it create problems?
- Bitcoin stores a hash of your public key — not the public key itself — which means a quantum computer can't reverse-engineer your private key just from the blockchain. But your public key is revealed the moment you spend Bitcoin. Does that create a window of vulnerability, however brief?
- Blockchain removes the need for trust by using technology instead. But do we want a world where we replace trust with code?
- Lightning makes Bitcoin fast and cheap. Does that make Bitcoin more like regular money — and does that matter?
- If you could redesign money from scratch today — knowing everything in this issue — what would you build?