In recent years, forces have converged to enable a new mechanism for software development at scale: the entrenchment of collaborative, API-drivable software development platforms such as GitHub, the trustless payment and contract systems of crypto networks, and the rapid acceleration of artificial intelligence, especially in the adoption and very quick optimization of large language models.

Web3 has provided a breakthrough in the coordination of machines and capital. No prior technology, incentive scheme, legal system or coordination mechanism has ever scaled and aligned networks of capital and machines so rapidly. This, on its own, represents a “killer use” for crypto and is a base layer to build on. 

In the previous post in this series, we laid out an argument that for DAOs to realize their potential as composable building blocks, they need to evolve to be truly programmable entities whose contracts implement the core functionality of each respective DAO. We described an example, SupportDAO, whose mission is to provide customer service for Web3 applications and protocols, and we discussed a possible programmable interface for SupportDAO which would allow the DAO to accept customer support cases to be processed, process the cases, and be paid based on successful resolution of those requests.

Much has been said about the idea of “money legos”, specifically with respect to decentralized finance systems. Crypto currency is programmable money, and programmable components done well are composable. The software industry has a rich history of approaches to composability (and, with it, code reuse). So when you start to think of money and the capabilities around it (borrowing, lending, etc.) as programmable components, a natural following step is to see how these various money-related components can be put together in new and unexpected ways.