Special thanks to Mike Armstrong, Aaron Henshaw, Michael Atassi, Steven Willinger, and Shan Aggarwal for helping to inform this article.
* * *
Despite the rise of Bitcoin and Ethereum, along with the emergence of new categories like DeFi, NFTs, GameFi and DAOs, web3 developers represent less than 1% of the 31.1M software developers globally.*
So why are there so few developers in web3 today? For one, the tools and infrastructure available to web3 developers are much less robust than that of web2. This simply makes it more difficult to get started building, experimenting, and deploying in web3. That’s all quickly changing however, as the number of monthly active web3 developers hit at the end of 2021. And to support this growing contingency, is a vibrant ecosystem of teams working to simplify the entire web3 developer journey, which will ultimately help unlock the next stage of web3 growth and innovation.
In this edition of Around The Block, we’ll explore the growing web3 developer stack.
Software development is the process of building computer programs. There are three main components to a given program:
The front-end (what users interact with)
The back-end (what users don’t see)
Database (where critical data is stored)
The front-end that a typical user interacts with through a mobile or desktop browser is basically the same in web2 and web3. A web3 app like Uniswap looks similar to a typical web2 app because both front-ends are mostly created using React — a popular developer framework for web and mobile apps.
It’s under the hood where web2 and web3 differ. The backend frameworks and types of databases that make web3’s defining characteristic — user-defined ownership — possible are new and unique.
Where web2 applications largely rely on centralized databases, web3 applications are built on decentralized databases (blockchains). This requires entirely new backends and new primitives like wallets.
The tools that aid in the creation, deployment, and maintenance of web2 applications are incredibly developer-friendly, thanks to decades of cumulative development. Out of the box solutions, mature infrastructure, shared code libraries, and easy to use frameworks largely make building in web2 a breeze.
Web3 on the other hand still requires specialized expertise to interface with complex infrastructure and commonly involves many redundant processes given that the stack is less developed, leaving teams to have to reinvent the wheel. That said, the tooling that will help onboard the next 1M+ web3 developers is rapidly improving.
Let’s take a (non-exhaustive) look at the evolving Web3 developer stack layer by layer (* denotes Coinbase Ventures portfolio company).
The first decision a web3 developer has to make is which blockchain protocol to build on. Building on Bitcoin is entirely different from building on Ethereum, and Solana differs from Ethereum, etc.
For faster and lower-cost applications, developers might want to build on a layer2 protocol — *, *, etc. For applications that need to port value from one chain to another, developers will want to leverage cross-chain bridges like or *.
Once these decisions are made, developers can start to incorporate building blocks that make user applications possible.
The next thing a developer needs to figure out is how their application will ultimately interact with the underlying blockchains. This is where infrastructure primitives come into play.
Node infrastructure — Nodes are where an app’s interaction with a blockchain “happens.” They’re computers that read the state of the blockchain and write updates to it once a user interacts with an application. Node infrastructure providers like , *, and * let developers easily set-up, manage, or access blockchain nodes, saving developers considerable time and resources.
Wallet & Key Management — Blockchain wallets, like , allow users to manage the private keys needed to perform transactions within web3 applications. Wallet and key management providers like * or *, enable developers to build secure connectivity between blockchain wallets and user-facing applications.
Identity — protocols like * serve as a user’s identity across applications. * provides frameworks and toolkits that developers can use to verify user credentials to authenticate actions on Ethereum. For example, developers can use the Spruce ID toolkit to empower users to sign into apps with their ENS accounts. Additionally, companies like provide developer tooling for granting access to content, software, and other data utilizing their tokens or NFTs.
Decentralized compute — Compute resources provide processing power that applications rely on to carry out computational tasks. Currently, most of the web’s compute is provided by centrally owned providers like AWS. Decentralized compute is a shift towards community-owned networks, in which compute resources are distributed in a permissionless manner at low-cost. Companies like and have emerged to provide peer-to-peer compute resources that are highly-performant and optimized for smart contracts and blockchain applications.
Decentralized storage — Storing every piece of data associated with a given web3 app directly on blockchain nodes is costly. Rather than storing data on a centralized database, web3 developers can use peer-to-peer data storage protocols like , *, and * for certain data. For example, web3 blogging site Mirror is built on Ethereum, but stores actual blog content on Arweave.
Oracles — For a typical Ethereum application, the blockchain stores transaction history and “state” (balances, smart contracts, and other variables). It can’t, however, natively store and interact with data from external sources — i.e. transaction history from other blockchains or “real world” data like the weather in San Francisco. That’s where oracles like or *come in, connecting blockchains to on-chain and off-chain data sources.
Interoperability — many different blockchains exist but few have the ability to exchange value and make use of information cross-chain. Interoperability protocols like *, , and * provide SDKs and APis for developers to build apps that are portable and can communicate with different blockchains.
Atop the infrastructure primitives that allow applications to interact with blockchain networks are tools that allow developers to more seamlessly interact with the above-named primitives.
Frameworks & IDEs — Developer frameworks consist of libraries of code that other developers have created that make development easier. Web3 frameworks like , *, , and *, let developers leverage existing code for smart contract applications so they don’t have to build everything from scratch. They also let developers test and deploy applications. Integrated development environments (IDEs) like and combine common source code editors, and build automation and debugging tools into a single, easily accessible interface.
Low-code / No-code — These platforms enable user-facing applications to be quickly designed/deployed entirely via drag-and-drop interfaces. Companies like provide developers with smart contract templates for NFTs to prevent web3 developers from having to reinvent the wheel.
Index & query — Data indexers help people locate and access specific data within an underlying database. In Web2, Google search is the most popular data indexing service that allows users to query data stored in online databases with sub-second response times. In Web3, decentralized indexing services are emerging to help app developers fetch, process, and query blockchain data. *, *, and * all provide APIs for extracting and making use of data from decentralized data storage providers and EVM-compatible blockchains.
Test, simulate, & monitor — It’s important to test and simulate web3 applications before they’re released into the wild. Companies like * and * offer a variety of tools for simulating how smart contracts and transactions will behave once live, as well as tools for debugging any issues. * provides dashboards and tools for monitoring transactions before they are submitted on-chain.
Security & audit — Given the potential for smart contract exploits, these platforms let developers apply security and audit best practices to their applications. , *, *, and * all provide a variety of services, frameworks, and monitoring tools for developers to mitigate potential security risks and vulnerabilities.
Messaging — Web3 apps often involve sending various communications to end users. For example, a crypto wallet may want to push a user alerts regarding transaction confirmations. Companies like * and are building secure messaging protocols and decentralized communication networks that drive user engagement and power these notifications within Web3 applications.
Analytics — There’s a host of platforms and services that let developers explore, analyze, extract, and visual blockchain data. *, *, and * each offer a variety of APIs and reporting capabilities to build data visualization features within web3 apps. * offers SDKs (software development kits) and APIs to create and share data insights on various crypto projects.
App Enablement LayerThe application enablement layer ties all of the above layers into specific web3 uses. NFTs, DAOs, DeFi, and gaming each have their own bespoke developer solutions.
NFT focused tools offer infrastructure for creating and managing NFT assets. DAO tools offer solutions for DAO creation (*, *), governance (*), and treasury management (*). DeFi focused tools offer APIs that let developers access various DeFi primitives. Gaming focused tools ( *, *, *) provide solutions for creating virtual worlds and blockchain based games.
The protocols, infrastructure, and developer tools mentioned above make up the nascent, yet evolving web3 developer stack. The modular and interoperable nature of web3 means that the stack can be combined in endless ways to create new and interesting applications.
While the framework and layers we highlighted will likely remain unchanged, we continue to see new developer tooling primitives emerge and expect the entire stack to evolve dramatically in the coming years.
Coinbase Ventures will continue to invest in the next generation of platform and developer tooling that will ultimately onboard millions of developers into web3. If you’re as dedicated to building out the web3 dev stack as we are, we would love to hear from you —
* * *
* * *
This website does not disclose material nonpublic information pertaining to Coinbase or Coinbase Venture’s portfolio companies.
Disclaimer: The opinions expressed on this website are those of the authors who may be associated persons of Coinbase, Inc., or its affiliates (“Coinbase”) and who do not represent the views, opinions and positions of Coinbase. Information is provided for general educational purposes only and is not intended to constitute investment or other advice on financial products. Coinbase makes no representations as to the accuracy, completeness, timeliness, suitability, or validity of any information on this website and will not be liable for any errors, omissions, or delays in this information or any losses, injuries, or damages arising from its display or use. Unless otherwise noted, all images provided herein are the property of Coinbase. This website contains links to third-party websites or other content for information purposes only. Third-party websites are not under the control of Coinbase, and Coinbase is not responsible for their contents. The inclusion of any link does not imply endorsement, approval or recommendation by Coinbase of the site or any association with its operators.