If you were forwarded this newsletter, and you'd like to receive it in the future, subscribe here.​

​Spot the Difference​

What is the difference between web2 & web3, really? Yes, there are tokens and initial coin offerings and drops and discords. But, today, they resemble each other quite a bit.

Here’s my mental model:

Imagine a startup that sells sports cards. A web2 architecture for this app would have five parts

1. A transaction database: user 1 sold card ABC to user 3.
2. A metadata database: user 1’s first name is Samuel and his profile picture is found at this URL.
3. File storage: the profile picture file is saved here.
4. App server: the code that runs the application.
5. IaaS/CDN (Infrastructure as a Service / Content Delivery Network): the servers that run code.

Compare this image to a web3 architecture with the web3 parts in red.

Only the transaction database & the file storage changed color.

We swapped the transaction database from PostGres to a blockchain like Ethereum or Sui, and the file storage from AWS S3 to a decentralized storage provider, perhaps Filecoin or ArWeave.

The rest of the application remains Web2, running on Amazon, Google or Microsoft servers. Many developers build web3 applications this way: games, exchanges, cross-chain bridges.

The remaining parts of the stack haven’t been recast as decentralized services, yet. Perhaps they will be.

For now, the transaction database remains the most critical decentralized component. That’s enough to confer the benefits of decentralization to users, while giving engineers the tools to build a functional app.

​