Contents
What McKinsey means by Web3
| Idea | Plain meaning |
|---|---|
| Decentralization | Some data, assets, or rules are maintained by a network instead of one company database. |
| Blockchain | A shared ledger that records transactions and updates across network participants. |
| Smart contracts | Code that executes rules when defined conditions are met. |
| Digital assets | Tokens, stablecoins, NFTs, or tokenized real-world assets. |
| User control | Users may hold assets or credentials in wallets, but this also creates responsibility and risk. |
Web1, Web2, and Web3
| Phase | Main behavior | Main tradeoff |
|---|---|---|
| Web1 | People mostly read and publish across open protocols. | Open, but less interactive and less productized. |
| Web2 | People create, share, buy, and communicate through platforms. | Convenient, but platform control and data concentration increase. |
| Web3 | People can interact with blockchain-based assets, wallets, and smart contracts. | More ownership and verification potential, but worse UX and higher user risk. |
Core Web3 building blocks
| Building block | What it does | Design implication |
|---|---|---|
| Wallet | Stores keys, connects identity, and signs actions. | Users need clear connection, permission, signing, and recovery states. |
| Smart contract | Executes rules on-chain. | The interface must explain what the action will do before the signature. |
| Token | Represents value, access, governance, ownership, or status. | Users need plain meaning, not only ticker symbols and contract addresses. |
| Stablecoin | A token designed to track another asset such as a currency. | Trust depends on issuer clarity, reserves, chain support, and regulation. |
| Account abstraction | Lets smart wallets support better recovery, gas handling, and bundled actions. | Good UX can hide some blockchain friction without hiding risk. |
What changed by 2026
| Signal | What it means for product teams |
|---|---|
| Crypto adoption is still real. | Do not assume Web3 is dead because one hype cycle ended. |
| Scams and wallet compromise are major risks. | Security communication and transaction clarity are product requirements. |
| Regulation is more active. | Compliance and user protection cannot be added after launch. |
| Account abstraction improves wallet UX. | Better onboarding is possible, but users still need clear consequences. |
| Enterprise use cases are narrower. | Traceability, settlement, tokenization, and identity need stronger proof than “decentralized” language. |
Why Web3 UX still matters
| UX rule | Why it matters |
|---|---|
| Show what will happen before signing. | A signature can move assets, grant permissions, or trigger contract logic. |
| Separate connection from transaction approval. | Connecting a wallet should not feel like approving a financial action. |
| Translate chain language. | Users need action meaning before they need protocol detail. |
| Design failure states. | Pending, failed, dropped, reverted, wrong-chain, and insufficient-gas states are normal. |
| Make risk visible. | Trust cues, permissions, contract identity, and recovery options should be explicit. |
