Web5 is Jack Dorsey's framing — announced via TBD, his Bitcoin-focused company — for an internet architecture that goes beyond Web3's blockchain focus to center everything on decentralized identity and personal data sovereignty. Whether you find Web5 a meaningful evolution or marketing nomenclature, the underlying technical vision raises important questions about who controls digital identity and whether blockchain-based identity is the right architecture.
The Web3 Critique Web5 Addresses
Web3 promised decentralization but delivered a mixed result: decentralized blockchains settling through increasingly centralized infrastructure (Infura, Alchemy for Ethereum RPC; AWS hosting most "decentralized" applications). More fundamentally, Web3 identity is tied to wallet addresses — which are not human-meaningful, are permanently lost if seed phrases are lost, and don't accumulate reputation across applications in a coherent way. Web5's critique is that putting identity on a smart contract platform (as ENS does) still makes identity dependent on the health of a specific blockchain.
Decentralized Identifiers (DIDs)
The W3C's DID specification, central to Web5, defines a self-sovereign identity system where you control a cryptographic identifier without relying on any specific blockchain. A DID is a URI that resolves to a DID Document — containing public keys, service endpoints, and verification methods — stored via decentralized storage systems like IPFS or on Bitcoin using Ordinals. The key property: a DID isn't owned by Ethereum, Solana, or any chain — it's controlled by the private key associated with it, and it can be resolved through multiple methods depending on implementation.
Decentralized Web Nodes and Personal Data Stores
TBD's architecture uses Decentralized Web Nodes (DWNs) as personal data stores — servers that store your data, controlled by your DID, which applications request permission to access rather than accumulating data in their own silos. Instead of Facebook owning your social graph and LinkedIn owning your professional history, these would live in your DWN. Applications get permissioned access to read or write specific data fields, and you can revoke that permission at any time. This is the data portability vision Web5 is most focused on.
Comparison with Ethereum ENS and Lens Protocol
Ethereum's ENS (Ethereum Name Service) maps human-readable names (alice.eth) to Ethereum addresses and IPFS content hashes — a practical identity layer for the Ethereum ecosystem. Lens Protocol builds on top to create decentralized social profiles where your followers, posts, and social graph are on-chain and portable between applications. Both are meaningful improvements over Web2 identity, but both are tied to Ethereum's availability and economic model. Web5's Bitcoin-based DID method (did:btc) argues that Bitcoin's security model and 15-year track record make it more suitable as an identity anchor than a smart contract platform.
Practical Outlook
Web5 is still largely specification and prototype. Real-world Web3 identity products — ENS names, Lens profiles, World ID — have actual users and momentum. The DID standard has seen adoption in enterprise contexts (Microsoft's ION on Bitcoin, government identity pilot programs in several countries) but consumer adoption is limited. The most likely outcome is not that a single identity model wins, but that DID standards create interoperability between multiple identity systems — so your Ethereum ENS name, your Lens profile, and your corporate Microsoft DID all resolve to the same underlying identity document, giving you portability across ecosystems.
