Blockchain Basics Part 1: The Problem, The Promise, and The Pillars
The Carrot That Keeps Moving
Last month, I competed in a hackathon. I built a GenAI project — something I was genuinely proud of. Clean demo, solid use case, good presentation. And yet, when I looked around at the teams that were getting the most attention, winning the top spots, the ones that stood out had one thing in common: they'd layered Web3 or blockchain integration on top of their AI stack.
A few months before that or maybe an year ago, plain GenAI projects were the move. Before that, it was something else.
It started to feel like a carrot-and-stick situation. The goalpost keeps moving. Every time you feel like you've caught up, the industry has already pivoted. And honestly? That's both exhausting and kind of exciting. It means there's always something new to learn, always a new angle to explore.
So I made a decision: instead of chasing the carrot, I'd actually understand what I kept running past. Blockchain. Not just "add some Web3 vibes to my project" blockchain, but the real thing — what it is, why it exists, and why it keeps showing up as the answer to problems I didn't even know needed solving.
This series is my attempt to work through that understanding out loud. I'm a CS student, not a blockchain engineer (yet). So if you're also someone who's heard the word "blockchain" thrown around in every tech conversation but still isn't quite sure what it actually does — you're in exactly the right place. Let's figure this out together.
The Problem: We've Been Trusting Middlemen Our Whole Lives
To understand why blockchain exists, you first have to sit with the problem it's trying to solve.
Think about how money moves. If you want to send cash to a friend in another country — say, someone living under a government that your country has imposed monetary sanctions on — what happens? You can't. Not directly, anyway. Your bank, operating under national regulations, simply won't process the transaction. A third party you didn't invite into the conversation has complete veto power over your money.
That's not a fringe scenario. That's the current reality of international finance. And it's not just about money. Think about your Instagram account. Every photo you've posted, every connection you've built, every piece of content you've created — who owns that? Instagram does. Meta does. If they decide tomorrow to change their algorithm, shadowban your account, or just shut down the platform entirely, you have no recourse. Your data lives on their servers. Their rules.
This is the fundamental architecture of the internet as it exists today: centralized systems. One entity — a company, a government, a platform — sits at the center and controls the flow of information, money, and access. And the thing about a central point of control is that it's also a central point of failure.
If a hacker wants to compromise a centralized database, they have a clear target. They don't need to attack a thousand machines — they need to crack one. If a government wants to censor information or freeze assets, they go to the one organization that holds the keys. If the server goes down, the whole system goes down.
We've built the modern digital world on this architecture, and for a long time, it worked well enough. But "well enough" and "trustworthy" aren't the same thing. We've been trusting middlemen for so long that we forgot to ask whether we needed to.
From Reading to Writing to Owning: The Web Evolution
To really appreciate where we're headed, it helps to see how we got here.
Web1 was the internet of the early days — the read-only web. Think Wikipedia, static pages, digital encyclopedias. You could consume information, but the web was largely a one-way street. Most people were readers, not creators. It was remarkable for its time, but it was passive.
Web2 changed everything. Suddenly, you could not only read — you could write. Social media, user-generated content, platforms that let anyone publish a blog post, upload a video, build a following. The internet became interactive and participatory. This is the web most of us grew up on and still live in today.
But Web2 came with a trade-off that wasn't written in any terms and conditions in plain language: in exchange for the ability to write and participate, you handed over ownership. Your posts, your connections, your behavioral data — the platforms became the custodians of all of it. They monetized it, analyzed it, and built billion-dollar businesses on the back of content you created.
Web2 gave us freedom to post, but quietly kept the keys. Classic.
Web3 is the response to that trade-off. The idea is that you should be able to read, write, and own. Your digital assets, your data, your identity — these should be yours in a verifiable, provable way that doesn't depend on any single company deciding to honor it. Web3 is still being built, still being argued about, and very much a work in progress. But the philosophy behind it is coherent: the internet should be a place where users have sovereignty, not just access.
Blockchain is the infrastructure that makes that vision technically possible. It's not the only piece of the puzzle, but it's the foundational one.
The Four Pillars of Blockchain
Before we get into the mechanics of how blockchain actually works (that's coming in later parts of this series), it's worth establishing why it works — the properties that make it more than just a fancy database. There are four that matter most.
Security. In a centralized system, security means protecting the center. In a blockchain, there is no center. The data isn't stored in one place — it's replicated across thousands (sometimes hundreds of thousands) of machines around the world. To "hack" a blockchain in the traditional sense, you'd need to simultaneously compromise the majority of all those machines. That's not just difficult; in a sufficiently large network, it's practically impossible. There's no single point of failure, because there's no single point — period.
Immutability. Once data is written to a blockchain, it can't be quietly changed or deleted. Every piece of data is linked cryptographically to everything that came before it, and any attempt to alter a historical record would require rewriting not just that entry, but every entry that followed it — and getting the majority of the network to agree to that rewrite. This makes blockchains extraordinarily resistant to retroactive manipulation. The record is permanent. What's written is written.
Transparency. Public blockchains are exactly that — public. Anyone can look at the ledger, trace the history of a transaction, verify a claim. This doesn't mean everything is visible (there are privacy-preserving techniques), but the default is openness. Accountability is baked in rather than bolted on. In a world where institutions routinely obscure how decisions are made, that's a genuinely radical property.
Accessibility. You don't need a credit score, a passport, a bank account, or the approval of any gatekeeper to interact with a public blockchain. If you have internet access and a wallet, you're in. This is what "permissionless" means in the blockchain space — nobody can tell you that you don't qualify. The network doesn't care who you are.
These four properties aren't independent features you can mix and match. They emerge together from the architecture of how blockchains are designed. Understand the architecture, and these properties make intuitive sense. That architecture is what we'll be unpacking over the next several posts.
The Distributed Ledger: A Google Doc Nobody Owns
I want to close this first post with an analogy that genuinely made things click for me. I picked this up from Rehan Khan, a representative from the Avalanche team 1, at a hackathon — and it's the clearest framing I've come across for someone encountering this concept for the first time.
Imagine a Google Doc. Not just any Google Doc — one that's open on thousands of screens simultaneously, all around the world. Every person who has it open can see every edit that's ever been made, in real time.
Now here's the twist: nobody owns this document. There's no admin. There's no Google. There's no single server it lives on. It exists as a collective, distributed across all those open screens at once.
What happens when someone tries to sneak in a change — to quietly edit their local copy without everyone else seeing? It doesn't work. The moment they try to alter their version, the document across thousands of other screens shows the mismatch. The network recognizes the inconsistency and rejects the change. For anything to actually get written to the document, the majority of the people who have it open need to agree that the change is valid.
That's a blockchain. The "document" is the ledger — the record of every transaction, every piece of data that's been written to the chain. The "thousands of screens" are the nodes in the network — independent computers, each holding an identical copy of the ledger. The "agreement process" is consensus — the mechanism by which the network decides what's true.
No single person, company, or government can rewrite the history in this document. They'd need to control more than half of all those screens at once. And they'd need to do it faster than the network can catch on and adapt. In practice, that's a near-impossibility on a sufficiently decentralized chain.
This is what "trustless" means in the blockchain context — not that there's no trust at all, but that trust is no longer placed in a single entity. Instead, it's distributed across the network itself. The system is designed so that you don't have to trust any one participant; the math and the consensus mechanism do the work of enforcing honesty.
If you want to see this in action visually — which I'd genuinely recommend — go explore this website by Anders Brownworth. He has an interactive blockchain demo that shows you exactly how blocks link together, what happens when you try to tamper with one, and why the cryptographic chaining makes manipulation so difficult. It's one of those rare tools that turns an abstract concept into something you can actually poke at. Worth fifteen minutes of your time before we go deeper in the next post.
Where We Go From Here
We've covered a lot of ground in this first post, and I want to acknowledge — this is still mostly the "why" of blockchain, not the "how." We haven't talked about cryptographic hashing, consensus algorithms, smart contracts, or any of the technical machinery that makes this all actually work. That's intentional. The problem has to be vivid before the solution makes sense.
Here's what I want you to walk away with from Part 1:
Centralized systems are convenient, but they're fragile and they require trust in entities that may not deserve it. Web3 is an attempt to build a different kind of internet — one where ownership is real and intermediaries are optional. Blockchain is the foundational technology behind that vision, built on four core properties: security through decentralization, immutability of records, transparency of data, and accessibility without gatekeepers. And at its heart, it's a ledger — a record-keeping system that no single entity controls.
In Part 2, we're going to open up the hood. We'll look at how blockchain actually structures and stores data — blocks, chains, hashes — and start to understand the elegant bit of engineering that makes immutability not just a promise, but a mathematical guarantee.
The carrot is still moving. But now we're actually chasing it on purpose.
If you found this helpful, drop a reaction or leave a comment — I'm figuring this out in public, and knowing what lands (and what doesn't) helps me write the next one better. See you in Part 2.
