Not All Blockchains Are The Same. And Choosing The Wrong One Could Kill Your Entire Solution.

Since 2022, when I first encountered Blockchain Technology, I was doing something I didn’t even realize.

Anytime someone said “blockchain,” I had one picture in my head. Ethereum. Bitcoin. Decentralized. Open. Public. That was blockchain to me, and everything else was just a variation of the same thing.

Then I started studying platform architecture properly, Bitcoin, Ethereum, Hyperledger Fabric, Corda, and something then hit me that I genuinely wasn’t expecting.

“These are not the same thing with different names. They were built for completely different reasons”.

Same technology. Completely different purposes. Choosing between them is an architectural decision, not a preference.

With something like Ethereum, the whole point is openness. Anyone can participate. Transactions are visible on the network. The people involved don’t necessarily know or trust each other, and that’s fine, because the network itself creates the trust.

But with Hyperledger Fabric? It’s built for businesses that already know who they’re dealing with. There are organizations, permissions, defined roles, and the blockchain is being used as a way for those known parties to share and agree on records they can all trust. Nobody random is joining this network.

Corda goes even further. It doesn’t broadcast information to everyone on the network. It shares data only between the parties who actually need to see it. Which, if you think about it, is how most business relationships actually work, right?

Public blockchain says: “We don’t trust each other, so the network creates the trust.” Enterprise blockchain says: “We know each other, but we need a better way to agree on the same records.”

That difference completely changed how I think about designing solutions.

Now, let me show you what I mean with a quite relatable example. To Nigerians sha… But I still believe our diaspora friends will understand

Get Bullish_Dave’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Land registration. One of the most painful, most disputed, most manipulated systems in the country. Records get lost. Ownership gets disputed. Documents get forged. Different offices hold different versions of the same information.

Now, if someone came to me tomorrow and said, “Build us a blockchain solution for land registration in Nigeria,” the worst thing I could do would be to immediately start picking a platform. That would be starting too late in the process.

The first question isn’t “which blockchain.” It’s “what is actually broken, and does blockchain even fix it?”

How I would actually think through it is as follows;
1. Understand the problem — where exactly do records get lost, disputed or manipulated?
2. Map the people involved — government, land registry, surveyors, lawyers, banks, landowners
3. Ask: Does this need blockchain, or just a better database?
4. If blockchain — public or permissioned? Land records involve known government organizations. Permissioned makes sense.
5. Which platform fits? Hyperledger Fabric — organizations, permissions, private data. Fits the structure.
6. Design the architecture — who can read what, who can write what, how ownership transfer works
7. Build the application — because a citizen shouldn’t need to understand blockchain to verify land ownership

This last point matters more than people just think. The blockchain is not the product. The application built on top of it is. A landowner in Abuja shouldn’t have to know what Hyperledger Fabric is. They should just open something, search a plot number, and see who owns it, verified, tamper-proof, and trusted. That's it!

That’s the architect’s job. Not just choosing the technology. Designing the whole system around the actual human problem.

The blockchain is the foundation. The application is what people actually use. An architect has to design both.

What this section of my studies made me realize is that the most important skill in blockchain architecture isn’t just knowing the technology. It’s knowing which technology fits which problem, and being honest enough to say when none of them do, and this is very important.

Any architect who leads with “let’s use blockchain” before understanding the problem is not designing a solution. They’re looking for a problem to fit their answer. And in a country with real, urgent infrastructure challenges, that’s clearly a luxury we can’t afford.

Coming next: We’ve talked about choosing the right blockchain, Next. How do you actually design the architecture itself? Three different views every architect needs, and why looking at a system from only one angle will always leave you blind to something important.

One question before you leave (as always): if you could put one broken Nigerian system on the right blockchain tomorrow, which would you pick, and which type of blockchain would you use? Drop it in the comments. I want to see how people are thinking about this.

David Umoren is an aspiring blockchain solutions analyst and content developer at Convexity. He teaches Web3 basics at Chaindustry Academy and writes about enterprise blockchain in plain language. His undergraduate thesis explored blockchain applications in the Nigerian construction industry.

Follow: Twitter/X @DavidUmoren6 · LinkedIn: David Umoren