I entered blockchain through the door of easy gains. I stayed because I found a philosophy of systems, trust, and human possibility.
I. Before Understanding, There Was Curiosity
My story with blockchain did not begin with vision.
It began like many others.
Around 2016, I entered the space through cryptocurrencies, mining experiments, Telegram bots, mobile applications promising shared revenue, and the idea that maybe, just maybe, technology had opened a shortcut to easy money.
I won some.
I lost some.
And like many beginners, I was first attracted by the visible surface of the ecosystem: coins, rewards, speculation, mining, hype.
At that stage, blockchain was not yet an architecture to me.
It was an opportunity.
But opportunities are often doors.
And sometimes, behind the wrong door, you find the right question.
The question that changed everything was simple:
What is really happening underneath?
Not the price.
Not the promise.
Not the noise.
The system.
That was the beginning of the real journey.
II. The Book That Almost Defeated Me
At some point, curiosity became stronger than speculation.
I wanted to understand what blockchain actually was, why Bitcoin mattered, and why people spoke about it as if it had changed something fundamental in the history of digital systems.
That search led me to Mastering Bitcoin: Unlocking Digital Cryptocurrencies by Andreas M. Antonopoulos.
And honestly, it was hard.
Not “hard” in the romantic sense.
Hard in the frustrating, humbling, almost discouraging sense.
Every page opened another door I was not ready for:
cryptography, hashing, public and private keys, peer-to-peer networks, consensus, transactions, blocks, mining, wallets, signatures.
I was not just reading a book.
I was being forced to learn an entire world in parallel.
Several times, I wanted to stop.
Several times, I felt like maybe this was too much.
But there was something else: a fire. A stubborn need to pierce the mystery.
I kept reading.
I watched videos.
I followed tutorials.
I rebuilt concepts in my mind.
And more importantly, I started questioning the dominant narrative.
Is blockchain only about cryptocurrency?
That question became the real engine.
Because once you stop seeing blockchain as money, you begin to see it as a way to rethink trust.
III. My First Blockchain: Speed, Failure, and the First Light
Between late 2016 and early 2017, I coded my first blockchain by following a tutorial.
It was not perfect.
It was not revolutionary.
It was not even close to production-ready.
But it worked.
And that changed something in me.
The first time you build even a simple blockchain, something shifts.
You stop seeing the concept as mystical.
You begin to understand that behind the myth, there is structure.
Blocks.
Hashes.
Links.
Validation.
State.
Rules.
I failed several times during that first attempt because I wanted to go too fast.
I was rushing toward results before fully understanding the logic.
But eventually, there was light at the end of the tunnel.
And with that light came ambition.
I started thinking:
If Satoshi could design something like this, and if others after him could build on it, then why not me?
Not in arrogance.
In possibility.
That was the moment blockchain stopped being something I consumed.
It became something I wanted to build with.
IV. Swiftchain: The Project That Taught Me Humility
My second major attempt was a project I called Swiftchain.
The idea was to build an EDI system based on blockchain.
It was ambitious. Maybe too ambitious for where I was at the time.
But ambition has a way of teaching what comfort never will.
Swiftchain became one of my most painful and formative experiences.
Fun fact: I had to restart the project three times.
The first time, I lost critical work because of a bad command-line file manipulation.
That was the day I learned, very personally, that backups are not optional wisdom.
The second time, a system crash corrupted the disk partition where the project was stored.
I tried recovery tools. Nothing meaningful came back.
The third time, I realized something even more painful:
my original design approach was wrong.
Not the code.
The approach.
That kind of failure hurts differently.
When code fails, you debug.
When architecture fails, you rethink yourself.
It took around seven months of work, frustration, rebuilding, and questioning before I reached something close to sustainable.
Swiftchain taught me that blockchain development is not about adding blocks to a chain.
It is about designing trust, flow, identity, validation, and failure conditions.
It taught me patience.
It taught me humility.
It taught me that systems punish unclear thinking.
V. From Blockchain to IPFS: The Archive Problem
After Swiftchain, I moved toward another experiment: a digital archiving system based on blockchain and IPFS.
This was important because it moved me further away from the cryptocurrency narrative.
I was no longer asking:
How can blockchain create value as a financial asset?
I was asking:
How can blockchain preserve integrity, traceability, and confidence in digital records?
That question opened a broader design space.
Archiving is not just about storage.
It is about memory.
Proof.
Authenticity.
Continuity.
IPFS brought another dimension: distributed storage, content addressing, and the idea that files could be referenced by what they are, not where they are.
This changed how I thought about digital systems.
A system should not only process information.
It should protect meaning.
VI. The Human Direction Behind the Technology
As more projects came to life, my intensity changed.
Life brought other realities, other responsibilities, other priorities.
I could not always build with the same obsession as before.
But the direction remained clear.
I wanted to design systems that were:
- human-centered,
- partially autonomous where useful,
- trustworthy by design,
- able to reduce friction in people’s lives,
- and capable of interacting with existing realities rather than ignoring them.
This last point became crucial.
Around 2020-2021, but even before, I hit one of the biggest walls in my blockchain journey:
interoperability with existing systems.
It is easy to imagine elegant decentralized systems in isolation.
It is much harder to make them communicate with legacy infrastructure, administrative systems, databases, identity providers, public institutions, and human workflows.
Yes, oracles can help connect blockchain systems to external data.
But then comes a deeper problem:
digital identity.
Who is acting?
Who is authorized?
Who can be trusted?
What does identity mean in a distributed system?
How do you bridge blockchain logic with institutional legitimacy?
That wall changed the scale of my thinking.
Blockchain was no longer just a technical domain.
It had become a governance problem, a public infrastructure problem, a social trust problem.
VII. The State Digital Identity Project
Between late 2019 and 2022, I entered what I can only describe as one of the most ambitious intellectual challenges I had ever taken on.
With limited resources, I started thinking through the foundations of a state-level digital identity system and the ecosystem around it.
Looking back, it was a crazy project.
Not because the idea was impossible, but because the scope was enormous.
To approach it seriously, I had to learn and connect multiple worlds:
- blockchain,
- PKI,
- distributed systems,
- digital identity,
- public administration,
- trust frameworks,
- governance models,
- interoperability,
- and institutional workflows.
There were months of questioning.
Months of learning.
Months of iteration.
Eventually, I reached a working use case:
birth certificate issuance by declaration.
That was a major milestone.
But even then, I knew I had not reached 30 percent of the full objective.
And that realization mattered.
Because when you work on systems connected to identity, government, citizenship, and trust, you quickly understand that technical success is not enough.
The code can work.
The prototype can run.
The architecture can be elegant.
But the real question is larger:
Can the system be trusted, adopted, governed, and sustained?
That project changed me.
It forced me to understand blockchain not only as infrastructure, but as institutional philosophy.
VIII. Teaching Blockchain: The Journey Becomes a Mirror
At the end of 2022, a new opportunity appeared: teaching blockchain and supervising or co-supervising master’s-level research.
That changed the journey again.
Teaching forces you to clarify what you think you understand.
Students ask questions that expose the weak spots in your reasoning.
Research topics push you into domains you might not have explored alone.
In many ways, teaching became a mirror.
It challenged me continuously.
It forced me to stay updated.
It kept the fire alive even when life pulled my attention elsewhere.
And through students, blockchain became more than my personal journey.
It became a shared adventure.
Some students explored health systems.
Others explored agriculture, identity, land, supply chain, certification, interoperability, and governance.
Each project expanded the field of possibility.
Each discussion reminded me that blockchain is not only a technology to explain.
It is a lens through which people learn to question trust, ownership, coordination, and accountability.
IX. From Experiments to Business Cases
By 2026, I can no longer count the number of blockchain and DLT business cases I have worked on, co-developed, discussed, or helped structure.
They span multiple sectors:
Health
Electronic medical records, interoperability, pharmaceutical supply chain, data integrity, consent, patient identity.
Agriculture
IoT and AI for production optimization, soil-less cultivation, food traceability, trusted records across value chains.
Digital Identity
Self-sovereign identity, GovTech, digital public services, institutional trust frameworks.
Land and Real Assets
Digital assets, tokenization, land registry logic, ownership traceability.
Supply Chain
Traceability, verification, audit trails, multi-party coordination.
And alongside the projects came certifications and structured learning paths:
CBE, CBA, CBSP, Certified DAO Expert, and more.
But the more I learned, the more I understood how much remains to learn.
That is the paradox of deep knowledge:
it does not make the world smaller.
It makes the unknown more visible.
X. What Blockchain Really Taught Me
Today, blockchain is no longer just a topic I study, teach, or build around.
It has shaped the way I think.
It taught me that trust is not abstract.
It can be designed, attacked, distributed, verified, weakened, strengthened.
It taught me that systems are never neutral.
They encode assumptions, incentives, governance, and power.
It taught me that decentralization is not automatically good.
It is costly, difficult, political, and often misunderstood.
It taught me that technology without human context becomes ideology.
And ideology without architecture becomes noise.
Most importantly, it taught me patience.
Because every meaningful system requires time:
time to understand,
time to fail,
time to rebuild,
time to question the original question.
Blockchain gave me more than technical skills.
It gave me a way to see the world.
XI. Why This Became a Philosophy of Life
Looking back, I did not stay in blockchain because of cryptocurrencies.
That was only the entry point.
I stayed because blockchain forced me to confront deeper questions:
- What is trust?
- Who owns truth?
- How do systems coordinate without central authority?
- What makes a record legitimate?
- How can humans design systems that are both autonomous and accountable?
- How do we build technology that serves people instead of replacing meaning?
These questions do not belong only to blockchain.
They belong to life.
In a way, choosing blockchain became choosing a philosophy:
a philosophy of curiosity, resilience, verification, and responsibility.
It taught me not to accept systems at face value.
It taught me to ask what lies beneath.
And maybe that is why this journey still matters to me.
Because blockchain, at its best, is not about escaping institutions, chasing tokens, or worshipping decentralization.
It is about one of the oldest human problems:
How do we create trust where trust cannot simply be assumed?
That question changed my career.
Then it changed my thinking.
And eventually, it became part of who I am.
XII. Closing Thought
I started with blockchain chasing opportunity.
I stayed because I found a discipline.
I failed, rebuilt, questioned, taught, designed, and kept learning because somewhere along the way, blockchain stopped being a technology I was studying.
It became a language.
A language for thinking about trust.
A language for designing systems.
A language for understanding how humans coordinate around truth.
And that is why, for me, blockchain is no longer just a field.
It is a way of life.