[ 04 / 10 ] · Freshman Track

Lesson 04: Why Build Decentralized?

4 minutes100 XP

Embark on your journey to building production grade apps.

Remember Lesson 3? You learned everything that goes into making an app production-ready. A database. Auth. File storage. Payments. Email. Error tracking.

Every item on that list is a separate service you don't own. Every one can break, get hacked, freeze your account, or disappear overnight.

Underneath all of it is one fact: you have to trust someone.

You trust Supabase to keep your database online. You trust Stripe not to freeze your funds. You trust AWS not to go down. You trust the platform not to change its terms and lock you out tomorrow morning.

This isn't hypothetical. Social platforms have banned users overnight after a single policy call. Payment processors have cut off merchants under public pressure. Apps that millions of people relied on have been pulled from app stores. The pattern is always the same: someone built on infrastructure they didn't own, and someone else decided to pull the plug.


A different way to build

What if trust wasn't a dependency?

That's what decentralized apps are for. There's no company in the middle that can decide, one Tuesday, that you're off the platform. There's no server a government can seize. The app runs on a network of computers that no one owns and no one can shut down.

You've used decentralized tech before. BitTorrent works this way. No company runs it, no one can turn it off. But BitTorrent only shares files. For apps that handle money, run logic, or store real state, you need the specific kind of decentralized network this course is about.

What's the core difference between a traditional app and a decentralized app?


Why it matters

A lot of what gets built on blockchains is speculative. Tokens with no real use, short-term trading, games built around price action. That part of the space gets most of the attention, and the criticism is fair.

But that's where the technology is right now, not what it can do.

The thing blockchains do that nothing else does: they let you build something that can't be shut down by a single company or platform. No registrar can pull your domain. No exchange can freeze your funds. No payment processor can decide your business isn't allowed anymore.

Stablecoins let freelancers in countries with slow or expensive banks get paid in dollars in minutes. A payment that used to take three days and cost $30 now costs cents.

ENS lets you actually own your domain name. You're not renting it from a registrar that can take it back.

Uniswap lets anyone swap tokens without opening an account or asking anyone for permission.

That's the part of the space worth building in.


What hasn't been built yet

Here's the part worth sitting with: the mainstream decentralized app that people use for something other than speculation or finance doesn't exist yet.

Billions of dollars have been raised. Hundreds of teams are trying. Most are still building casinos.

Meanwhile, the real problems are sitting there waiting:

  • Anti-censorship tools
  • Verifiable identity and voting
  • Data privacy that users actually own
  • AI-content detection that can't be faked
  • Governance systems that can't be captured
  • Ownership that no platform can revoke

Every one of these is a billion-dollar problem. None of them have been solved well. The reason isn't that the technology can't do it. The reason is that most of the people building the technology aren't thinking about users.


Why you

You know how to think about users. You know what makes an app actually good. You're now learning the technology that lets you build things no platform can take away.

That combination is rare here. Most people in this space have one side or the other.

The decentralized app people actually use hasn't been built yet. It might be yours.


Next up

You understand why to build decentralized. Next lesson: the specific network we'll build on.

0/1 correct

0% — get all correct to complete

Sign Up to Track Progress