There's a version of knowing something that feels like understanding but isn't.
I had that version of Bitcoin.

For a long time, I could talk about it confidently. How it works. Why it matters. What makes it different from everything that came before. I wasn't making things up. But I also wasn't telling the full truth — because I didn't know it yet.

I was describing the car by pointing at the wheels. I had never looked inside the engine.

Seven weeks ago, I joined the Btrust Builders Mastering Bitcoin self-paced cohort. I expected to fill in a few gaps. What actually happened was different. The gaps were bigger than I thought. And the things I assumed I already knew were often the things I understood the least.

Chapter 1 Should Have Been Easy

I expected Week 1 to be review.
It wasn't.
The first thing that stopped me was double-spending. I had explained it before — Bitcoin stops you from spending the same coin twice — and moved on like it was simple. But sitting with the actual mechanics of how that works, with no central authority, with strangers across the world who don't know or trust each other somehow agreeing on one shared history — I realised I had been skipping past the most important part every single time.

By Chapter 3, I was reading about Elliptic Curve Cryptography and what it actually means that the relationship between a private key and a public key is one-way. You can go forward but never back. I had said that sentence before but I had never actually understood what it meant until I sat with the mathematics behind it.
The private key doesn't just protect your bitcoin. It generates everything — your address, your identity on the network, your ability to prove you authorized a transaction. All of it flows from one number that only you hold.

The Chapter That Embarrassed Me

Here's something that genuinely embarrassed me.
When I got to Chapter 9 — transaction fees, I discovered something I had been getting slightly wrong every time I explained it.
Bitcoin transactions have no fee field.
None. It doesn't exist in the protocol.
The fee is simply whatever is left over after you subtract your outputs from your inputs. If you send 1 bitcoin and create outputs totalling 0.9999 bitcoin, the miner takes the 0.0001 that remains. If you forget to send change back to yourself, the entire remainder goes to the miner. There is no prompt. No warning. The protocol just takes it.
I thought about how many times I had explained fees as "a small charge." That framing completely hides the truth. It's not a charge. It's a bid. Every transaction is competing with thousands of others for space in the next block. Miners pick the highest-paying ones. Your transaction is an auction entry.
I rewrote my mental model of fees from scratch that week.

Mining Is Not What I Thought It Was

This one hit harder than the rest.
I used to explain mining like this: miners solve a puzzle and new bitcoin gets created. But after Chapter 12, I can't say it that way anymore. Because that framing puts the emphasis in completely the wrong place.
Bitcoin isn't issued because miners solve puzzles. Miners solve puzzles because that's the only known way to get thousands of strangers, with no reason to trust each other, to agree on one shared version of history.
The new bitcoin is just the incentive. The real product is consensus. Agreement. A record that nobody owns but everybody can verify.
If you only understand Bitcoin as a coin that miners produce, you'll always be slightly confused about why it works the way it does. If you understand it as a system for achieving trustless agreement, everything else starts to make sense — including why changing any of its rules is so difficult and so controversial.

Security Taught Me Something About Myself

Chapter 13 — Bitcoin Security, made me uncomfortable. Not because it was complex. Because it was personal.
Bitcoin security is not like bank security. A bank is designed to protect you from your own mistakes. Bitcoin is not. Bitcoin cannot. If you lose your keys, there is no recovery. If someone steals them, the transaction confirms and the network moves on. The same property that makes Bitcoin uncensorable — that no authority can reverse a transaction — makes your errors permanent too.
The book describes a real event: a well-known Bitcoin project lost nearly 7,000 BTC in 2011. Not from a hack. From over-engineering their own backups. They encrypted everything so aggressively they locked themselves out. The protection destroyed the thing it was meant to protect.
I sat with that for a while.
Possession of the private key is ten-tenths of the law. Not nine-tenths. Ten. There is no appeals process. No customer service line. No one coming to help.
That kind of responsibility is heavy. But it's also honest. And I'd rather have an honest system than a comfortable one.

The Week Everything Clicked

Chapter 14 — second-layer applications, is where seven weeks of learning collapsed into one clear picture.
Payment channels. Two people lock funds on-chain. Then they pass signed transactions back and forth privately, as fast as they want, with nothing touching the blockchain. Only two transactions ever get mined — the opening and the closing. Everything in between is invisible to the network.
The Lightning Network connects those channels together. Now Alice can pay Eric without ever opening a direct channel with him. The payment routes through other nodes, each hop secured by Hash Time Lock Contracts. Every hop either completes or refunds. Nobody in the middle can steal the money.The system is designed so that honesty is always more profitable than cheating.

And if you try to cheat — if you broadcast an old channel state hoping to steal a few sats, the other party can use the revocation key to take everything. Not just their share. All of it.
The punishment is total. Automatic. Cryptographic.
There's a real elegance to that. The system doesn't assume you're good. It just makes dishonesty catastrophically expensive.

What Actually Changed

Before this cohort, I could talk about Bitcoin.
After it, I think in Bitcoin.
There's a real difference between those two things. Talking is surface movement. Thinking means the mental model is underneath everything, quietly organizing how you see new information. When I come across a new Bitcoin product or proposal now, I automatically ask: what primitives does it use? Where does trust live? What happens if one party disappears or tries to cheat?
I also know more precisely where my understanding ends. Week 1 I asked: will Bitcoin ever replace fiat? Looking back, that was a spectator's question. The questions I'm asking now are builder's questions. Better questions are the real sign of learning. Not better answers.

WHAT'S NEXT

I'm building BitcoinLasgidi — a Bitcoin-focused community on my campus in Lagos. We educate developers, designers, builders, and enthusiasts about Bitcoin. Everything I learned in these seven weeks goes directly back into that work. The way I explain keys, fees, mining, Lightning, none of it will sound the same as it did before.

Now I know how much there is still to learn, and how much more there is to build.
That's the best possible outcome.

Let Bitcoin Lead. 🧡