Web2 vs Web3
Comparing the identity, data, and control differences between the experience centralised platforms provide and a model where the user directly controls assets and identity.
Web2 is the internet where a platform (a social network or an exchange, say) holds your account, your data, and your content. Web3 is a model where identity and assets are tied to a key you control rather than to a platform. The difference is less about technology and more about the question of who holds control.
Why it matters
This distinction answers questions like “why can nobody help me when I lose my wallet?” or “why did this app let me in without an email?” Knowing where control sits also shows who carries which risk.
Compare Web2 and Web3 across three axes
| Web2 | Web3 | |
|---|---|---|
| Identity | Platform account (email/password) | Wallet address and key |
| Data | On the platform’s servers | On-chain or with the user |
| Control | Platform sets the rules | Code and key holder decide |
| Recovery | Password reset is possible | No recovery if the key is lost |
Identity, data, and control move together
In Web3, when you connect to an app with your wallet, you are the one carrying the account. That gives independence from the platform, but most safety nets — password resets, customer support, “cancel this transaction” — disappear.
A practical comparison
You log into an exchange with an email and password; your assets sit on the exchange’s ledger.
You connect your wallet to an app; your assets stay at your address, and the app only requests access.
In Web2 you reset a password; in Web3, lose the key and there is usually no way back.
Web3 does not fix everything: the user experience is hard, key management is risky, scaling and fraud are serious problems, and many “decentralised” apps actually rely on centralised pieces. That is a good reason to treat grand promises with scepticism.
A common mistake is assuming Web3 is automatically “safer.” In fact most of the responsibility shifts from the platform to you, which demands more care and better key hygiene.
Connecting a wallet to an app can mean granting it specific permissions. Do not approve without understanding what you grant, and review unnecessary approvals regularly.
Now that you see control sits in the key, learning to store that key safely is the next step. Move on to wallets, private keys, seed phrases, and custody.