Web2 v Web3 Front End Cheat Sheet

The chart below is a “cheat sheet” laying out the primary differences between Web2.0 and Web3.0 Front Ends.

	Web 2.0	Web 3.0
Front End’s Role	Single proprietary website communicating to single proprietary back end software to execute user requests (e.g., Venmo transfer).	Many optional access points (websites, browser extensions) to open source, permissionless software, which allows users to send their own requests to the open back end which is programmed to automatically execute users’ requests.
Back End Visibility	Proprietary software, not publicly available, closed-source.	Openly viewable and auditable, source-available or open-source.
Custody & Control Over User Data or Assets	Companies operating front ends own and control user data and assets and control the flow of customer funds.	No third party has access or control over user data, assets, or the flow of funds. Users own and control all and decide when and how to use them via optional access point. Software developers have no relationship with users and do not custody or control user data or assets.
Control Over Back End Software	Centralized control by an identifiable company or group of entities.	No person/group of persons has unilateral control over the back end.
Information Asymmetry & Disclosures	Centralized companies hold non-public routing/execution information, oversight and disclosures required to correct information asymmetries.	Public, decentralized blockchains means there are no intermediaries with non-public information. No information asymmetries.
Customer Relationship	Customers are in contractual privity with companies; information is collected and service is provided. Web2.0 companies are trusted to carry out actions on behalf of customers and  resolve errors.	No customer relationship between Web3.0 developers and end users of permissionless networks; developers provide software tools for users to communicate self-directed transactions with blockchains.