Before we started the first session of BinnaDevLab Cohorts, I knew one thing with certainty:
If we opened with the word "blockchain," we'd lose half of the room.
Not because the topic is hard. Because the word carries baggage. Crypto speculation. NFT mania. Headlines about scams and volatility. By the time most developers hear "blockchain," they've already formed an opinion and it's usually dismissive.
So we didn't start there.
We started with a question.
"Think of an app you used this morning. Name it."
That was the warm-up exercise Uchenna Ofoma, our facilitator for Session 1 put to the cohort.
The answers came quickly.
Opay. WhatsApp. Gmail. Facebook. Sporty.
Uchenna nodded at each one. Then he asked the follow-up question. The one that changed everything:
"Who were you actually trusting?"
The room went quiet.
Not the app. Not the company. When you send ₦5,000 on Opay, you're trusting:
- Opay's servers to record the transaction accurately
- The commercial bank Opay connects to
- NIBSS to clear the interbank transfer
- The KYC provider that verified both account holders
- The CBN regulatory framework sitting beneath all of it
You weren't trusting one party. You were trusting a chain and you had zero visibility into any link of it.
That's not a crypto problem. That's not a web3 problem. That's a software engineering problem that exists in every application you've ever built or used.
And that is the real reason blockchain was invented.
Why We Built BinnaDevLab Around This
When I started BinnaDevLab Cohorts, the goal was simple but specific: train developers to reason at a global level not just to write code, but to understand why systems are designed the way they are.
The industry is full of bootcamps that teach you to ship fast. We wanted to build something different. A program built on the principle that reasoning comes before coding. That understanding the problem deeply is the actual skill, the code is just the output.
Blockchain was the perfect first topic. Not because it's trendy. Because it sits at the intersection of distributed systems, game theory, cryptography, and trust and most introductions to it skip all of that in favour of price charts.
We wanted to go the other way.
What Actually Happens When Trust Breaks
🎬 Prefer to watch? The full 64-minute session is on YouTube
Blockchain Fundamentals Explained | BinnaDevLab Cohort 1, Session 1
Uchenna spent the core of Session 1 on a deceptively simple question: where does the trust network fail?
The answer: single points of failure.
Every link in that chain we described: Opay, the bank, NIBSS, the KYC provider is a centralised entity. That means:
- One server goes down -> transactions fail
- One database is compromised -> your data is leaked
- One regulatory decision -> your account is frozen without warning
- One bad actor inside the organisation -> the records are altered
You have no way to verify what's happening. You're trusting the institution to be honest, competent, and well-intentioned. Usually they are. But the system requires you to trust them, you have no alternative.
Blockchain's argument is not that institutions are corrupt. It's that you shouldn't have to assume they're honest. The system should be designed so that anyone can verify the truth not just the people running the servers.
In practice, that means:
- Instead of rules locked on a private server -> rules deployed as code, in public
- Instead of promises -> anyone can read the code and check exactly what it does
- Instead of one keeper -> everyone keeps a copy, and no single party can rewrite history
That's not magic. That's engineering. And it comes with real costs.
The Honest Trade-offs (Most Courses Skip This Part)
One of the things I'm proudest of in how Uchenna ran Session 1 is that he didn't sell blockchain. He explained it including the parts that hurt.
Distributed verification is slower than a centralised server. Always. If you need instant transaction finality, a blockchain is the wrong tool.
It's more expensive to run. Every node in the network has to process every transaction. That cost is real and it compounds at scale.
Finality works differently. On your bank app, if you send money to the wrong person, you call customer service. On a public blockchain, the transaction is final. There is no customer service. The code runs.
And perhaps the sharpest point: blockchain doesn't remove trust. It relocates it. You stop trusting institutions and start trusting code, mathematics, and the incentive structures of a decentralised network. That's a different kind of trust, more auditable, more transparent, but trust nonetheless.
Understanding those trade-offs is what separates engineers who can reason about distributed systems from developers who just know how to call a Web3 library.
Watch the Full Session
Everything I've described above is the skeleton of a 64-minute live session with audience interaction, Q&A, and a cohort working through these ideas in real time.
Uchenna also covered:
- A brief history of blockchain (Bitcoin 2008 -> Ethereum 2015 -> today)
- Public vs. private blockchains and why each exists
- What Ethereum and the EVM actually are
- What people are building on Ethereum right now
- Consensus mechanisms: Proof-of-Work, Proof-of-Stake, Proof-of-History
- A live Q&A: does blockchain make systems trustless, or does it just shift the trust?
If this article gave you the argument, the video gives you the full picture including the moments where the cohort pushed back and Uchenna had to defend his reasoning in real time.
That's the kind of session we wanted to build. Not a lecture. A thinking session.
Watch here 👉 Blockchain Fundamentals Explained | BinnaDevLab Cohort 1, Session 1
What's Next
Session 2 is hands-on. Obinna takes the cohort from theory into code writing and deploying a smart contract in Solidity, live.
If Session 1 answers why blockchain exists, Session 2 answers how you build on it.
Follow BinnaDevLab to catch it when it drops.
About BinnaDevLab
BinnaDevLab is a developer training community built around one idea: reason before you code.
We run structured cohorts for developers who want to build with depth not just ship fast.
Top comments (0)