Essays

Blockchain that benefit everyone. Five reasons current blockchain can't be web3

If you are also thinking blockchain has a potential but just like me, deeply dissatisfied with what it became, this series will give you new perspectives and arguments on how you can achieve web3.

6 min read By Medet Ahmetson

I was working on game development tools on blockchain, researching everything. Then GitHub released Copilot. I looked at it and thought: with AI, computers can own their own software. Blockchain could play a role in that.

I left my company to build a generic framework, away from blockchain games. I was tired of blockchain and did not want to go back to it. One day I asked myself: what makes this different from every other framework out there? Why would anyone use mine? I stopped. Did not touch a computer for a week.

Then the eureka came. The answer led me back to Ara, a dream I had been carrying since I first began using computers. Users owning their software. Malleable systems. The framework was the path to that dream, and blockchain was one of Ara’s components. So I returned to blockchain. This time I knew how to find its real use case.

Five reasons why blockchain is not web3

I don’t mean payment blockchains as Bitcoin because they never advocate the web3 future. Here, blockchain refers to apps or platforms pushing the web3 vision using this technology.

1. The wrong question

First, we need to shift our thinking model regarding computers. With the rise of the web we look at the technology from a data perspective. Since 2015, the data paradigm has reached its peak as a privacy matter, and the data ownership paradigm is the most used frame for solutions. Instead, let’s think of computers as software executions.

The core thesis of web3 is data ownership, due to data pov. We don’t hear about software ownership. Have you ever heard about it? I haven’t yet. After all, we stopped owning them, we rented them. Once software ownership is solved, data ownership resolves automatically.

In a follow-up essay, I will expand this data pov versus software pov. But for now, when you hear about computers, I ask you to think about the software as a computer’s core artifact. As we keep ignoring it, while we treat computers and the Internet as Information Technology, we won’t have the next big revolution ever.

That data perspective is exactly why blockchain got defined as a public database. But that is not what it is.

Think of it this way. Every time you run the same program with the same input, you get the same output. Nobody can secretly change what it does. Nobody can shut it down as long as the internet is alive. That is what blockchain actually is from a software perspective. Not a database. A program that runs the same way forever, for everyone, without a gatekeeper.

Once we have the software pov, which applies to software ownership problems, and to the definition of blockchain technology, the next two I need to talk about are fundamental flaws of the blockchain. Both stem from simply copying Bitcoin. Those who state blockchain as the evolution of the web, simply never addressed these two flaws in their design. So we don’t have wide adoption, and never will.

First is the missing hyperlinks. Hyperlink allows users to browse across machines forming a world wide web.

How can you talk about blockchain as web3, when it just lacks its fundamental component? Blockchain is not even compatible with the web, let alone as its proposed future.

3. Builders get nothing

Second is not splitting its application logic from the security. In Bitcoin, cryptocurrency plays a dual role. It’s the application and the security mechanism. Computers compete in mining and this economic incentive is what makes Bitcoin run without central authority while keeping it secure. Web3 platforms took this design unchanged.

I tried to make a web3 app. Blockchain covers maybe 10% of what a real application needs. Everything else, storage, external data, discovery, is a separate network, a separate token, a separate decentralized network to keep nodes happy. No one cares about developers.

  • Writing code for a single computer is the easiest form of software development.
  • Writing a distributed application is always harder.
  • Writing a distributed application on a p2p network is even harder. No wonder it couldn’t get momentum, except for piracy (torrent) and scam (blockchain).
  • Writing software across multiple p2p networks is impossible.

Developers take the biggest risk in this ecosystem. All they get in return is access to the platform. Meanwhile the economic model is internal, pushing everything toward transaction volume and token price growth. Developers are not part of that equation.

I lived this. Hackathons where prizes went to whatever could be hyped fastest. The day I was deploying a smart contract, watching the token price skyrocket in another tab, thinking: how is this worth that much when just getting something running is this painful.

The last two reasons are the lessons from the rise of tech giants. If blockchain wants to be widely adopted, then it has to take the lessons from them as well.

4. Nobody incentivized user experience

Besides software, and data, the interface is also important. I do not like things that become iconic just by becoming popular. Steve Jobs is one of those figures I had to sit with honestly. What I landed on: his credit in computer science history is specifically this. He proved how something feels to use matters as much as what it does. Blockchain platforms never learned that lesson. They left interface entirely to developers, and every developer solved it separately with no standards and no support.

5. Nothing is findable

The last reason is that blockchain, despite being a platform, lacks a built-in discovery mechanism. Today, when every app tries to turn into an ecosystem with the integrated marketplaces, when the OS comes with the app stores, and programming languages with the package managers, blockchain has no discovery mechanism. It’s a world computer designed as if no internet exists at all.

Ara’s initial idea had two parts: semantic storage, and communication between developers and users. Both were pointing toward a social network. I hated that frame myself. It was not what I wanted.

So I cut off everyone who understood it that way. Sat alone again and revisited everything from scratch. One question kept coming back: why had I never developed the discovery mechanism further? There are apps that track user behavior by snapshot. But with app semantics it is faster and more precise. The answer came. It was never a social network to communicate, it was a recommendation engine.

Summary

Why did blockchain, despite having a potential, not move on beyond 2015?

Five things broken from the start. Wrong thinking model. No links. No incentives for builders. No design. No discovery.

The whitepaper on https://ara.foundation/ara.pdf has details and solutions. None of it requires throwing current blockchains away by inventing replacements.

Or follow Ara project on to get updates about new essays.