The trust is in the client
Moxie Marlinspike’s first impressions of web3 found that the decentralized apps people use run through a few companies’ servers. People trust what the screen tells them, so that’s where the trust in a system actually lives.
Moxie Marlinspike, who created Signal, published his first impressions of web3 on January 7. He built a couple of small apps to see how it worked in practice, and the post has been passed around ever since.
His central finding is about people. “Even nerds do not want to run their own servers at this point,” he writes. So the apps people use to reach a blockchain don’t talk to it directly. They go through a handful of API companies, and the clients mostly don’t verify what those APIs send back.
He has a sharp example. He made an NFT whose image changed depending on who was looking at it. When OpenSea removed it, it also vanished from his wallet, because the wallet was showing him what OpenSea’s API said he owned.
Where trust actually lives
That example is a design lesson more than a blockchain one. People trust what their screen tells them, so the trust in any system lives in the client, wherever the data is kept.
A ledger can be permanent and public, but almost nobody reads a ledger. They read an app. If the app shows them whatever a server returns, the guarantee underneath doesn’t reach them. The interface is the only part of the system most people ever check, and in web3 right now it’s one of the most centralized parts.
Show the real state
I’ve spent a lot of my career designing tools for people inside a live system. At Uber, the engineers using Studio to test the marketplace needed a tool that showed the real state of a trip, because a tool that looked right and was wrong would send them chasing the wrong bug. The rule I took from that work is that a tool’s first job is to never lie about state.
For anything people are asked to trust, that rule becomes a question for every screen: where did this come from, and would the screen tell me if the source changed its answer? Most products don’t need to answer those out loud. A product whose pitch is that you don’t have to trust anyone does.
The honest version
Decentralization may still be a good idea. The work just doesn’t end where the protocol does. Until the apps people actually use can check what they’re told, the promise belongs to the ledger, and users experience whatever the API says.