Bitcoin has no unique use cases. It's simply a form of money that's secure, a worldwide trading economy that works.

The reason that's interesting is because as humanity we never had one of those before.

I won't attempt to enumerate the ways that crypto is useful. But i'll tell you how I want to use it.

But first, it's important to understand this. The actual foundations for what crypto can enable is still being built, so if you're expecting me to show you some "killer app"... i'm not going to show you a working version today. Is that because Crypto is vaporware? No, i'm seeing important stuff deployed all the time. It's because the underlying infrastructure is being built as we speak. One example, today ETH transactions are expensive. I bought an ENS domain (which hey, that's cool) the domain cost $5, but the gas cost $200. That's a problem. Fortunately, that's a problem people are working on. ETH is building out L2. AVAX (the chain I am most heavily invested in) is using something called subnets. A subnet for example allows you to have a custom VM, and isolate chain traffic (gas cost is a function of supply and demand for blockspace, if you both increase supply of blockspace, and decrease demand for specific blockspace you can reduce gas prices). The early examples of subnets are demonstrating this theory is true.

With cheaper transactions, and custom VM's the application space will widen. On my preferred chain AVAX, that's stuff that is JUST now being released (like first one was deployed a few weeks ago). The stuff that is becoming popular today (Defi, NFT's etc) are foundational components.

So with that laid out, here's my use case. I want to run a SaaS. How is a blockchain superior to "traditional" methods? A saas managed by a DAO has a central advantage. No employees. As a corporation i'm limited by the resources I have employed for me. Need a feature? Let me prioritize it, add it to a sprint etc. Corporations have employees, and they can only move as fast as those employees allow it. A DAO with zero employees has the entire internet as a potential contribution source. But unlike open source development, it's not done by "good will". You can pay people for their contributions in a trustless way that allows ANYONE to contribute and earn. Also, and this IS a benefit, in a future of GPT3 and AI assisted coding. There's probably going to be swarms of bots searching the space for work. Posting work, providing a way to pick it up, and integrate it into your project is going to be WAY faster in the blockchain space, than what corps will be able to acheive. But there's a few missing pieces before this can work. We have services like Akash, so throwing services into the blockchain is possible today. But managing a repository on the chain is not. I was contemplating using stateful precompiles in a Subnet VM to do this. The next problem is bridging SUCKS, but all these raw components are scattered around. That makes it difficult, even with the pieces defined to be combined. Solvable problems, but things that need to be solved.

> But unlike open source development, it's not done by "good will". You can pay people for their contributions in a trustless way that allows ANYONE to contribute and earn.

You can pay people for open source work now. You can even pay them in crypto.

A DAO doesn't make any of the hard work of developing a system (eg, specifying what you need, arguing if it has or hasn't been developed correctly) any easier.

I hear what you're saying, and I agree given your framework of constraints its true. I'd argue the constraints are wrong on chain. If you're engineering a "system" you're thinking like a corporation.

The magic of crypto are the various protocols are like legos. I think a DAO should be a simple single capability like a unix process. It should strive to do one thing well.

"money lego" works well when it's specific technical capabilities that need to be stuck together.

That makes no sense at all when it's a complex process with human interactions.

I think DAOs are interesting things. But the completely naive way people talk about them (like what you are saying here) is completely unrealistic and shows the lack of technical experience that so much of crypto suffers from.

in my experience volunteering at a dao, daos increase coordination effort required and have yet to yield additional productivity.

i wonder which pieces we are missing to get to your theoretical world of increased efficiency.

Frankly I haven't seen a DAO that operates the way I'd assume a DAO should operate. Today they seem like little developer collectives. It doesn't surprise me that it's less effecient. I think I explained in my previous post what I think needs to be built.

There does exist gitcoin today, but that is not a repository attached to a smart contract. The idea of smart contracts governing a repository is POWERFUL and critical to making it work IMO.